Data and services
The platform separates data (what you upload), services (what you publish) and scenes (what users open). Keeping the three layers clear makes projects easier to reuse across applications.
Supported data
| Data |
Typical use |
| Photos and panoramas |
Site records, facade inspection, panorama tours |
| Point clouds |
Terrain, buildings, scan-to-BIM checks |
| 3D Tiles / OSGB |
City and site models |
| Shapefile / GeoJSON |
Boundaries, parcels, planning layers |
| GeoTIFF / imagery |
Basemaps and raster analysis |
| IFC / Revit |
BIM models |
| CSV |
Business and sensor tables |
Convert very large models to 3D Tiles before publishing. Keep the source files in your own archive; the platform stores the published copy.
Workflow
- Create a project and choose the coordinate reference system used by the data.
- Upload files through the data manager, or register a storage path for large data sets.
- Check the bounding box, height offset and coordinate system after import.
- Publish the data as a service (3D Tiles, terrain, imagery or feature service).
- Authorise the service for the users, roles or applications that need it.
- Use the service in a scene, dashboard or map application.
Publishing services
- Publish one service per logical layer, not one service for an entire project.
- Keep layer names stable; downstream scenes and applications reference them.
- Set the visible level of detail and the maximum tile level before publishing.
- For imagery, confirm the resolution and NoData value; transparent edges are a common source of visual seams.
Projects, resources and permissions
- A project groups data, services and members.
- Roles decide who can upload, publish, edit or only view.
- Tenant administrators manage members and quotas; project administrators manage content.
- Share a scene or application with a URL or QR code only after checking that anonymous access is intended.
Common issues
| Symptom |
Check |
| Model sits below or above the ground |
Height offset and vertical datum |
| Layers do not align |
Coordinate system of each source and the project |
| Publishing is slow |
File size, tile count and storage throughput |
| Service loads but tiles are missing |
Tile path, permissions and CORS |
| Colours look washed out |
Texture format, colour space and lighting settings |
Next