Modify ↓
Opened 6 years ago
Last modified 9 months ago
#15038 new enhancement
compare route_ref tag to the list of actually served lines/route relations
Reported by: | Polyglot | Owned by: | darya |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Plugin pt_assistant | Version: | |
Keywords: | Cc: |
Description (last modified by )
The functionality to gather which lines serve a give stop is already present. Please add a rule that compares this to route_ref, if a route_ref tag is present on the stop.
If a route_ref is not present, we don't want to compute it automatically by the routes traversing there, since we never know if all routes are correctly mapped.
Attachments (0)
Change History (4)
comment:1 Changed 6 years ago by
Component: | Core → Plugin pt_assistant |
---|---|
Owner: | changed from team to darya |
Type: | defect → enhancement |
comment:2 Changed 3 years ago by
Description: | modified (diff) |
---|
comment:3 Changed 3 years ago by
comment:4 Changed 3 years ago by
Note: See
TracTickets for help on using
tickets.
I get an informational warning (other)
PT: Refs of the routes do not match with the route_ref tag of the primitive
with pt_assistant (2.1.10-80-g7d9bba3).The problem with this rule among others is that it needs to be run only for new objects or objects within downloaded areas. Otherwise it should only warn about if the
ref
of the route relation is not part of the value ofroute_ref
.Working with incomplete data like downloading only a relation without any members first and then all its members gives many misleading, incorrect false positives, see #4142.