Opened 10 years ago
Closed 5 years ago
#10429 closed defect (wontfix)
false warnings about role:"number" and forward/backward:stop for public transport routes
| Reported by: | skyper | Owned by: | team |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Core validator | Version: | latest |
| Keywords: | public-transport-v1 role | Cc: | simon04 |
Description
Since adding public_transport:version=* I get tons of warning about stop:[number] and similar though it is written on the wiki for years that colon separated numbers behind the role is allowed.
For version 1 forward/backward are also valid.
Attachments (2)
Change History (12)
follow-up: 2 comment:1 by , 10 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → needinfo |
comment:2 by , 10 years ago
| Owner: | changed from to |
|---|---|
| Status: | needinfo → new |
Replying to Don-vip:
can you please attach a sample file? Thanks.
Please, just have a look at my last changeset. Should be enough.
follow-up: 4 comment:3 by , 10 years ago
I will tomorrow if I find some time, but please note:
- we have a thousand tickets to look after and a small .osm extract is the fastest way for us to understand and fix a problem. For example, #10416 was very easy/fast
- objects listed in a changeset are subject to further change between the time you create a ticket and the time we fix it. It can be be minutes or years... ;)
comment:4 by , 10 years ago
Replying to Don-vip:
I will tomorrow if I find some time, but please note:
- we have a thousand tickets to look after and a small .osm extract is the fastest way for us to understand and fix a problem. For example, #10416 was very easy/fast
- objects listed in a changeset are subject to further change between the time you create a ticket and the time we fix it. It can be be minutes or years... ;)
Sorry, was a bit lazy and thought my description and Relation:route#Members is enough. Think it is possible to download a specific version of an object but you are right that it makes it more complicated and time consuming.
I attached as "version=2" example relation/69434 as Bus_12.osm.gz and as "version=1" example relation/68320 as Bus_7208.1.osm.gz.
comment:5 by , 10 years ago
| Cc: | added |
|---|
Simon: where is public_transport:version used? I don't find any reference to it besides the validator warning asking for its presence?
comment:6 by , 10 years ago
public_transport:version should be used to find the proper tests. Without it the tests about proper roles are not run at all, but I did not test if it the value makes any difference, so far.
comment:7 by , 10 years ago
| Summary: | false warnings about role:"number" and forward/backward for public transport routes → false warnings about role:"number" and forward/backward:stop for public transport routes |
|---|
Replying to skyper:
For version 1
forward/backwardare also valid.
I meant `forward:stop[:number] but the above is true, as well.
comment:8 by , 9 years ago
| Keywords: | public-transport-v1 added; public transport removed |
|---|
comment:9 by , 8 years ago
The roles are documented for ages at the wiki and it is the only way to get JOSM to sort the relation the right way.
I get tons of these warnings (~ 90% of all warnings) which makes it hard to find warnings about other relation types and real problems.
comment:10 by , 5 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
The use of numbers is discourage meanwhile, therefore nothing to do.
can you please attach a sample file? Thanks.