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

Indoor Routing #35

Merged
merged 19 commits into from
May 25, 2023
Merged

Indoor Routing #35

merged 19 commits into from
May 25, 2023

Conversation

pablohoch
Copy link
Member

@pablohoch pablohoch commented May 24, 2023

Initial support for indoor routing

  • Extract and store level information from OSM (for edges and areas)
  • C++ Routing API reworked:
    • New find_routes_v2 function
      • Start and destination locations can be specified using either coordinates or OSM type + id, or both
        • Support for OSM type + id is incomplete in this version
      • An optional level can be specified for each input location
      • Routing options can be specified (including options for matching input locations)
    • The old find_routes function remains supported
  • HTTP Routing API updated:
    • Start and destination locations can be specified using either coordinates or OSM type + id, or both
      • For coordinates, use lng and lat (as before), for OSM ids use osm_id and osm_type ("way" or "relation")
      • Support for OSM type + id is incomplete in this version
    • An optional level can be specified for each input location, e.g. {"lat": 12.34, "lng": 45.67, "level": 1.5}
  • Don't allow walking between areas with different levels if they share nodes. To allow walking between such areas, a way must be present (e.g. stairs/escalator).

@pablohoch pablohoch marked this pull request as ready for review May 25, 2023 14:23
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

Successfully merging this pull request may close these issues.

1 participant