Open-Harbor/osrm-backend
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 3 Wiki Activity
38fef77d70
osrm-backend/features/guidance/destination-signs.feature

42 lines
3.1 KiB
Gherkin
Raw Normal View History

Basic destination sign handling. This first part in our Exit Sign / Destination Sign quest re-wires the `destination=` and `destination:ref=` tag to the `ref=` tag (in case it's the highway does not already have a `ref=` tag). Doing some analysis on both Berlin and San Francisco it looks like this will add a couple of thousand `ref=` tags that we will announce in guidance. References: - https://github.com/Project-OSRM/osrm-backend/issues/2267#issuecomment-214771682 - http://wiki.openstreetmap.org/wiki/Key:destination - http://wiki.openstreetmap.org/wiki/Proposed_features/Destination_details
2016-04-27 07:24:25 -04:00
@routing @guidance
Feature: Destination Signs
Background:
Given the profile "car"
Scenario: Car - route name assembly with destination signs
Given the node map
| a | b |
| c | d |
| e | f |
| g | h |
| i | j |
| k | l |
| m | n |
Guard against mis-tagging: only use destination tag in combination with oneway tag
2016-04-29 06:28:03 -04:00
| o | p |
Cucumber test for destination:ref and no destination=*
2016-05-02 05:29:14 -04:00
| q | r |
Basic destination sign handling. This first part in our Exit Sign / Destination Sign quest re-wires the `destination=` and `destination:ref=` tag to the `ref=` tag (in case it's the highway does not already have a `ref=` tag). Doing some analysis on both Berlin and San Francisco it looks like this will add a couple of thousand `ref=` tags that we will announce in guidance. References: - https://github.com/Project-OSRM/osrm-backend/issues/2267#issuecomment-214771682 - http://wiki.openstreetmap.org/wiki/Key:destination - http://wiki.openstreetmap.org/wiki/Proposed_features/Destination_details
2016-04-27 07:24:25 -04:00
And the ways
Guard against mis-tagging: only use destination tag in combination with oneway tag
2016-04-29 06:28:03 -04:00
| nodes | name | ref | destination | destination:ref | oneway | # |
| ab | AB | E1 | | | yes | |
| cd | CD | | Berlin | | yes | |
| ef | EF | | Berlin | A1 | yes | |
| gh | | | Berlin | A1 | yes | |
| ij | | | Berlin | | yes | |
| kl | KL | E1 | Berlin | A1 | yes | |
| mn | MN | | Berlin;Hamburg | A1;A2 | yes | |
| op | OP | | Berlin;Hamburg | A1;A2 | no | mis-tagged destination: not a oneway |
Cucumber test for destination:ref and no destination=*
2016-05-02 05:29:14 -04:00
| qr | QR | | | A1;A2 | yes | |
Basic destination sign handling. This first part in our Exit Sign / Destination Sign quest re-wires the `destination=` and `destination:ref=` tag to the `ref=` tag (in case it's the highway does not already have a `ref=` tag). Doing some analysis on both Berlin and San Francisco it looks like this will add a couple of thousand `ref=` tags that we will announce in guidance. References: - https://github.com/Project-OSRM/osrm-backend/issues/2267#issuecomment-214771682 - http://wiki.openstreetmap.org/wiki/Key:destination - http://wiki.openstreetmap.org/wiki/Proposed_features/Destination_details
2016-04-27 07:24:25 -04:00
When I route I should get
Add destinations API feature
2016-05-26 18:47:46 -04:00
| from | to | route | destinations | # |
| a | b | AB (E1),AB (E1) | , | |
| c | d | CD (Berlin),CD (Berlin) | Berlin,Berlin | |
| e | f | EF (A1: Berlin),EF (A1: Berlin) | A1: Berlin,A1: Berlin | |
| g | h | , | A1: Berlin,A1: Berlin | |
| i | j | , | Berlin,Berlin | |
| k | l | KL (E1),KL (E1) | A1: Berlin,A1: Berlin | |
| m | n | MN (A1, A2: Berlin, Hamburg),MN (A1, A2: Berlin, Hamburg) | A1, A2: Berlin, Hamburg,A1, A2: Berlin, Hamburg | |
| o | p | OP,OP | , | guard against mis-tagging |
| q | r | QR (A1, A2),QR (A1, A2) | A1, A2,A1, A2 | |
Reference in New Issue Copy Permalink