- Products ProductsLocation Services
Solve complex location problems from geofencing to custom routing
PlatformCloud environments for location-centric solution development, data exchange and visualization
Tracking & PositioningFast and accurate tracking and positioning of people and devices, indoors or outdoors
APIs & SDKsEasy to use, scaleable and flexible tools to get going quickly
Developer EcosystemsAccess Location Services on your favorite developer platform ecosystem
- Documentation DocumentationOverview OverviewServices ServicesApplications ApplicationsDevelopment Enablers Development EnablersContent ContentHERE Studio HERE StudioHERE Workspace HERE WorkspaceHERE Marketplace HERE MarketplacePlatform Foundation and Policy Documents Platform Foundation and Policy Documents
- Pricing
- Resources ResourcesTutorials TutorialsExamples ExamplesBlog & Release Announcements Blog & Release AnnouncementsChangelog ChangelogDeveloper Newsletter Developer NewsletterKnowledge Base Knowledge BaseFeature List Feature ListSupport Plans Support PlansSystem Status System StatusLocation Services Coverage Information Location Services Coverage InformationSample Map Data for Students Sample Map Data for Students
- Help
Accessibility
This section describes how HERE Indoor Map interconnects with outdoor maps.
Street Address
Indoor maps have the indoor.Site feature, which references a street address from outdoor map data. The street address is represented as an Address feature of the sub-category PointAddress. This feature's main use is to provide a house number for the address. It is rarely self-contained, but includes a reference to the Road feature, which then gives the road name and other road-related parameters. Together, they enable access to outdoor map features, such as AdminRegion.
In some special indoor maps, the Address may also be stored within the indoor map data. The references then include the property space: indoor.
The PointAddress not only presents the street address, but also acts as a parent for all internal addresses within the indoor map.
Binding routing to outdoor roads
The street address of a site may not be well positioned for navigation, especially when there are multiple entrances to a parking facility. The MOM feature indoor.Structure, which represents structures such as parking structures or office buildings, may be connected to an Address with a sub-category of MicroPA. This address feature is part of indoor maps bound to outdoor roads, as this address will contain the property routingPoints, typically with one point per entrance. Among other properties, RoutePoint contains the ID of the road and coordinates on the road to which the route point is connected. Therefore, it provides a point in an outdoor road where a transition between an outdoor and an indoor map can take place.
Additionally, the target binds indoor topologies that pass-through entrances and exits to a node in the outdoor road network, which makes the indoor topology network an extension to the outdoor road network. Also, the coordinates of the node are captured to the corresponding RoutePoint. However, if there is no node available in the correct location within an outdoor road network, then it is possible to temporarily create an indoor-node on top of an outdoor road until a proper outdoor node is available in the outdoor map data.
Note
The route points in the structure address do not define which topology on the indoor map is connected to this route point, but during indoor map creation, HERE's tooling will ensure that at the exact coordinates of the route point, a topology will exist which will extend the outdoor topology graph into the indoor map. To identify the linkage for indoor/outdoor routing, first gather the route points for the structure from the structure's address, and then identify the indoor topologies which end on the route points' coordinates.
Binding to HERE Places
Some indoor maps are bound to HERE Places features found in outdoor map data. The binding is typically done at the indoor.Site level, but can be done at the indoor.Structure level too. Therefore, if there is a HERE Places, such as a parking garage, shopping mall, or stadium, then the linking enables finding the HERE Places object when rendering the indoor map.
indoor.Occupant may also be bound to a HERE Places feature. This is relevant when working with commercial occupants, such as shops or restaurants. However, this linking is not yet applied in indoor maps. Binding from HERE Places to indoor maps is not currently possible.
