Re: [OSM-talk] Attributing others' errors to OSM data and what to do about it. Was: Craigslist OpenStreetMap Rendering Issue

[Janko Mihelić]

OSM should act as a consultant to data consumers. Whenever a mistake like
this is spotted, we should try to contact the data consumer and help repair
the misinterpretation. I think nothing more is needed.

We should also make it easier for data consumers to interpret data
correctly. I think we should have a machine readable list of tag
combinations wih their semantic meanings.

Janko

ned, 31. svi 2015. 16:50 pmailkeey .  je napisao:

> 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

Re: [OSM-talk] Attributing others' errors to OSM data and what to do about it. Was: Craigslist OpenStreetMap Rendering Issue

[Michał Brzozowski]

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 .  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

Re: [OSM-talk] Attributing others' errors to OSM data and what to do about it. Was: Craigslist OpenStreetMap Rendering Issue

[pmailkeey .]

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