> For the complete documentation index, see [llms.txt](https://docs.gospace.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gospace.com/how-gospace-works/data-formats-and-frequency.md).

# Data formats and frequency

The formats, fields and update frequency gospace needs for each data source.

***

This page is the technical reference for connecting your data. To see what each source unlocks, and which ones you need, start with [Your data and what it unlocks](https://docs.gospace.com/how-gospace-works/your-data-and-what-it-unlocks).

**You only need floorplans and people and teams to start.** Everything else on this page is optional and can be added at any time.&#x20;

### At a glance

| Data                             | How it reaches gospace                                            | How often                                                         | Setup         |
| -------------------------------- | ----------------------------------------------------------------- | ----------------------------------------------------------------- | ------------- |
| Floorplans                       | DXF, IMDF or PDF upload, or Microsoft Places import               | When your space changes                                           | Self-serve    |
| People and teams                 | CSV file over SFTP, Snowflake, or Microsoft directory integration | Kept in sync; at least whenever people join, leave or change team | Self-serve    |
| Attendance history               | CSV file over SFTP, Snowflake, or the gospace API                 | Daily or weekly                                                   | Self-serve    |
| Wi-Fi presence (Cisco Meraki)    | Direct Meraki integration                                         | Every 5 minutes, automatically                                    | Self-serve    |
| Wi-Fi presence (other providers) | CSV file over SFTP                                                | At least every 15 minutes for live features                       | With our team |
| Space sensors                    | Disruptive Technologies integration, other providers on demand    | Continuous                                                        | Self-serve    |
| Calendar and collaboration       | Microsoft 365 (Microsoft Graph and calendar)                      | Continuous                                                        | With our team |

### Floorplans

**Accepted formats:** DXF, IMDF, PDF, JPEG. You can also import floorplans from Microsoft Places.

Upload a floorplan for each floor you want gospace to manage. You then define zones, desks and rooms on it. Room sizes come from here, which is how gospace matches meetings to rooms of the right size.

### People and teams

**Delivered by:** a CSV file over SFTP, Snowflake, or a Microsoft directory integration (Entra ID).

**Required user fields**

| Field      | Description                                                                                                              |
| ---------- | ------------------------------------------------------------------------------------------------------------------------ |
| User ID    | A unique identifier for each person, such as an employee ID. It must match the ID used in your attendance or Wi-Fi data. |
| Email      | The person's email address                                                                                               |
| First name |                                                                                                                          |
| Last name  |                                                                                                                          |

**Required team fields**

| Field     | Description                       |
| --------- | --------------------------------- |
| Team ID   | A unique identifier for each team |
| Team name |                                   |

**Example file**

| First\_Name | Last\_Name | Email                      | UserID          | Team\_Name | TeamID |
| ----------- | ---------- | -------------------------- | --------------- | ---------- | ------ |
| Rees        | Foulkes    | <rees.foulkes@gospace.com> | uid-c2dr5-6f8l0 | Product    | P10T   |
| Ron         | Jones      | <ron.jones@gospace.com>    | uid-d4h5-9pn61  | Sales      | S11T   |

{% file src="/files/UpOTpuOY8mxhBxudmo01" %}

**Team hierarchy** (teams within teams) is currently supported through the SFTP file only.

### Attendance history

**Delivered by:** a CSV file over SFTP, Snowflake, or the [gospace API](https://developer.gospace.com/start-building/add-historic-attendance).

**How much history:** gospace can forecast with **3 months** of history. We recommend **at least 6 months**. Without history, gospace collects from the day you connect and starts forecasting once there is enough.

**After the initial load:** keep sending new attendance **daily or weekly**, so gospace stays aware of current trends.

**Required fields**

| Field            | Description                                                                                                      |
| ---------------- | ---------------------------------------------------------------------------------------------------------------- |
| User ID          | Must match the User ID in your people data. Anonymised IDs are fine, as long as they are the same in both files. |
| Location         | The building the person attended                                                                                 |
| Date / timestamp | Date and time of entry and/or exit                                                                               |

**Example file**

| Date            | User ID         | Location |
| --------------- | --------------- | -------- |
| 10/2/2025 16:14 | uid-c2dr5-6f8l0 | Boston   |

{% file src="/files/2T8MAKq9RHunCn1iAGt1" %}

**Time zones:** tell us whether your timestamps are in UTC or in the building's local time.

**No badge data?** If your Wi-Fi data identifies people and covers past periods, it can be used as your attendance history instead.

### Wi-Fi presence

#### Cisco Meraki

gospace connects directly to Meraki and pulls presence data **every 5 minutes**. No file transfer is needed. See [Cisco Meraki](https://docs.gospace.com/integrations/connecting-an-integration/cisco-meraki).

You will also place your access points on the floorplan so gospace knows which zone each one covers.

**Identified or anonymised:**

| Your Meraki data... | gospace can use it for                                                                               |
| ------------------- | ---------------------------------------------------------------------------------------------------- |
| Identifies people   | Live presence, automatic desk release, zone usage, community recommendations, and attendance history |
| Is anonymised       | Zone usage only                                                                                      |

#### Lambent spaces (beta)

gospace connects to Lambent spaces and pulls area utilisation. This data is fully anonymised so it provides zone usage only.

#### Other Wi-Fi providers

Wi-Fi data from other providers can be sent as a CSV file over SFTP. For live features such as automatic desk release, data needs to arrive **at least every 15 minutes**. Talk to us about your provider and we'll set it up with you.

### Space sensors

gospace integrates with **Disruptive Technologies** sensors, which provide zone usage at desk and room level. For other sensor providers, [get in touch](https://www.gospace.com/contact).

### Calendar and collaboration

gospace uses **Microsoft 365**: Microsoft Graph for collaboration, and calendar data for meeting requests. Microsoft Places room bookings are calendar events, so they are picked up too.

Our team sets this up with you.

### General rules

* **Keep IDs consistent.** The same person must have the same User ID in every file and integration, or gospace can't link their data.
* **Anonymised IDs are supported** wherever a User ID is required, as long as they are consistent.
* **SFTP connections** support username and password, or public key authentication. You can use your own SFTP server or ours.

### Next steps

* [Connecting an integration](https://docs.gospace.com/integrations/connecting-an-integration)
* [Mapping your data](https://docs.gospace.com/integrations/mapping-your-data)
* Questions about your data? [Contact us](https://www.gospace.com/contact)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.gospace.com/how-gospace-works/data-formats-and-frequency.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
