I’m trying to enable turn costs in my graphhopper index (to see if it makes my routing times more realistic) and I’m a little confused by the docs. I’m happy to submit patches with better language if someone can help me understand it better.
What’s the difference between prepare.ch.turn_costs=edge_or_node and prepare.ch.turn_costs=edge_and_node in config.yml? as described in https://github.com/graphhopper/graphhopper/blob/master/docs/core/turn-restrictions.md
My other confusion is with config-example.yml, this whole section is confusing me
To enable turn-costs in speed mode (contraction hierarchies) edge-based graph traversal and a more elaborate
pre-processing is required. Using this option you can either turn off the edge-based pre-processing (choose ‘off’),
use edge-based pre-processing for all encoders/vehicles with turn_costs=true (choose ‘edge_or_node’) or use node-based
pre-processing for all encoders/vehicles and additional edge-based pre-processing for all encoders/vehicles with
turn_costs=true (choose ‘edge_and_node’).
question: why doesn’t it mention prepare.ch.turn_costs like the docs do?
question: am I supposed to set this to true or on or something else?
question: how is prepare.ch.edge_based relatd to prepare.ch.turn_costs?