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.

Sign up for GitHub

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

Jump to bottom

Route-Relation: report issue when 'ref'/'network' of Route-Master is different #18

Closed
osm-ToniE opened this issue May 23, 2018 · 0 comments
Closed

Route-Relation: report issue when 'ref'/'network' of Route-Master is different #18

osm-ToniE opened this issue May 23, 2018 · 0 comments
Assignees
@osm-ToniE
Labels
enhancement New feature or request

Comments

@osm-ToniE
Copy link
Owner

When analyzing a Route-Relation, check for existence of Route-Master(s):

  • a Route-Master should have the same 'ref' value
  • a Route-Master should have the same 'network' value
    report an issue if this is not the case.
    Mainly consider Route-Masters where the 'ref' or 'network' value does not match the wanted criterias of:
  • network_long_regex / network_short_regex
  • refs_of_interest
@osm-ToniE osm-ToniE added the enhancement New feature or request label May 23, 2018
@osm-ToniE osm-ToniE self-assigned this May 23, 2018
osm-ToniE added a commit that referenced this issue May 24, 2018
@osm-ToniE
fix issues #18 and #19
80fedd3 
both fixes done by complete rearrangement in analyze_route_environment() function
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@osm-ToniE osm-ToniE

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@osm-ToniE