Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dedicated bus lanes not getting a referenceId in POST /match/geoms API #3

Open
alephcero opened this issue Jan 11, 2019 · 0 comments
Open

Comments

@alephcero
Copy link

alephcero commented Jan 11, 2019

Like the issue with the Python API, when I try to match a line within a dedicated bus lane, the API doesn't return a referenceId.

I assumed this is realted to the level 6 of sharedstreet which doen't take into account service roads (type 7 does).

In OSM, dedicated bus lanes are tagged as service roads, according to OSM standars:

For dedicated, separate bus tracks, use highway=service, access=no, psv=designated (or psv=yes)

This was the LineString I used to test it (bearingTolerance=50&searchRadius=10) :

{'type': 'FeatureCollection',
 'features': [{'id': '0',
   'type': 'Feature',
   'properties': {},
   'geometry': {'type': 'LineString',
    'coordinates': ((-58.3813759227416, -34.606569952195585),
     (-58.38135557659362, -34.60693988197623))},
   'bbox': (-58.3813759227416,
    -34.60693988197623,
    -58.38135557659362,
    -34.606569952195585)}],
 'bbox': (-58.3813759227416,
  -34.60693988197623,
  -58.38135557659362,
  -34.606569952195585)} 
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant