[Tagging] V3 to V4 Mapillary image id migration
Kai Michael Poppe - OSM
osm at poppe.dev
Sun Oct 17 08:03:28 UTC 2021
Hi Stuart,
while I cannot fault Stephan's argument, that adding mapillary pictures to certain features feels strange (the most used value is "_pZwO3eo4jjZoTHDjGTJBg <https://taginfo.openstreetmap.org/tags/mapillary=_pZwO3eo4jjZoTHDjGTJBg>" which is a picture of a road-side billoard in France. I wonder how someone would think it's a good idea adding that to ~50 nodes all over the country where the image itself is just of one in one particular spot, but that's not the issue here) - nevertheless the Wiki makes it clear that a picture of the feature can be added, so to me it's totally fine if you're using that in your Map App.
To me it looks like going to https://mapillary.com/map/im/... still yields to correct image, because https://www.openstreetmap.org/node/3413495243 and the "new" image of
https://mapillary.com/map/im/ofr9UjZn4ammjewdPnGIGA (which is https://www.mapillary.com/app/?pKey=1222981694805082&lat=46.29724166666699&lng=6.07412777777779&z=17) look pretty much to be in the same area.
Yes, I have read that the imageKeys wouldn't be useful in API v4, but on first glance it seems that they did something to make (at least) their web app backwards compatible. That might not help you when your product is using the API to get the image, but from a data-consumer standpoint that would link to the website of Mapillary that seems to be OK.
I haven't read the new guidelines for the API or the T&C of the website but if you're having issues with the imageKeys that those <1000 fountains have you might want to keep a database in your app that you have filled with a match between the old imageKey and the new pKey that the above mentioned URL sends you to ... Would be an afternoon's work to get the new pKeys.
That all that is neccessary despite to promise that the OSM community wouldn't experience any downsides when Facebook took over is a whole different discussion.
Kai
On 17.10.2021 08:01, Water-Map wrote:
> Dear Stephan,
>
> Thank you for your message.
>
> While a small minority of water-map users take the time to read our OpenStreetMap data contribution instructions, the majority just use our app to find drinking water fountains or to a lessor extent to take pictures of fountains (which we store on an aws s3). Therefore, water-map is a data user and seeks a consistent and up to date database. The question of best practice concerns us less than common practice.
>
> _With respect to the mapillary tag:_
>
> Our app displays fountain images (when the point is pressed) on osm items which have wikimedia tags, certain image tags, or have an image stored on our server or have a MAPILLARY tag with a valid image id.
>
> There are currently 978 drinking water fountains in the database (ie osm nodes or ways with drinking_water=yes) with mapillary tags. All of them have V3 mapillary image ids which are stale and wrong. I am looking for a solution to this issue so that I can query the mapillary api within the app for the correct image link.
>
> There are currently over 200,000 usages of the mapillary tag. All values are incorrect in the osm database with the transition from mapillary v3 to v4.
> https://taginfo.openstreetmap.org/keys/mapillary <https://taginfo.openstreetmap.org/keys/mapillary>
>
> Info regarding the mapillary transition.
> https://blog.mapillary.com/update/2021/06/23/getting-started-with-the-new-mapillary-api-v4.html <https://blog.mapillary.com/update/2021/06/23/getting-started-with-the-new-mapillary-api-v4.html>
> Search for Api v4 keys and you will see there was a breaking change.
>
> Best regards,
>
> Stuart
>
>
>
>
>
>
> On Sat, Oct 16, 2021, 22:47 Stephan Knauss <osm at stephans-server.de <mailto:osm at stephans-server.de>> wrote:
>
> Hello Stuart,
>
> On 16.10.2021 18:20, Water-Map wrote:
> > Does anyone know if there is a way to map the old V3 mapillary image ids
> > to the V4 mapillary image ids ? Or if there is a project to have a bot
> > update the V3 mapillary image ids, or at least delete the old invalid ones?
> >
> > For example:
> > https://www.openstreetmap.org/node/3413495243 <https://www.openstreetmap.org/node/3413495243>
>
> I am sorry that I can't answer your question. But adding Mapillary image
> ids to OSM element tags is nothing I would overly encourage.
>
> Wouldn't it be more appropriate to mention this image ID on the
> changeset in which you used the imagery? You can have dozens of images
> of an element also on changing dates. So a single tag does not allow to
> link it.
>
> Stephan
>
> _______________________________________________
> Tagging mailing list
> Tagging at openstreetmap.org <mailto:Tagging at openstreetmap.org>
> https://lists.openstreetmap.org/listinfo/tagging <https://lists.openstreetmap.org/listinfo/tagging>
>
>
> _______________________________________________
> Tagging mailing list
> Tagging at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/tagging
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20211017/54ff105d/attachment-0001.htm>
More information about the Tagging
mailing list