Readonly __typeOptional amenityOptional colorOptional descriptionOptional detailsOptional externalOptional filterOptional galleryOptional logoOptional operationOptional phoneOptional pictureOptional shortOptional showOptional showOptional siblingOptional socialOptional sortOptional tagsStatic Readonly __typeCategories related to this location.
Nodes this Location is attached to.
Parent of this Location, if any. Used in cases where one Location is inside another, more "important" Location.
Polygons this Location is attached to.
Get Directions to a node, polygon, or location
Optional options: TDirectionToOptionsOptional options: TDirectionToOptionsCalculate distance between 2 nodes, polygons or locations
Optional options: TDirectionToOptionsStatic fetchStatic hydrateStatic isStatic updateOptional hydrateData: any
A MappedinLocation is something like a store or washroom on a MappedinMap. It has an ID and will be linked to zero or more MappedinNodes and MappedinPolygons.
A Location's Nodes and Polygons can be on multiple Maps, or in multiple non-adjacent places on the same Map. For example, all washroom at a given Venue could belong to one Location, or a department store could live on multiple floors. A Washroom Location might a have a few Polygons spread throughout the Venue for each one that exists, but a single store might just have one presence, and therefore one Polygon. Some Locations just have a single point and only have Nodes.
A Location can have more properties (typically things like 'name', 'externalId', 'type', 'categories', 'description', 'logo', etc).
The Mappedin 'things' object is where you would specify what properties you want to download for Locations. Only specify what you will actually use, to minmimze transfer time. Work with your Mappedin developer relations contact to set up any custom properties you need.
See below for an example a 'things' object with available Location properties specified: