We have a number of keys for which the values can easily exceed 255 chars besides opening_hours, lane destinations and conditional restrictions are good candidates. Not to mention changeset tags. With other words it is a general problem which should be tackled with a general solution.
One would be to extend at least the available space in the database for tag values, however that is a significant amount of work (see https://github.com/openstreetmap/openstreetmap-website/issues/1593) and I suspect it is unlikely to find support. The other way to address this would be to provide a general value extension syntax that editors and consumers could support for example say /key-/ext/-nnn /The exact semantics would need to be determined (how to split and join long values) and the key syntax needs to be chosen to minimize possible conflicts. Simon
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
