[openstreetmap/openstreetmap-website] Link to openplaques (#2405)

[eehpcm]

@Marc-marc-marc 

> I think the arguments against have not been heard, I try to summarize

An interesting summary of the arguments against. :)
 
>  avoid having to work each time the link changes or each new request like 

That's a fair point.  It's extra work.  I don't like extra work.  Not even when somebody else is doing it.

> could be solved with a PR externalizing the "osm tag -> web link" code#
> as @grischard suggests

You mean it's not already table-driven?  I'm surprised.  But your phrasing reads more like an argument for than against.  The real argument against this is that it might encourage people to request similar linkages and "taint the purity of the map."

>  the links on osm.org are made for a return to the contributor. therefore
> saying that it allows access to a text of more than 255 characters makes
> no sense. reading the full content of the plate does not help the osm
> contribution. this is for the end user.

That is a valid point.  However, isn't aiding the contributors the _primary_ purpose, not the _only_ purpose?  I refer you to the [tile usage policy](https://operations.osmfoundation.org/policies/tiles/) which states "We are in principle happy for our map tiles to be used by external users for creative and unexpected uses".

I would also point out that the standard map being used, and found useful, by end users is a means of recruiting more mappers.  Of course, the argument against that is that it will result in more load on the servers.

In the end, though, it boils down to human nature and the prime directive of OSM: "any tag you like."  Some mappers **will** add inscriptions, whether you feel those serve a useful purpose or not.  If there's a 255-character limit with no alternative like a link to an openplaques ID then some of them will resort to inscription_1, etc.  Deprecate the inscription tag, or even filter it from the results returned by the query tool and they'll just put the inscription in the description.  Or put the openplaques link in a url=* or website=*.  No standardized approach, just a slew of different bodges.


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/issues/2405#issuecomment-623675539
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20200504/db70a144/attachment.htm>