<div dir="ltr">I didn't share my viewpoint yet here. In my opinion, there is usually no need for more than one image on a POI (two at worst), so I don't see a need. If you want to photograph each entrance of a school, why don't you attach each photo to the respective entrance? If you made photographs of each hall, why don't you do indoor mapping and attach the photos to the respective hall, etc.<br><br>In general, I think it is more productive to create a Wikipedia article about a thing of major interest (like a university) and illustrate the article with a proper amount of images and/or create a gallery there. In this case, even 1 OSM image link is considered excessive, as it could and should be scraped from the sidebar of the article by data users instead. In my experience, Wikipedia does a better job at maintaining articles (and galleries) than OSM in many, if not all regions.<br><br>Your link is 100 characters long, and a field is limited to up to 255 unicode characters, so two of these could fit in. I think if you use reasonable providers, links should be reasonably short. Filenames are optional in IPFS links and also, if we added schema-specific a key for ipfs (similar to Mapillary/Flickr/etc), it could be a lot less shorter (46 characters a piece + semicolons), like<br>image:ipfs=QmR9wseHQiLbv4AnTXACo5rQ1CEcKj2fJq6vEnuZoi6Amd<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Aug 26, 2020 at 11:06 AM Thibault Molleman <<a href="mailto:thibaultmolleman@gmail.com">thibaultmolleman@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Ah, I feel like there are certain images that might get deleted from Commons just because they don't "contribute to wikipedia articles".<div>Maybe a special example but still:</div><div>Recently mapped a construction zone for a residential area and took a couple photos. Those might not "belong on Commons" according to their moderation team. </div><div><br></div><div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">As mentioned on the linked wiki page, you can escape a semicolon by doubling it:<br><blockquote><a href="https://wiki.openstreetmap.org/wiki/Semi-colon_value_separator#Escaping_with_.27.3B.3B.27" target="_blank">https://wiki.openstreetmap.org/wiki/Semi-colon_value_separator#Escaping_with_.27.3B.3B.27</a></blockquote></blockquote></div><div>Ah interesting, somehow missed that.</div><div>It's a solution, but still doesn't solve the problem of long urls clogging up one tag.</div><div>Definitely if you have long urls because of unique hash/id's</div><div>(extreme example: IPFS urls: <a href="https://ipfs.io/ipfs/QmR9wseHQiLbv4AnTXACo5rQ1CEcKj2fJq6vEnuZoi6Amd?filename=IMG_20200727_172553.jpg" target="_blank">https://ipfs.io/ipfs/QmR9wseHQiLbv4AnTXACo5rQ1CEcKj2fJq6vEnuZoi6Amd?filename=IMG_20200727_172553.jpg</a> )</div><div><br></div><div>Cheers,</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, 26 Aug 2020 at 10:54, bkil <<a href="http://bkil.hu" target="_blank">bkil.hu</a>+<a href="mailto:Aq@gmail.com" target="_blank">Aq@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>As mentioned on the linked wiki page, you can escape a semicolon by doubling it:</div><a href="https://wiki.openstreetmap.org/wiki/Semi-colon_value_separator#Escaping_with_.27.3B.3B.27" target="_blank">https://wiki.openstreetmap.org/wiki/Semi-colon_value_separator#Escaping_with_.27.3B.3B.27</a></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Aug 26, 2020 at 9:11 AM Thibault Molleman <<a href="mailto:thibaultmolleman@gmail.com" target="_blank">thibaultmolleman@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto">While I use the semicolon for some other tags already, the problem with using it for something that has a URL. <div dir="auto">Is that TECHNICALLYaccording to the specification, a URL can contain a semicolon.</div><div dir="auto">So I feel like the use of a semicolon in a url based tag isn't a good solution</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Aug 26, 2020, 08:44 Mateusz Konieczny via Tagging <<a href="mailto:tagging@openstreetmap.org" target="_blank">tagging@openstreetmap.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<div>If someone really needs multiple images on one object then<br></div><div><a href="https://wiki.openstreetmap.org/wiki/Semi-colon_value_separator" rel="noreferrer" target="_blank">https://wiki.openstreetmap.org/wiki/Semi-colon_value_separator</a><br></div><div>is standard.<br></div><div><br></div><div>At the same time use for that seems dubious for this specific tag.<br></div><div><br></div><div><br></div><div>Aug 26, 2020, 07:41 by <a href="mailto:thibaultmolleman@gmail.com" rel="noreferrer" target="_blank">thibaultmolleman@gmail.com</a>:<br></div><blockquote style="border-left:1px solid rgb(147,163,184);padding-left:10px;margin-left:5px"><div dir="ltr"><div>Hi,<br></div><div><br></div><div>It seems like there (still) isn't a proper tagging system to put multiple images on one node/way/relation.<br></div><div>Having the ability to link other images as well would be useful I think.<br></div><div>Either via:<br></div><div><div>`image=url1;url2;url3`<br></div><div>or<br></div><div>```<br></div><div>image=url1<br></div><div>image:2=url2<br></div><div>image:3=url3<br></div><div>```<br></div></div><div>That later would allow for any application that currently uses images to still continue to work perfectly.<br></div><div><br></div><div>Curious to hear your thoughts<br></div><div><br></div><div>Cheers,<br></div><div>Thibault<br></div></div></blockquote><div><br></div> </div>
_______________________________________________<br>
Tagging mailing list<br>
<a href="mailto:Tagging@openstreetmap.org" rel="noreferrer" target="_blank">Tagging@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/tagging" rel="noreferrer noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/tagging</a><br>
</blockquote></div>
_______________________________________________<br>
Tagging mailing list<br>
<a href="mailto:Tagging@openstreetmap.org" target="_blank">Tagging@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/tagging" rel="noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/tagging</a><br>
</blockquote></div>
_______________________________________________<br>
Tagging mailing list<br>
<a href="mailto:Tagging@openstreetmap.org" target="_blank">Tagging@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/tagging" rel="noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/tagging</a><br>
</blockquote></div>
_______________________________________________<br>
Tagging mailing list<br>
<a href="mailto:Tagging@openstreetmap.org" target="_blank">Tagging@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/tagging" rel="noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/tagging</a><br>
</blockquote></div>