Dataset types
Every dataset has a dataset type, chosen when the dataset is created. The type decides how a delivery is read: which folders are looked in, which metadata file is read, and what is indexed from it. It is not inferred from the data.
Each page below documents one dataset type: the folder layout it looks for, the metadata file it reads, which fields are mandatory, what it tolerates, and what you get back.
Two conventions worth knowing before you read any of them:
- Nothing is reprojected unless the page says so. Coordinates must already be in the dataset's configured CRS.
- Filename matching is exact and case-sensitive.
.jpgand.jpegare not interchangeable, and which one a dataset type accepts differs between dataset types.
Both are covered properly in Concepts.
- Point cloud genericDeliver LAS/LAZ point clouds with no sidecar metadata. Folder layout, accepted files and what gets generated.
- Ortho genericOrthophoto deliveries as GeoTIFFs or ECW v2/v3, laid out in Ortho/, with no sidecar metadata.
- Mobile mapping genericHow to prepare a mobile mapping delivery: panorama images, a pose CSV, optional point clouds and dataset settings.
- Orbit Mobile Mapping ImportPanoramas exported from Orbit as a generic trajectory: the tab-separated pose file, its clock, and optional point clouds.
- DJI droneDJI drone deliveries. Metadata is read from the JPGs themselves, so there is no pose CSV to prepare.
- HorusHorus panorama deliveries with a positional pose CSV. Requires an exact one-to-one match between CSV and photos.
- Horus Movie MakerHorus Movie Maker deliveries: per-recording folders with panoramas, inspection photos and lidar.
- Horus VertexHorus Vertex recordings: pre-stitched panoramas with a Movie Maker pose CSV, plus raw lidar captures we colour for you.
- E57Scans delivered as E57, with the spherical panoramas they carry. One E57 per set, nothing else to deliver.
- AI Infrasolutions panoramaSession-based panorama deliveries with a tab-separated Recording.csv. Every row must resolve to a real photo.
- Smart Delta SmartPano Gen2Panoramas at the bucket root with a GPS_Trajectory.csv, plus a coloured SLAM point cloud.
- Inspection photosSewer and duct inspection frames driven by a GeoJSON of measurement points, one folder per inspection.
- TerraTecTerraTec aerial deliveries: oblique and nadir imagery with footprint shapefiles, plus ortho and point clouds.
- Field GeoField Geo aerial deliveries: forward, backward and nadir frames with GeoPackage footprints, four-band nadir twins, orthophoto tiles and point clouds.
- Leica CityMapperLeica CityMapper-2 aerial deliveries: nadir and oblique frames, the adjusted orientations, footprints, and optional true ortho and LAZ tiles.
- Cyclomedia importCyclomedia panorama imports driven by a DataPackage XML, with coordinate reprojection from the SRID in the package.
- ProRail PVRTrain-mounted inspection runs: one folder per Train_* pass, each with Planar1 photos and a point cloud.
- ProRail PVR (older deliveries)The earlier ProRail PVR delivery shape, where the folder layout itself differs per supplier.
- ProRail stationsopnamenStation captures under the Vraagspecificatie Stationsopnamen 2025: 360° panoramas and RD-tiled LiDAR for one station.
- ProRail straatopnamenPublic-road captures near the track under the Vraagspecificatie Straatopnamen 2025: 360° panoramas and RD-tiled LiDAR.
- Oblique (UltraMap)Oblique aerial deliveries with an UltraMap aerotriangulation export (.eo), the JPGs per camera cone, and the footprint shapefile.
- Vansteelandt obliqueOblique aerial photos from Vansteelandt's CityMapper flights: JPEGs per camera head, and one footprint shapefile carrying each photo's orientation.
- Kavel 10 obliqueKavel 10 oblique aerial deliveries: flat imagery plus per-camera direct-referencing orientation CSVs.
- SenP obliqueOblique aerial photography with a footprint shapefile, a whitespace-separated orientation file and LAZ tiles.
- Vexcel obliqueVexcel oblique aerial imagery driven by a single JSON metadata file.