| WRLD Indoor Map Format | WRLD 3D indoor map | |
|---|---|---|
 |
 |
 |
This repository contains details of the Open CC-BY-4.0 WRLD Indoor Map Format & API.
Get started creating 3D indoor maps with the TUTORIAL.md
- TUTORIAL.md - a worked example showing how to go from a floor plan to a 3D map
- FORMAT.md - a description of the Open GeoJSON-based WRLD Indoor Map Format
- Full Indoor Map API Specification - a description of the REST API for submitting maps in the WRLD Indoor Map Format
- examples/ - a folder containing example indoor maps in the WRLD Indoor Map Format, including the correct directory structure to use when submitting indoor maps.
- TROUBLESHOOTING.md - tips for solving common problems
$ curl -v -XPOST https://indoor-maps-api.wrld3d.com/v1/edits/?token=<dev_auth_token> -F name="<venue_name>" -F venue_street_address="<address>" -F venue_phone_number="<phone no.>" -F venue_email="<email address>" -F submission_contact_email="<email address for notifications>" -F venue_outline="@</path/to/my/file>"This will return a UUID string which can be used to identify the indoor map edit and query its status.
The supplied outline is a GeoJSON file containing one or more polygons in the default Coordinate Reference System. This can be created via QGIS, using online editors such as GeoJSON.io or with any other GIS software capable of exporting to GeoJSON.
When you come to upload your indoor map, your edits will be checked against the GeoJSON submitted during this claim request, so please make sure the submitted polygons fully cover the regions you want to edit, but only intersect those buildings which form part of your indoor map.
$ curl -v https://indoor-maps-api.wrld3d.com/v1/edits/<UUID>/status?token=<dev_auth_token>$ curl -v -XPUT https://indoor-maps-api.wrld3d.com/v1/edits/<UUID>?token=<dev_auth_token> -F comment="<my venue comment>" -F file="@</path/to/my/file>"This submits the map for processing, so the referenced file should contain the full detail that the user wants to see in the client. The response will contain a build_id string which can be used to identify this version of the indoor map.
$ curl -v https://indoor-maps-api.wrld3d.com/v1.1/indoor-maps/<UUID>/versions/<build_id>?token=<dev_auth_token>$ curl -v https://indoor-maps-api.wrld3d.com/v1.1/indoor-maps/<UUID>/versions/?token=<dev_auth_token>$ curl -v https://indoor-maps-api.wrld3d.com/v1.1/indoor-maps/<UUID>/versions/<build_id>/submission?token=<dev_auth_token> > submission.zip$ curl -v https://indoor-maps-api.wrld3d.com/v1/edits/<UUID>?token=<dev_auth_token>$ curl -v https://indoor-maps-api.wrld3d.com/v1/edits/?token=<dev_auth_token>$ curl -v https://indoor-maps-api.wrld3d.com/v1.1/indoor-maps/<UUID>/claim?token=<dev_auth_token> > claim.geojson$ curl -v -XPUT https://indoor-maps-api.wrld3d.com/v1.1/indoor-maps/<UUID>/claim?token=<dev_auth_token> -F venue_outline="@</path/to/my/file>"$ curl -v -XDELETE https://indoor-maps-api.wrld3d.com/v1/edits/<UUID>?token=<dev_auth_token>curl -v -X PUT https://indoor-maps-api.wrld3d.com/v1/indoor-data/<UUID>?token=<dev_auth_token> -d '{"private":<true|false>}'curl -v -X POST https://indoor-maps-api.wrld3d.com/v1/api-keys/<UUID>?token=<dev_auth_token> -d '{"apikey":"<api_key>"}'curl -v -X DELETE https://indoor-maps-api.wrld3d.com/v1/api-keys/<UUID>/<api_key>?token=<dev_auth_token>curl -v -X PUT https://indoor-maps-api.wrld3d.com/v1/indoor-data/<UUID>?token=<dev_auth_token> -d '{"referer_private":<true|false>}'curl -v -X POST https://indoor-maps-api.wrld3d.com/v1.1/referers/<UUID>?token=<dev_auth_token> -d '{"referer":"<referer_url>"}'- Domain:
wrld3d.com - Protocol and domain:
https://wrld3d.com - Subdomain:
maps.wrld3d.com - Protocol and subdomain:
https://maps.wrld3d.com
curl -v -X DELETE https://indoor-maps-api.wrld3d.com/v1.1/referers/<UUID>?token=<dev_auth_token>&referer=<referer_url>curl -v -X PUT https://indoor-maps-api.wrld3d.com/v1/indoor-data/<UUID>?token=<dev_auth_token> -d '{"user_data":{"<key>":"<value>"}}'curl -v -XPOST https://indoor-maps-api.wrld3d.com/v1/poi/<UUID>?token=<dev_auth_token> -F feature_to_poi_key="@</path/to/my/file>" -F "contact_email=<example@mail.com>"- defaults: Which interior feature types should have POIs generated, and what tag should be used to represent them.
- special: Which interior IDs should have POIs generated, and what tag should be used to represent them.
- highlight_color: What colour and opacity should be used for area highlights, where features have highlight set.
{
"defaults": {
"interior feature type": "point of interest tag",
"interior feature type": "point of interest tag",
"interior feature type": "point of interest tag"
},
"special": {
"point of interest tag": ["feature ID", "feature ID", "feature ID"],
"point of interest tag": ["feature ID", "feature ID", "feature ID"],
"point of interest tag": ["feature ID", "feature ID", "feature ID"]
},
"highlight_color": {
"red": "0-255 red value",
"green": "0-255 green value",
"blue": "0-255 blue value",
"opacity": "0-255 opacity value"
}
}{
"defaults": {
"room": "cocktail",
"highlight": "hospital"
},
"special": {
"entertainment":[318, 21, 400],
"camping":[21, 52]
},
"highlight_color": {
"red":0,
"green":220,
"blue":25,
"opacity":128
}
}Indoor Assets and Asset Sets describe the queryable contents of an indoor map floor. An Asset Set can be added to an indoor map that you have access to.
Indoor Entity Sets have a status parameter that can be either 0 or 1, which corresponds to staged or live respectively.
There can be only one published set, which is immutable. Publishing a set will create a live copy of the current set, overwriting an existing published set.
| Status | Meaning | Description |
|---|---|---|
0 |
staged |
Visible to API service but not visible to client, i.e. not automatically shown in the indoor map. |
1 |
live |
Shown in the Indoor Map on every client, also available to the API service. The published set is immutable. |
curl -v -XPOST https://indoor-maps-api.wrld3d.com/v1.1/indoor-maps/<indoor_uuid>/<floor_id>/entity-sets/?token=<dev_auth_token> -F "name=<set_name>"| Parameter | Description |
|---|---|
name |
The name of your entity set. |
indoor_uuid |
The Indoor UUID the entity set belongs to. |
floor_id |
The integer floor id of the floor the entity set should appear on. |
curl -v https://indoor-maps-api.wrld3d.com/v1.1/indoor-maps/<indoor_uuid>/<floor_id>/entity-sets/<set_id>?token=<dev_auth_token> You can fetch all asset sets associated by a dev token for a given indoor map floor:
curl -v https://indoor-maps-api.wrld3d.com/v1.1/indoor-maps/<indoor_uuid>/<floor_id>/entity-sets/?token=<dev_auth_token>curl -v -X PUT https://indoor-maps-api.wrld3d.com/v1.1/indoor-maps/<indoor_uuid>/<floor_id>/entity-sets/<set_id>?token=<dev_auth_token> -F "name=<updated_name>"curl -v -X DELETE https://indoor-maps-api.wrld3d.com/v1.1/indoor-maps/<indoor_uuid>/<floor_id>/entity-sets/<set_id>?token=<dev_auth_token>As JSON:
curl -v https://indoor-maps-api.wrld3d.com/v1.1/indoor-maps/<indoor_uuid>/<floor_id>/entity-sets/<set_id>/entities/?token=<dev_auth_token>As GeoJSON:
curl -v https://indoor-maps-api.wrld3d.com/v1.1/indoor-maps/<indoor_uuid>/<floor_id>/entity-sets/<set_id>/entities.geojson?token=<dev_auth_token>curl -v https://indoor-maps-api.wrld3d.com/v1.1/indoor-maps/<indoor_uuid>/<floor_id>/entity-sets/<set_id>/entities.geojson?token=<dev_auth_token> > ./entities.geojsonThis will delete the currently published entity set, create a copy of the specified entity set called "Published Set" and set its status to 1 ('live'):
curl -v -XPOST https://indoor-maps-api.wrld3d.com/v1.1/indoor-maps/<indoor_uuid>/<floor_id>/entity-sets/<set_id>/publish?token=<dev_auth_token>For more information on publishing an Indoor Asset Set, see the Indoor Assets Tutorial.
Indoor Assets can be added to a set you have access to. They describe something like a desk with a given model and rotation, and can have an associated user_data for use with third party data services.
curl -v https://indoor-maps-api.wrld3d.com/v1.1/indoor-maps/<indoor_uuid>/<floor_id>/entity-sets/<set_id>/entities/<entity_id>?token=<dev_auth_token>curl -v -X POST https://indoor-maps-api.wrld3d.com/v1.1/indoor-maps/<indoor_uuid>/<floor_id>/entity-sets/<set_id>/entities/?token=<dev_auth_token> -F "name=<asset_name>" -F "lat=<lat>" -F "lon=<lon>" -F "orientation=<orientation_in_degrees>" -F "model=<model_id>" -F "user_data=<user_data>"| Parameter | Required | Description |
|---|---|---|
name |
Yes | The name of your asset. |
lat |
Yes | Latitude coordinate of your asset (-90 < x < 90). |
lon |
Yes | Longitude coordinate of your asset (-180 < x < 180). |
orientation |
Yes | The orientation of the asset in degrees, where 0.0 is aligned 'North'. |
model |
Yes | The 3D model id to use for this asset. Should match a prop_id from our prop manifest. |
user_data |
No | An arbitrary data payload. Any valid json value is accepted (e.g. 1, "1", {"id": 1}). |
height_offset |
No | Optional vertical offset from the ground in meters. |
curl -v -X PUT https://indoor-maps-api.wrld3d.com/v1.1/indoor-maps/<indoor_uuid>/<floor_id>/entity-sets/<set_id>/entities/<entity_id>?token=<dev_auth_token> -F "name=<updated_name>" -F "orientation=<orientation_in_degrees>"All parameters are optional.
curl -v -X DELETE https://indoor-maps-api.wrld3d.com/v1.1/indoor-maps/<indoor_uuid>/<floor_id>/entity-sets/<set_id>/entities/<entity_id>?token=<dev_auth_token>Similar to the POI API you can perform bulk operations that can create, update or delete existing entities in a set.
curl -v -X POST https://indoor-maps-api.wrld3d.com/v1.1/indoor-maps/<indoor_uuid>/<floor_id>/entity-sets/<set_id>/bulk?token=<dev_auth_token> -d '{
"create":[
{"name":"new", "lat":11.1, "lon":22.2, "orientation":45.0, "model":"circular_table_01"},
{"name":"new2", "lat":33.3, "lon":44.4, "orientation":22.5, "model":"circular_table_01"}
],
"update":[
{"id":5, "name":"updated_name"}
],
"delete":[
6,
7
]
}'You can also fetch all the assets for a given floor you have access to. Using a dev token will show both Live and Staged sets you have access to:
curl -v https://indoor-maps-api.wrld3d.com/v1.1/indoor-maps/<indoor_uuid>/<floor_id>/entities.json?token=<dev_auth_token>Using an API key instead of a dev token will only show you the Live assets you have access to:
curl -v https://indoor-maps-api.wrld3d.com/v1.1/indoor-maps/<indoor_uuid>/<floor_id>/entities.json?apikey=<apikey_with_access_to_indoor_map>You can also change the extension to .hcff to retrieve a chunk file of the same data, or .geojson to download the assets + the floor trace json combined.
For more information on how to prepare an Indoor Asset AutoCAD DXF submission, refer to the Indoor Assets Tutorial.
curl -v -XPOST "https://indoor-maps-api.wrld3d.com/v1.1/indoor-maps/<indoor_map_uuid>/<floor_id>/cad_conversions?token=<dev_auth_token>" -F 'file=@<path/to/file.zip>' -F 'submission_contact_email=<optional_email_address>'Calling the above endpoint submits a file to be processed by our pipeline that takes a short time to complete. If you specified an email address, you will be mailed the result (success or failure) to that address upon completion. If not you can fetch the current status via:
curl -v "https://indoor-maps-api.wrld3d.com/v1.1/indoor-maps/<indoor_map_uuid>/<floor_id>/cad_conversions/<job_id>?token=<dev_auth_token>"The status parameter has the following values:
| Status | Value | Description |
|---|---|---|
| Waiting | 0 | The conversion job is waiting in a queue to process. |
| Working | 1 | The conversion job is currently being processed. |
| Failed | 2 | The conversion job has failed to process. |
| Success | 3 | The conversion job has succeeded. |
curl -v "https://indoor-maps-api.wrld3d.com/v1.1/indoor-maps/<indoor_map_uuid>/<floor_id>/cad_conversions/<job_id>/result.geojson?token=<dev_auth_token>"To fetch some additional information such as Warnings or Failures on a completed import request, you can call the following:
curl -v "https://indoor-maps-api.wrld3d.com/v1.1/indoor-maps/<indoor_map_uuid>/<floor_id>/cad_conversions/<job_id>/report.json?token=<dev_auth_token>"curl -v -XDELETE https://indoor-maps-api.wrld3d.com/v1.1/indoor-maps/<indoor_map_uuid>/<floor_id>/cad_conversions/<job_id>?token=<dev_auth_token>The WRLD Indoor Map data format is an open format released under Creative Commons Attribution 4.0 International. See the LICENSE.md file for details.
This is a stable, semantically versioned API.
WRLD may make changes to the API from time to time but will adhere to Semantic Versioning and provide backward compatible end points for as long as possible.
If you have any problems or queries please raise an issue.