Thank you for the learning resources. The video and documentation help, but as a new user it is still difficult to understand multi-building connection and path routing setup.
It would be helpful if you could provide:
Step-by-step guide for multi-building navigation
Example project with connected buildings
Visual tutorial for drawing inter-building paths
Thank you.
Mappedin makes use of OpenStreetMap for outdoor pathing. There is nothing to do within the Mappedin Map editor to create routes between multiple buildings. These are generated automatically based on OpenStreetMap data.
If you are missing routes because of new buildings or changes, the updates can be made to OpenStreetMap. After they’re accepted there, Mappedin can use them. Note that you would need to make an edit to your Mappedin Map for it to pick up the OpenStreetMap update (so that it resaves and regenerates the outdoor routes).
I would like to ask about the white-label option for our Mappedin project.
Our client would like the navigation system to display their own company name and branding instead of the Mappedin logo on the map viewer. Could you please advise if our current plan supports white-label, or if there is an upgrade available to enable this?
We are deploying the solution for our client and would like the interface to reflect their branding.
I previously submitted several enquiries regarding the white-label option for our Mappedin project but have not yet received feedback from the sales team.
We are preparing to deploy the map for our client, however the current viewer shows the Mappedin logo and our customer requires their own branding before going live.
Could you please advise how we can enable the white-label option or help connect us with the appropriate sales contact to upgrade our subscription?
Your assistance would be greatly appreciated as this project is quite urgent.
I tried copying the mapid into main.ts to integrate the map, but now I’m seeing two stacker collapsers on the interface. I’m not sure if I did it the correct way.
Could you please advise if I missed something in the setup, or if there’s a better way to initialize the map without creating duplicate UI components?
As you may have discovered, you need to copy your key, secret and mapId. Just copying the mapId will result in a 401 error because the key used in the sample doesn’t have access to your map.
Note that you’ll also need to make sure the map for the mapId you are using has been upgraded to a Pro or Enterprise map. This is required to use Mappedin SDKs. You can upgrade within the Mappedin Maker interface. Pro and Enterprise Maps should show differentiated from free maps. Free maps cannot be used with Mappedin SDKs.
I am currently subscribed to the Mappedin Pro package at USD 200/month. I would like to confirm whether this subscription entitles me to use the Mappedin SDK.
I have also been in contact regarding white-label options and a custom plan, and I want to ensure my setup is correct for SDK integration.
Additionally, I have encountered a 401 Unauthorized error when using my mapId. Could you please confirm:
That my current Pro subscription supports SDK access.
Whether the map I am using needs to be upgraded to Pro or Enterprise for SDK usage.
The correct way to use key + secret + mapId to avoid authorization errors.
Thank you for your assistance. I look forward to your guidance.
The Pro plan does include Mappedin SDK access. Note that subscriptions are per map, meaning you need to add the subscription to the map you wish to use in the Mappedin SDK.
If you are getting a 401 when using the SDK it’s likely from using the map ID of a free map or lower subscription. If this isn’t the case please contact our support team who can look into your subscription configuration.
I am currently testing the Mappedin SDK with my Pro subscription, but I am encountering a 401 Unauthorized error when trying to load my map.
Here are the details:
Map Name / ID: [Your MapID here]
API Key: [Your API Key here]
API Secret: [Your API Secret here]
Issue: 401 Unauthorized error in SDK
Note: The map was created in Mappedin Maker, but I am unsure if the Pro subscription is correctly linked to this map.
Could you please verify that my map is properly upgraded to Pro and linked to my API credentials? I want to ensure I can start using wayfinding features in the SDK.