Prepare a dataset

A dataset layer contains geographic features and their properties. Use it for content such as locations, paths, boundaries, or footprints. A dataset renderer in your application determines how those features look.

To place an existing GLB instead, use a model layer.

Supported sources

GeoJSON can contain Point, MultiPoint, LineString, MultiLineString, Polygon, and MultiPolygon geometries. The uploader does not accept GeometryCollection or null geometries. Renderer support is a separate concern: your chosen SDK renderer must implement the geometry types in your data.

Delimited text produces point features. It does not infer lines or polygons from the order of rows.

Import GeoJSON

1. Add a layer, enter a name, and choose Dataset.
2. Select a GeoJSON file. The application inspects its geometry types.
3. Assign a render definition to every detected type.
4. Select Create layer and wait for ready.

Use WGS 84 coordinates in longitude, latitude order. For example:

{
  "type": "FeatureCollection",
  "features": [
    {
      "type": "Feature",
      "geometry": {
        "type": "Point",
        "coordinates": [4.8952, 52.3702]
      },
      "properties": {
        "name": "Meeting point",
        "category": "meeting"
      }
    }
  ]
}

You do not need to put ardl:render_definition in the source file. Conversion adds it from the layer's geometry-to-definition mapping.

Import CSV, TSV, or TXT

Start with a header row and one feature per row:

name,longitude,latitude
Meeting point,4.8952,52.3702
Entrance,4.8955,52.3704

1. Add a Dataset layer and select the file.
2. Review the detected delimiter and coordinate column mapping.
3. Select the coordinate reference system used by the source.
4. Map the X/longitude and Y/latitude columns. Optionally map an altitude column. Each coordinate role must use a different column.
5. Assign a render definition that accepts Point.
6. Select Create layer and wait for ready.

Supported source coordinate systems:

Conversion writes WGS 84 output. Non-coordinate columns become feature properties. Check coordinate values before uploading: blank or invalid coordinates cannot produce a usable point. The conversion worker counts rows it skips.

Choose render definitions

A mapping applies to a geometry type across the layer, not to an individual feature or a property value. For example, map all Point features to places. A places renderer can then read category to choose different prefabs or colors.

If the layer contains lines as well, map LineString to another compatible definition, such as routes, and register a corresponding renderer in your SDK.

Conversion and updates

Reality Import generates spatially indexed FlatGeobuf data. SDKs query nearby features from that output instead of reading the original upload.

Editing a layer's render-definition mapping queues conversion again. Renaming a dataset layer does not by itself requeue conversion. The editor does not replace the source dataset; add a new layer for a replacement file.

Display the dataset

• Lens Studio SDK — documentation coming soon.
• Unity SDK — documentation coming soon.