| Note | # | ⏱️ Last updated | Event | Contributor | Comment |
|---|---|---|---|---|---|
| 5171687 Category: CoMaps | 1 | ~ 7 months ago | opened | Jbell4588 ♦3 | "#2981" OSM snapshot date: 2026-02-07T17:28:58Z POI has no name POI types: addr:interpolation-odd #CoMaps android 2026.02.09-4-Google |
| 2 | ~ 3 months ago | closed | CurlingMan13 ♦54,417 | added | |
| 4975313 Category: Unknown | 1 | ~ 1 year ago | opened | --- | The house number of this lot is 27744. |
| 2 | ~ 9 months ago | closed | Jbell4588 ♦3 | Confirmed and corrected | |
| 4587029 Category: unknown | 1 | ~ 1 year ago | opened | John1946@ ♦1 | Edmonds to Kingston Ferry does not seem to connect with roads. Route always takes the long way around whereas the Seattle to Bainbridge ferry route does work. |
| 2 | ~ 1 year ago | commented | khevans ♦22 | Did you resolve this? I noticed that you made an edit on the route and I tried the 3 mappers in iD and they now route via the Kingston-Edmonds ferry | |
| 3 | ~ 1 year ago | commented | John1946@ ♦1 | It's not resolved. In OSMAND when I started a track on Bainbridge Island to Kingston then to Edmonds via ferry it worked fine. As soon as I tried to extend the track to Lake Forest Park - Wa Hwy 522 the program re-routed back across the ferry to Bainbridge Island and took the BI ferry to Seattle to get to Lake Forest Park. The problem lies on the Edmonds ferry dock. There was a gap between the road on the dock and the road exiting the dock. I tried to connect the two road ends but it didn't solve the problem. I think someone with way more expertise than I should take a closer look. I just tried the track again in OSMAND and it still routes back to Bainbridge Isl. and Seattle. | |
| 4 | ~ 1 year ago | commented | khevans ♦22 | I opened an issue on the OsmAnd Github: https://github.com/osmandapp/OsmAnd/issues/22306 and it looks like their team will take a deeper look at the problem. | |
| 5 | ~ 10 months ago | commented | Natfoot ♦1,111 | per this note. using my favorite router. if I move the start point beyond the Kingston Ferry Dock (in the water) it will route through Edmonds. but as soon as I place it on the Kingston dock it goes around. now after looking at the Kingston Dock it is the only one without reversible bridge decks leading to the ferry. I will say that if I place the end point in the water it will navigate to the water point through the Kingston Dock. So there is something more going on here. | |
| 6 | ~ 10 months ago | commented | Natfoot ♦1,111 | When I say go around it does not use any of the ferries. | |
| 7 | ~ 10 months ago | commented | Natfoot ♦1,111 | with a turn of events to this note my favorite router works just fine on the app. | |
| 8 | ~ 9 months ago | commented | Jbell4588 ♦3 | I tested current Comaps and OsmAnd web routing, placing points directly on the Edmonds and Kingston dock ways, routing points located close inland and offshore, and including multi-leg routes extending inland. I was unable to reproduce the ferry avoidance behavior. For context, Comaps uses a GraphHopper-based router, and OsmAnd web uses a OsmAnd specific routing backend. This suggests the issue may be resolved in current OSM data or may have been router-specific or version-dependent. | |
| 9 | ~ 9 months ago | commented | pwbriggs ♦1,039 | Hmm. Does it also avoid all ferries if you replicate this experiment on another ferry line? What if you set the start location to a bridge-free island (like Vashon)? Maybe that will help narrow down the issue. | |
| 10 | ~ 17 days ago | closed | Natfoot ♦1,111 | I have seen no change in this and it looks to be an app based problem. |