Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

check for certain keys whose values contain a semicolon (or more) #22

Closed
malenki opened this Issue · 8 comments

2 participants

@malenki

There are several keys where it is not appropriate that multiple values should be mentioned, separated by semicolons. This often appears when several way segments with identical keys but different values are merged.
Best example I found so far: maxspeed=90;␣90;␣90;␣90;␣50;␣90;␣90;␣90;␣90 -> https://www.osm.org/way/217853059/history
Keys which should be checked (incomplete list):
maxspeed
cycleway
sidewalk
oneway
highway
See also my recent diary entry: http://www.osm.org/user/malenki/diary/21081

@mueschel
Owner

I implemented it as a new check for "suspicious values".

@mueschel mueschel closed this
@malenki

More suggestions of keys to check for (suggested by stw1701):
landuse
tracktype
layer
width
wheelchair
lanes
smoothness
postal_code
trail_visibility

@mueschel
Owner

Sounds good.
I'm not sure about the postal code - many big companies in Germany have their own code, but can also be reached by the normal area code. Maybe someone wants to tag both?
trail_visibility and smoothness are used very often with free text values - wouldn't it make sense to allow lists here?

@mueschel mueschel reopened this
@malenki
@mueschel
Owner

You're right. I added the exceptions you mentioned.

@mueschel
Owner

I think we forgot to close this...

@mueschel mueschel closed this
@malenki

I cannot find "suspicious values" on http://keepright.ipax.at/report_map.php

@mueschel
Owner

Keepright.at is still not running on this version of the code - reasons are various, and it most likely will take a while until we do this step.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.