Modify

Opened 13 months ago

Last modified 13 months ago

#23966 new defect

MapCSS validator: Turn:lanes:forward and change:lanes:forward with oneway=* tag is marked as a suspicious combination

Reported by: emrtnsdc@… Owned by: team
Priority: normal Milestone:
Component: Core validator Version:
Keywords: Cc:

Description

https://josm.openstreetmap.de/browser/josm/trunk/resources/data/validator/combinations.mapcss#L316

I can definetly say that turn:lanes:forward and change:lanes:forward are exactly the same as turn:lanes and change:lanes on one-way roads and can be interchanged.

it only becomes a problem when its turn:lanes:backwards and change:lanes:backwards combined with oneway=yes.

I do agree that it is a totally unnecessary suffix, but this in itself should not provoke a suspicious tag.
this list is directly used in osmose.

Attachments (0)

Change History (3)

comment:1 by taylor.smock, 13 months ago

No; I think it should be suspicious. For example, I've had to remap a bidirectional road that was turned into a divided highway. It can be easy to miss a section where there were *:lanes:forward tags when updating the road.

IMO, a stretch of road with oneway=yes + (turn:lanes:forward | change:lanes:forward) should have the turn/change lanes checked since they are likely left over from a conversion of the road from a bidirectional road into a divided highway or just made a oneway with no modifications (example: two roads surrounding a block are made oneways in opposite directions).

comment:2 by emrtnsdc@…, 13 months ago

@taylor.smock so your reasoning being "so we can know the tag could be outdated", that is not the job of the validator.
maybe it could be marked as info instead.

comment:3 by Famlam, 13 months ago

I think that marking it info would defeat the purpose, since in the vast majority of cases it does point to a true suspicious situation:

  1. Either it exists already, in which case there's a large probability of it being an unintended leftover
  2. Or the user isn't aware of best tagging practices
  3. Or the user is under the impression that (s)he is adjusting a two-way road instead.

Making it info-level would hide it from most users (or have them ignore it), thus likely letting cases slip through.

So I'm with Taylor

Like with all QA, there'll always be exceptions and it doesn't necessarily point to an error, it can also just be a suggestion for/pointer to improvement.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as new The owner will remain team.
as The resolution will be set. Next status will be 'closed'.
to The owner will be changed from team to the specified user.
Next status will be 'needinfo'. The owner will be changed from team to emrtnsdc@….
as duplicate The resolution will be set to duplicate. Next status will be 'closed'. The specified ticket will be cross-referenced with this ticket.
The owner will be changed from team to anonymous. Next status will be 'assigned'.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.