"Routing Service can't find end point. Please redefine"

I tried it out, gpx attached.If you investigate by trying small parts of routings in the problematic section (not taking the coast route), you see that probably OSM data is the cause for this particular problem and probably of the original described problem in this issue. In the screenshot you can see that there is a small gap in the highway displayed south-east of the bridge over the Carpinteria Creek direction south and if the destination point is set right behind this gap, the routing algorithm does not want to cross that gap.

So this is just the beginning of investigation about the OSM data. As the wrong routing is probably occuring at several other places on the costal route, it could be need some effords to correct it for OSM contributors. Or the LoRouting needs to be adapted to the not optimal OSM data. Graphhopper as Routingservice in Locus does not show the problem.

I did some more research im OSM (by comparing the 101 at the different places) and found that in the name of "ventura highway" the 101 has a classification of parametet "vehicle" (in German screenshot: "Fahrzeuge") which looks not valid against the usual values explained in https://wiki.openstreetmap.org/wiki/Key:vehicle

I will now see if I can change the status of this parameters to a commonly accepted value ("openly accessible" or something like this should be the correct value). But as other routing services rely on other parameters to see if a street can be used, probably LoRouter developers can have a look at how to handle this example the best way (as it could ocvir for oter locations, too).

This is well spotted druki. The primary problem is the unfortunate, unsupported and indeed totally wrong tag motor_vehicle=no|yes|yes. At the moment I am not able to tell how exactly is this "|" sign which normally means OR handled deep inside programs that build routing data. I will have a look as I want to understand this problem into detail. But it may be easier just to delete 24 usages or this mapping worldwide.

https://overpass-turbo.eu/?w="motor_vehicle"%3D"no|yes|yes"+global&R

https://overpass-turbo.eu/?w="motor_vehicle"%3D"no|yes|yes|yes"+global&R

I can not confirm a difference between LoRouter offline and LoRouter online in this case. Both take the "mountainroute". But earlier in thread it was mentioned "web version of OSM" works. So this is an other routing logic as the LoRouter.

Both online and offline LoRouter and external Brouter have the same behavior - take the mountain road.

Sorry, yes, the way I tested online was via https://www.openstreetmap.org/ - it routes along the coast as expected with a start of santa barbara, ca & and end of ventura, ca.

Unfortunately my main requirement is offline routing/creation/editing that works in unknown areas (not this particular area, this was just a test run.)

I think it may be that anything openstreetmaps based will be unacceptable unless I ran into the one extremely popular highway with bad data.

@demca:
you should note that this is an outdoor app. For car it could be so it doesn't work perfectly. These bugs should always have a low prio. What is important is that cycling and hiking works well.
I always use Google Maps for car. They are at car specialists. Locus also offers a quick switch from Locus to maps. I use that often. Find me a free parking (Locus shows that) near my tour and say navigate with Maps.
The other way around also works very well now. Find me on the road a cafe on Maps and share it with Locus.

Believe it or not.. Locus is actually one of the best apps for car (or motorcycle, in my case) offline usage. the key is OFFLINE.. much of the entire western US has poor to no cell coverage, so you cannot rely on having connectivity. Many times I plan a route in the morning, end up 300 km away and realize I need to replan my route with no signal.

Google maps is almost the exact opposite of what I want: online, fastest routing, doesn't follow the route I want it to (usually backroads/curvy roads/dirt roads.) You can download chunks of offline map data, but it is clunky and not easy to get all the chunks you need if you're crossing 1000s of kms.

Unfortunately the only real alternative are Garmin dedicated devices, and their products get worse every year. But their maps and POI are pretty solid. Ideally Garmin should just license their map data to someone else, so they could write a decent Android/IOS app!

oh dear, always thought the USA is a very progressive country. With motorcycle knows user 0709 quite well. I think he takes kurviger.de for planning and then navigates with Locus. He is also in the forum, possibly times write to.

@demca - this particular problem should be solved both for online and offline routing soon, just by the App update. If there is more obvious blunt errors like this, please do report them.