<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi Stuart,</p>
<p>while I cannot fault Stephan's argument, that adding mapillary
pictures to certain features feels strange (the most used value is
"<span class="overflow"><a
href="https://taginfo.openstreetmap.org/tags/mapillary=_pZwO3eo4jjZoTHDjGTJBg">_pZwO3eo4jjZoTHDjGTJBg</a>"
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.</span></p>
<p><span class="overflow">To me it looks like going to
<a class="moz-txt-link-freetext" href="https://mapillary.com/map/im/">https://mapillary.com/map/im/</a>... still yields to correct image,
because <a class="moz-txt-link-freetext" href="https://www.openstreetmap.org/node/3413495243">https://www.openstreetmap.org/node/3413495243</a> and the
"new" image of </span><br>
<span class="overflow"><span class="overflow"><a class="moz-txt-link-freetext" href="https://mapillary.com/map/im/">https://mapillary.com/map/im/</a></span></span><span
class="overflow">ofr9UjZn4ammjewdPnGIGA (which is
<a class="moz-txt-link-freetext" href="https://www.mapillary.com/app/?pKey=1222981694805082&lat=46.29724166666699&lng=6.07412777777779&z=17">https://www.mapillary.com/app/?pKey=1222981694805082&lat=46.29724166666699&lng=6.07412777777779&z=17</a>)
look pretty much to be in the same area. <br>
</span></p>
<p><span class="overflow">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.<br>
</span></p>
<p><span class="overflow">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.</span></p>
<p><span class="overflow">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.<br>
</span></p>
<p><span class="overflow">Kai<br>
</span></p>
<div class="moz-cite-prefix">On 17.10.2021 08:01, Water-Map wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAK=tSVdthrhaE=D_T2h0PeVi1ukOP3WFFL9ieSSgdztQKXvG9Q@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div dir="auto">Dear Stephan,
<div dir="auto"><br>
</div>
<div dir="auto">Thank you for your message.</div>
<div dir="auto"><br>
</div>
<div>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. </div>
<div><br>
</div>
<div><u>With respect to the mapillary tag:</u></div>
<div><br>
</div>
<div>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. </div>
<div><br>
</div>
<div>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. </div>
<div><br>
</div>
<div>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. </div>
<div><a
href="https://taginfo.openstreetmap.org/keys/mapillary"
moz-do-not-send="true">https://taginfo.openstreetmap.org/keys/mapillary</a></div>
<div><br>
</div>
<div>Info regarding the mapillary transition. </div>
<div><a
href="https://blog.mapillary.com/update/2021/06/23/getting-started-with-the-new-mapillary-api-v4.html"
moz-do-not-send="true">https://blog.mapillary.com/update/2021/06/23/getting-started-with-the-new-mapillary-api-v4.html</a><br>
</div>
<div>Search for Api v4 keys and you will see there was a
breaking change. </div>
<div> <br>
</div>
<div>Best regards,</div>
<div><br>
</div>
<div>Stuart </div>
<div><br>
</div>
<div><br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<br>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Sat, Oct 16, 2021,
22:47 Stephan Knauss <<a
href="mailto:osm@stephans-server.de" target="_blank"
moz-do-not-send="true">osm@stephans-server.de</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hello
Stuart,<br>
<br>
On 16.10.2021 18:20, Water-Map wrote:<br>
> Does anyone know if there is a way to map the old V3
mapillary image ids <br>
> to the V4 mapillary image ids ? Or if there is a
project to have a bot <br>
> update the V3 mapillary image ids, or at least delete
the old invalid ones?<br>
> <br>
> For example:<br>
> <a
href="https://www.openstreetmap.org/node/3413495243"
rel="noreferrer noreferrer" target="_blank"
moz-do-not-send="true">https://www.openstreetmap.org/node/3413495243</a>
<br>
<br>
I am sorry that I can't answer your question. But adding
Mapillary image <br>
ids to OSM element tags is nothing I would overly
encourage.<br>
<br>
Wouldn't it be more appropriate to mention this image ID
on the <br>
changeset in which you used the imagery? You can have
dozens of images <br>
of an element also on changing dates. So a single tag does
not allow to <br>
link it.<br>
<br>
Stephan<br>
<br>
_______________________________________________<br>
Tagging mailing list<br>
<a href="mailto:Tagging@openstreetmap.org"
rel="noreferrer" target="_blank" moz-do-not-send="true">Tagging@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/tagging"
rel="noreferrer noreferrer" target="_blank"
moz-do-not-send="true">https://lists.openstreetmap.org/listinfo/tagging</a><br>
</blockquote>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Tagging mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Tagging@openstreetmap.org">Tagging@openstreetmap.org</a>
<a class="moz-txt-link-freetext" href="https://lists.openstreetmap.org/listinfo/tagging">https://lists.openstreetmap.org/listinfo/tagging</a>
</pre>
</blockquote>
</body>
</html>