Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a check if the surface does not match the tracktype from highway=track #1468

Closed
mcliquid opened this issue May 31, 2022 · 11 comments
Closed

Comments

@mcliquid
Copy link
Contributor

Driven by this discussion from StreetComplete, I would like to introduce my idea to the Osmose Analyzer.

Short: I noticed that quite often a surface=* is mapped to a highway=track which does not match the existing tracktype=* (or the other way around). In these cases Osmose could give a information / Error. The goal should be that both entries correspond to reality and match each other.

For example:

  • Warn if there's surface=asphalt and tracktype=grade4
  • Warn if there's surface=gravel and tracktype=grade1
  • Warn if there's tracktype=grade1 and surface=gravel

Here is a rough list of cases where this error should be triggered:
highway = track AND surface = unpaved|gravel|fine_gravel|compacted|pebblestone|dirt|earth|grass|grass_paver|mud|sand|woodchips|snow|ice|salt|rock|ground AND tracktype=grade1

highway = track AND surface = paved|asphalt|asphalt:lanes|chipseal|concrete|concrete:lanes|concrete:plates|paving_stones|sett|unhewn_cobblestone|cobblestone|cobblestone:flattened|metal|wood|stepping_stones AND tracktype = grade2|grade3|grade4|grade5

@Famlam
Copy link
Collaborator

Famlam commented May 31, 2022

Like this one?
https://osmose.openstreetmap.fr/nl/map/#item=9001&zoom=17&lat=45.820472&lon=4.345231&level=3&tags=&fixable=&issue_uuid=0ce247e1-6c65-338c-f003-40cec3fc5a80

They're already imported from JOSMs combinations.mapcss, although JOSM could add this one as well to be complete with your list:
way[tracktype][surface][tracktype=~/grade[2-5]/][surface!=grass_paver]!.unpaved_surface

@mcliquid
Copy link
Contributor Author

mcliquid commented Jun 1, 2022

Like this one?

Exactly! Thank you for the hint, found it with your help in item=9001&class=9001002
But will it only trigger if grade1 exists with unpaved? I can't find anything with grade2 to grade5 and sealed surfaces. Can this be?

@Famlam
Copy link
Collaborator

Famlam commented Jun 1, 2022

But will it only trigger if grade1 exists with unpaved? I can't find anything with grade2 to grade5 and sealed surfaces. Can this be?

That's what I meant with the suggestion that JOSM (and, via import of their rules, Osmose) could add this rule:
way[tracktype][surface][tracktype=~/grade[2-5]/][surface!=grass_paver]!.unpaved_surface

@mcliquid
Copy link
Contributor Author

mcliquid commented Jun 1, 2022

Thank you so much @Famlam! I've created this ticket inspired by your input: https://josm.openstreetmap.de/ticket/22102
Will the check then be automatically integrated into Osmose, so that we can close this issue here or is there still an effort on the part of Osmose backend afterwards?

@Famlam
Copy link
Collaborator

Famlam commented Jun 1, 2022

I think Frodrigo would've to synchronize it afterwards

@matkoniecz
Copy link
Contributor

JOSM validations checking tags are from time to time imported to Osmose.

@frodrigo
Copy link
Member

frodrigo commented Jun 1, 2022

No, manual. Ping here when is done.

@Famlam
Copy link
Collaborator

Famlam commented Jul 27, 2022

No, manual. Ping here when is done.

Ping ;) it was merged in JOSM

@frodrigo
Copy link
Member

frodrigo commented Aug 9, 2022

No, manual. Ping here when is done.

Ping ;) it was merged in JOSM

Code update done. Will be shipped on next deploy.

@Famlam
Copy link
Collaborator

Famlam commented Sep 8, 2022

I think this issue can be closed as fixed?

@frodrigo
Copy link
Member

frodrigo commented Sep 8, 2022

Yes deployed.

@frodrigo frodrigo closed this as completed Sep 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants