This documentation is no longer actively supported and may be out of date. Going forward, please visit and bookmark our new site (https://docs.phunware.com/) for up-to-date documentation.
Mapping API v1.1
This document describes the specification for the MaaS Mapping API ("API"). This API allows remote clients to manage the various resources associated with mapping, including venues, campuses, buildings, floors, points of interest, segments and routes.
Below are the object types that need to be created, read, updated and destroyed (CRUD) for geofences, callbacks and associated zone elements. Other terms used with the Mapping service are defined as well.
A location where events take place. Venues consist of one or more campuses.
A collection of one or more buildings grouped together by a common theme.
A physical structure that contains one or more floors.
An object associated with a building containing a building ID, floor ID, zoom level and resource URL(s) (e.g. .svg, .pdf).
The image files associated with a floor. The .svg or .pdf asset URL and the associated metadata are often referred to as a map.
A point of interest (POI), waypoint or portal location associated with a map.
The zoom scale on the actual map.
Zoom Level 1 = 1.0 zoom scale on device
Zoom Level 2 = 2.0 zoom scale on device
Zoom Level 3 = 4.0 zoom scale on device
Zoom Level 4 = 8.0 zoom scale on device
Zoom Level 5 = 16.0 zoom scale on device
Undefined Zoom Level = -1
The Cisco Mobility Services Engine (MSE) is a network appliance that provides tools for wireless network monitoring and network asset location tracking.