Opened 6 months ago

Last modified 6 months ago

#21966 new enhancement

[Patch] Allow cardinal directions as roles in road routes

Reported by: ZLima12 Owned by: team
Priority: minor Milestone:
Component: Internal preset Version:
Keywords: road route relation role Cc:

Attachments (0)

Change History (5)

comment:1 Changed 6 months ago by ZLima12

Keywords: road route relation preset added

comment:2 Changed 6 months ago by skyper

Component: unspecifiedInternal preset
Keywords: role added; preset removed
Summary: Allow cardinal directions as roles in road routes[Patch] Allow cardinal directions as roles in road routes
Version: tested

These roles are only for route=road relations and should not be mixed with e.g. forward/backward, am I right?

I'd prefer an own preset for these route relations and similar to #20731 we should add validator rules to warn about a mix of both concepts within a relation.

comment:3 Changed 6 months ago by 1ec5

Cardinal direction roles are incompatible with forward/backward roles. Every route relation that currently has a forward or backward role for one of its members would eventually need to be refactored into two subrelations, one for each direction, in order to communicate the cardinal direction to a router. (Routers use the cardinal direction in guidance instructions because they’re so important for navigation in the countries that use them.)

How would the preset work? The cardinal direction roles aren’t the preferred roles for any network in particular. They‘re only a crude first pass, compared to PTv2-style subrelations, that are acceptable because less experienced mappers would find it difficult to perform that refactoring every time they encounter a short dual carriageway along an otherwise single-carriageway route.

comment:4 Changed 6 months ago by ZLima12

Just ran a homemade script on every road route that has a network beginning with US: (47246 of them). Was looking for statistics on how they were mapped in the US: for member roles, do people use forward/backward more, or north/south/east/west more? Here's the results:

  • All members have empty role: 37870
  • forward/backward`: 6176
  • north/south/east/west: 1673
  • Mixed between forward/backward and north/south/east/west: 923
  • All relations (presumably superroute): 311
  • >=1 member has a role different from those mentioned: 291
  • Everything else (invalid, probably): 2

comment:5 Changed 6 months ago by ZLima12

Those 923 mixed relations should rightfully have a warning issued by JOSM.

Modify Ticket

Change Properties
Set your email in Preferences
as new The owner will remain team.
as The resolution will be set.
to The owner will be changed from team to the specified user.
The owner will change to ZLima12
as duplicate The resolution will be set to duplicate.The specified ticket will be cross-referenced with this ticket
The owner will be changed from team to anonymous.

Add Comment

E-mail address and name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.