Re: [OSM-dev] Use of OSM API for non-editing third party applications

In the light of this discussion, and to follow up my original email, one thing I would want to do is associate uploaded panoramas with user IDs, for which I would need the OSM user details API. I would need this to only allow a given user to rotate or move their own panoramas, and not other

Re: [OSM-dev] Use of OSM API for non-editing third party applications

Not necessarily, the API calls user/details (https://wiki.openstreetmap.org/wiki/API_v0.6#Details_of_the_logged-in_user ) and user/preferences

Re: [OSM-dev] Use of OSM API for non-editing third party applications

Now you are confusing authentication with authorisation. On 2 August 2019 10:07:19 BST, Tigerfell wrote: >Not necessarily, the API calls >user/details >(https://wiki.openstreetmap.org/wiki/API_v0.6#Details_of_the_logged-in_user

Re: [OSM-dev] Use of OSM API for non-editing third party applications

In the OAuth authentication you get the display name and ID of the OSM user, you can then use that OSM ID to mark the users contributions in your own db. 2. ágúst 2019 kl. 11:41, skrifaði "Nick Whitelegg" mailto:nick.whitel...@solent.ac.uk?to=%22Nick%20Whitelegg%22%20)>: In the light of this