[Talk-us-massachusetts] Let's delete MA imported massgis: attributes

[Nicholas Davidowicz]

Took me awhile to find an example, it seems the OSM render behavior has
been changed so this is usually only apparent in editors (or other software
that relies on correct tagging), but here is one.

https://www.openstreetmap.org/edit#map=17/42.10157/-71.71371

Jones Road in Sutton. The "condition" tag is "intolerable" for a portion of
the road, and the "surface" tag is "unpaved". But, for the good half of the
road, the "condition" tag is "fair", and for that section, there is no
"surface" tag. I expect the "surface" to be "paved" or at least not
"unpaved"; this is misleading (especially because the road has since been
repaved entirely).

In short, anywhere the "condition" is not at least "fair", the "surface"
will be incorrectly tagged "unpaved".

On Sat, May 6, 2017 at 10:38 AM, Greg Troxel <gdt at lexort.com> wrote:

>
> Nicholas Davidowicz <nicholasdavidowicz at gmail.com> writes:
>
> > another related issue I've noticed is that paved roads will be mis-marked
> > as unpaved if they are are a certain State of disrepair. should be
> possible
> > to tackle this with an automated too.
>
> I don't follow.   If there is a tag that says the road is not in good
> repair, and that's accurate, then if some software is choosing to treat
> it as unpaved that is a perhaps valid choice.  Removing tags because you
> don't like how some software chooses to behave doesn't seem right.
>
> What software are you talking about?   OsmAnd has the ability to show
> surface quality, but it's confusing (to me anyway) because there are
> multiple things to code on each road (surface, quality, access) and only
> so many colors.
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk-us-massachusetts/attachments/20170506/5fd6c645/attachment.html>