Index
Migration Guide From 4.5 to 4.6
-
API: /Positioning/PropertySummaries
- In 4.6, this API has modified the
VisitSegmentobject to include a list ofDwellPointsandDwellZones DwellPointswill be detected when the user was moving very slowly or no steps were detected for more than 5 minutes. EachDwellPointshas the following form:[Longitude, Latitude, Start_Unix_sec, Duration_sec]DwellZonesare obtained by clustering the continuousDwellPointsinto zones. EachDwellZoneshas the following form:[Longitude, Latitude, Radius_m, Start_Unix_sec, Duration_sec, FloorId]
- In 4.6, this API has modified the
-
API: /Positioning/MapData
- In 4.6, the format of the
MapDataAPI response has changed - We now return a
.zipfile for the given property - Within the
.zipfile are two sub-folders BuildingLevel- Collection of building dataPropertyLevel- Collection of property data- The
PropertyLevelcontains geojson files for the basic property information, as well as the entities on the property level - Each
BuildingLevelcontains geojson files for the basic building information, as well as the entities on each floor level
- In 4.6, the format of the
-
CSV APIs: /CSV/Users, /CSV/Trajectories, /CSV/Transitions, /CSV/DwellZones
- In 4.6, we have added a CSV form of the
DwellZonesdata - All of these CSV APIs now accept an optional input
userUIDs, a comma-separated list (no space). CSV APIs will return data only related to inputuserUIDs. If nouserUIDsinput, then these CSV APIs will remain return all data.
- In 4.6, we have added a CSV form of the