MapMatching Rigidly Follows Traffic Laws
還沒有人認領這個 Issue。
評估
研究方向
從 mapMatching API 開始，檢視相關 issue #849，然後追蹤自訂 OSRM 路線如何透過 Java SDK 傳遞。將所要求的 first responders 路線行為與目前的語音和橫幅指示流程進行比較。完成這項工作需要有一種明確定義且受支援的方式來產生這些指示，同時不拒絕違反交通法規的路線。
由索引模型根據 Issue 內容生成。
描述
The mapMatching API doesn't work with routes that disobey traffic laws. We are providing routes for first-responders (fire, law-enforment, EMS, etc.) who don't always need to obey traffic laws so this is causing issues.
Here's an example (the image on the left is the recommended route; the image on the right is what is returned from mapMatching, not allowing the illegal left turn):
We are generating routes from our own OSRM server using custom profiles and want to use mapbox-navigation-ios for the navigation frontend. As noted in this tutorial and https://github.com/Project-OSRM/osrm-text-instructions/issues/269#issuecomment-449417857 the recommended approach is to use the mapMatching api to add voice and banner instructions to the custom generated route object (orsm-text-instructions could be used to add the simple text instructions but not the voice and banner instructions).
We don't even need the "matching" part of the mapMatching api... we already have the precise road geometry, we're not snapping fuzzy gps coordinates to a road network. We only need the voice and banner instructions but there doesn't seem to be a way to get just these without using the mapMatching API.
We could write our own package to produce the voice and text instructions based on the route object (returned from orsm) and the simple text instructions (returned from osrm-text-instructions) but it seems needless considering this is something already implemented by Mapbox but not available in any way (open source or api).
We plan to reach out directly to Mapbox support to talk about this but I wanted to post a public issue here so that other's could add to the discussion if they have similar issues or possible solutions.
related to #849
- 主要語言
- Java
- 星號
- 438
- 分支
- 117
- PR 合併指標
- 30 天內沒有已合併 PR
環境準備
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
mapbox/mapbox-java 的其他 Issue
-
難度 2/5 1-3 小時 新手友好度 72/100
mapbox/mapbox-java#1640 ·
-
難度 4/5 3-5 天 新手友好度 55/100
mapbox/mapbox-java#1635 ·
-
難度 5/5 一週以上 新手友好度 15/100
mapbox/mapbox-java#1619 ·
-
Mapbox-java incompatible with gson 2.13.0 and up - call to internal GSON classes that were renamed未關閉
難度 2/5 1-3 小時 新手友好度 48/100
mapbox/mapbox-java#1614 · 2 則留言 · 1 個 reaction ·
-
難度 5/5 一週以上 新手友好度 20/100
mapbox/mapbox-java#1612 · 1 個 reaction ·
查看 mapbox/mapbox-java 的全部 Issue
相似的 Issue
-
bug
難度 2/5 1-3 小時 新手友好度 78/100
-
component/zeebe kind/bug
難度 1/5 1 小時以內 新手友好度 90/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 78/100
UniversalMediaServer/UniversalMediaServer#6356 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 88/100
refinedmods/refinedstorage2#1414 · 1 則留言 ·
-
難度 1/5 1-3 小時 新手友好度 88/100
yegor256/rultor-image#76 · 1 則留言 ·