<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
Good evening and happy easter to those celebrating!
<div class="moz-forward-container">
<p>After a ton of work and being yelled at for making too many
changesets, making too many changes, making too few changes, not
discussing the automated edit properly (?!?) and being accused
of working for Mapillary or OSMand because why else would I even
bother (clearly someone didn't read the initial rationale),
there are now 246.7k valid new API keys in the "mapillary" key,
with only 7.2k "old" keys left that could not be matched to a
new existing image, because they have either been deleted by the
user or where invalid to start with (lower case instead of upper
case character or something). <br>
</p>
<p>I haven't updated the Wiki Page [1] yet, the Community post [2]
has some more up-to-date info while I was working on the
subject.</p>
<p>** This mail is to ask for comments on editing the "image"-key
as well. **<br>
</p>
<p>Stats: There are around 14.9k objects in the planet file where
the regex "image"~".*mapillary\.com.*" matches, of which 11.1k
also contain "thumb" after that. In that case people used the
"old" way of linking to a thumbnail-image on mapillary, which no
longer exists. 10.6k objects _also_ have a "mapillary" that is
purely numeric - i.e. has been changed by the automated edit
already and is therefore known to be a correct ID. <br>
</p>
<p>** Proposed edit **</p>
<p>1)</p>
<p>(way/194649358) image=<span class="is-family-monospace"><a
href="https://images.mapillary.com/za85be97UcMzVuaPCMZQVQ/thumb-2048.jpg"
target="_blank" class="moz-txt-link-freetext"
moz-do-not-send="true">https://images.mapillary.com/za85be97UcMzVuaPCMZQVQ/thumb-2048.jpg</a>,
mapillary=</span><span class="is-family-monospace"><a
href="https://www.mapillary.com/app?focus=photo&pKey=207683754228814"
target="_blank" moz-do-not-send="true">207683754228814</a><br>
</span></p>
<p>=> image entry leads to same mapillary id, that already
exists.<br>
=> Action: remove image-entry because there are no thumbnails
available anymore.<br>
=> That's one of the 10.6k objects, so the highest amount of
objects to edit.<br>
</p>
<p>2)</p>
<p>(node/5919376334)
image=<a class="moz-txt-link-freetext"
href="https://www.mapillary.com/app/?lat=52.626783214558486&lng=-0.9952875506141936&z=17&pKey=MfEfU0jdHULiSROiCvl0Wg"
moz-do-not-send="true">https://www.mapillary.com/app/?lat=52.626783214558486&lng=-0.9952875506141936&z=17&pKey=MfEfU0jdHULiSROiCvl0Wg</a>,
mapillary=MfEfU0jdHULiSROiCvl0Wg</p>
<p>=> image entry is the website link which could also easily
be generated from the mapillary entry<br>
=> [ask myself why the id wasn't caught as a conversion
candidate before]<br>
=> Action: remove image-entry and update correct mapillary id</p>
<p>3)</p>
<p>(node/5140643074) image=<span class="is-family-monospace"><a
href="https://www.mapillary.com/app/?lat=54.041690805555554&lng=9.201796527777777&z=17&pKey=3YFedo4Ys-k0ThQM8LZgOQ&focus=photo"
target="_blank" moz-do-not-send="true">https://www.mapillary.com/app/?lat=54.041690805555554&lng=9.201796527777777&z=17&pKey=3YFedo4Ys-k0ThQM8LZgOQ&focus=photo</a>,
mapillary key non-existent<br>
(node/3762262144) image=</span><span
class="is-family-monospace"><a
href="https://www.mapillary.com/map/im/O8OS2R0tVfNEaFyZcFsesQ/photo"
target="_blank" class="moz-txt-link-freetext"
moz-do-not-send="true">https://www.mapillary.com/map/im/O8OS2R0tVfNEaFyZcFsesQ/photo</a>,
mapillary key non-existent</span><span
class="is-family-monospace"></span></p>
<p>=> image entry is the website link which could also easily
be generated from the mapillary entry<br>
=> Action: remove image-entry and add correct mapillary id</p>
<p>4)</p>
<p>(node/9425856002) image=<a class="moz-txt-link-freetext"
href="https://www.mapillary.com/app/?pKey=134015699048525"
moz-do-not-send="true">https://www.mapillary.com/app/?pKey=134015699048525</a></p>
<p>=> image entry is the website link which could also easily
be generated from the mapillary entry<br>
=> Action: remove image-entry and move the already correct
new id to the mapillary key</p>
<p>** Note **<br>
</p>
<p>As mentioned in [2] as well, objects that link to specific
x,y,zoom URIs will not be touched. As those are mostly 360°
photos where people wanted to show an exact point in the image,
linking the numeric ID alone wouldn't satisfy the mappers that
used that image in the first place. <br>
</p>
<p>** Rationale **</p>
<p>Removing dead links from the image-key sounds like a no-brainer
to me, even though it might not be with the URI being
unavailable temporarily. In this case, direct thumbnails are
never coming back.</p>
<p>For non-dead links (i.e. those leading to the mapillary
website-"app") everything (primarily the wiki page of the
image-key [3]) yells at me, that the ID should be stored in the
appropriate key.</p>
<p>**</p>
<p>PLEASE provide feedback. I hate being shouted at for trying to
support the community (remember: the reason this came up was an
app developer who couldn't use the mapillary API v4 with the old
keys anymore!).</p>
<p>Thanks a bunch!</p>
<p>Kai</p>
<p>**<br>
<span class="is-family-monospace"></span></p>
<p>[1]
<a class="moz-txt-link-freetext"
href="https://wiki.openstreetmap.org/wiki/User:Kmpoppe/Automated_Edits/Mapillary_Update"
moz-do-not-send="true">https://wiki.openstreetmap.org/wiki/User:Kmpoppe/Automated_Edits/Mapillary_Update</a></p>
<p>[2]
<a class="moz-txt-link-freetext"
href="https://community.openstreetmap.org/t/begin-of-automated-edit-for-mapillary-key/3426"
moz-do-not-send="true">https://community.openstreetmap.org/t/begin-of-automated-edit-for-mapillary-key/3426</a></p>
<p>[3] <a class="moz-txt-link-freetext"
href="https://wiki.openstreetmap.org/wiki/Key:image#Usage"
moz-do-not-send="true">https://wiki.openstreetmap.org/wiki/Key:image#Usage</a><br>
</p>
</div>
</body>
</html>