-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
integration with other iOS apps #363
Comments
I have found something here, support is there for geo and gomaposm schemes but as far as I understand there is no support for specifying object type and id yet (e.g. node 123). |
There’s currently no way to open a specific node/way by its ID, but as you found you can specify the location/zoom. If other OSM apps already have a scheme we can adopt it. |
This is related to #164 and #98, right? I had a new idea for those: The whole domain-validation-process could be simplified by registering osm-gomap.app and using this as the opening-point for URLs, so osm-gomap.app/node/123 would open the node. With a custom domain, we work around the need to use the osm.org-domain but osm.org could still link to GoMap for mobile-iOS. |
After implementing this and it apparently worked I have found now that there is an issue: somehow the position is cached. It works at first, but following calls bring me back to an older position. I am using the appspecific path like this: |
Are you using the TestFlight beta? There was an issue that sometimes caused the position to not get set when the app was freshly launched (not in the background).Specifically, the call to set the position was done before the app was ready to receive it. |
Yes, I use the beta, with latest it works now as expected. great! |
This is more a question than a bug, please excuse if this is the wrong place to ask.
If someone wants to open a specific element with goMap!! from within a different iOS app, which is the format of the URL that she should use?
The text was updated successfully, but these errors were encountered: