> Insulting people will get you nowhere at all. Well there over hundred messages and some people don't dare to study topic, I was repeating my messages multiple times already.
> If you want to be able to perform index searches, then import the data in tables with fields allowing you to do so. That's the great thing about open data. You can work with it any way you like. Valid point, but also should suggest good practices for people who would like to benefit from default indexes: API performance overpass performance These tools are quite popular right now and we should consider how people with work with data. JOSM is editor for raw osm data, not post-processes or indexed data. > not finding any support here for converting semicolon delimited lists to some more verbose format I don't need support. People use this *more verbose* format right now for information they care about. Problem was in outdated documentation at wiki and people at this tagging list... >The only consensus I see emerging is that we should avoid them where this is practical and possible. It was so long before discussion at tagging list. Somehow it become rege...@openstreetmap.org. > Nobody (except you) is forcing anyone to store semicolon values as literals rather than e.g. into a postgresql array. Your argument entirely *depends* on that stupid way of loading multivalue into the DB. I see your point. Actually, let's talk about it. How "smart" loading script should know if key=* is multivalued or not? Should it parse every value in database? ";;;;" - 4 symbols? 2 escaped semicolons? how do you know?
_______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
