Modify

Opened 6 weeks ago

Last modified 5 weeks ago

#24053 needinfo enhancement

Validator: Detect invalid barrier nodes

Reported by: anonymous Owned by: anonymous
Priority: normal Milestone:
Component: Core validator Version:
Keywords: barrier Cc:

Description (last modified by Famlam)

Barrier tags must not be used on junction nodes connecting multiple ways. https://wiki.openstreetmap.org/wiki/Key:barrier#How_to_map_barrier_nodes

Such invalid barriers could be detected by the validator:

  • a node has a barrier tag
  • the node belongs to more than one way with a highway tag

Attachments (0)

Change History (3)

comment:1 by Famlam, 6 weeks ago

Description: modified (diff)

Note that this can be fine with some barriers, e.g. bollards. And I assume you mean either three connecting ways or two connecting ways where at least one way isn't an end node.

Osmose has such a check, see sql41. Might be useful to see that implementation in case someone wishes to implement this.

comment:2 by skyper, 5 weeks ago

Owner: changed from team to anonymous
Status: newneedinfo

There is already a warning see combinations.mapcss line 122-147 though it makes some assumptions and excludes some highway=*, see #20742.
Please, provide real world examples where you expect to get a warning but current implementation does not catch it.

comment:3 by skyper, 5 weeks ago

Keywords: barrier added

Modify Ticket

Change Properties
Set your email in Preferences
Action
as needinfo The owner will remain anonymous.
as The resolution will be set. Next status will be 'closed'.
to The owner will be changed from anonymous to the specified user. Next status will be 'new'.
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 remain 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.