100% true. Consumers don't respect (Polish word "szanować" beside "to respect" means something like taking care of a thing, especially if you got it from someone) our data. Most implementations are mediocre to horrible. Main offenses are displaying irrelevant things, very scarce tags support, partial and outright wrong translation of object types, needless exposure of users to OSM data model (eg. directly slapping raw opening_hours on the screen), and no understanding of regional differences in address formats.
This sparked an idea in my mind some time ago. If anyone has resources, they could make some sort of library/program (and maybe distribute compiled data "products") that does all these "software has to..." cases, doing eg. access values inference and whatever the user specifies, maybe normalization (conflating tags that mean the same, or abstracting from tags whatsoever - example would be that shops come with shop=* mostly, but some do with amenity=* - or that there are services that are tagged as shop=*) or address/admin preprocessing which apparently is SO tricky (people still often don't understand that addr:place is there...) Doing things once is beneficial, saving work and keeping bugs out. Michał On Sun, May 31, 2015 at 4:46 PM, pmailkeey . <pmailk...@googlemail.com> wrote: > Totally agree - the oneway(=no) is being misinterpreted. > > OSM's BIG ISSUE is what to do about others misinterpreting OSM data and > attributing the error to OSM. > > -- > Mike. > @millomweb - For all your info on Millom and South Copeland > via the area's premier website - > > currently unavailable due to ongoing harassment of me, my family, property & > pets > > T&Cs > > _______________________________________________ > talk mailing list > talk@openstreetmap.org > https://lists.openstreetmap.org/listinfo/talk > _______________________________________________ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
