Custom vehicle doesn't work after update to 8.0 about graphhopper HOT 5 CLOSED

I recommend to use our forum so that we can find out if it is an issue or maybe some migration mistake.

In general it looks like you should try to use a piste_nordic boolean encoded value and use this in a custom model instead of these many encoded values and parsers. It is also more flexible and you could let users decide about the speed or priority per request.

from graphhopper.

Regarding this problem here: what is the exact problem you are facing? "Connection not found" or "route not found" or something else? Ensure that the access encoded value is set to true and also the speed encoded value is set to some positive value for the same way. You can put a break point with the debugger and see if it is called at all.

from graphhopper.

I was printing those values and both encoded value is set to true and speed is always 5.0 for this tag.
Exact problem is "PointNotFoundException". "lookup" method in ViaRouting cannot find any snap (and I am sure that in this area there is possible piste route, I have saved coordinates from graphhopper 5.3)

from graphhopper.

Hard to tell without a reproducer. You need to debug if the parser is actually called.

Did you modify the config import.osm.ignored_highways accordingly? Let's move to the forum: https://discuss.graphhopper.com/

Maybe the new way filtering is too strict. Have a look here: #2448 (comment)

from graphhopper.

I did create topic: https://discuss.graphhopper.com/t/custom-vehicle-doesnt-work-after-update-to-8-0/8449
I am sure that TagParsers are called correctly, if I remove all "way.isPiste()" calls and just set speed and access then it works.
I have no idea what "import.osm.ignored_highways" are. Piste tag is set on ways which are not highways, that is the point of this custom vehicle, so maybe some code inside graphhopper is strictly allowing only highway tags?

from graphhopper.