Hmmh, it could be that we do not allow cars on highway=pedestrian probably regardless of vehicle=yes etc. But if that is the reality then we need to make it working, somehow
Here is the line which returns “no access”: https://github.com/graphhopper/graphhopper/blob/master/core/src/main/java/com/graphhopper/routing/util/CarFlagEncoder.java#L205
Maybe we just need to move the getFirstPrio call a bit early, but unit test (failings) will guide you
BTW: thanks for opening this issue again, I’ve now disabled auto closing of topics here, which is too often not nice.
1 Like
Hi,
We’ve found another road with the same issue.
Here “Storetorv” is listed as “highway: pedestrian” but it does have “vehicles: yes”, yet it’s excluded from car navigation. Just to confirm is this the code that controls this?
import com.graphhopper.reader.ReaderWay;
import com.graphhopper.routing.ev.*;
import com.graphhopper.routing.util.FerrySpeedCalculator;
import com.graphhopper.routing.util.TransportationMode;
import com.graphhopper.routing.util.WayAccess;
import com.graphhopper.util.PMap;
import java.util.*;
public class CarAccessParser extends AbstractAccessParser implements TagParser {
protected final Set<String> trackTypeValues = new HashSet<>();
protected final Set<String> highwayValues = new HashSet<>();
protected final BooleanEncodedValue roundaboutEnc;
public CarAccessParser(EncodedValueLookup lookup, PMap properties) {
this(
lookup.getBooleanEncodedValue(VehicleAccess.key("car")),
lookup.getBooleanEncodedValue(Roundabout.KEY),
properties,
It seems we did not consider this when we did a refactoring for an earlier version (7.0), I think.
The access code is the correct one @Sam_Ruston but there is another pre-filtering mechanism which is the problem here: https://github.com/graphhopper/graphhopper/blob/c4c07cc7f17f999fe3ed25c670bb178cb02701f4/config-example.yml#L187
We’ll change the config for production and it should be fixed next week.
1 Like