[openstreetmap/openstreetmap-website] Increase may key and value max length (#2025)

[mmd]

As a very first step, the API should include the current _**max{key,value} lengths**_ in https://api.openstreetmap.org/api/0.6/capabilities. Then editors could start respecting those settings rather than using some hardcoded value. It would enable us to to switch at least all editors to a larger field length all at once, simply by rolling out a new version of the osm website (+cgimap).

This sounds much easier than it really is: we've got lots of editing applications, and sometimes people use ancient versions. Some older apps might be unsupported, and will break. Preventing them from uploading corrupted data to OSM seems like a logical requirement.

My optimistic assumption is that this step alone takes at least 1 year.

Meanwhile, we need to figure out, what to do with all those data consumers. Expect plenty of time for research. I have no idea, what kind of fixes will be needed for tools like osmconvert, osmium, and many other binary file format based apps, including many mobile apps. This will be the most difficult part of the whole endeavour. Changing a few limits in editing apps will be a piece of cake in comparison. 

Deliberately I left the decision open, if switching from 0.6 -> 0.7 would be needed as well, as it causes all sorts of pains on its own.


-- 
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/2025#issuecomment-429615259
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20181014/148ff6e6/attachment.html>