So I’ve outlined the context of my question in this short video. All of my data layers are derived from OSM data, and all roads have associated OSMIDs.
First, can one use data more precise/granular than the OpenStreetMap Way IDs (OSMIDs) for the OpenRouteService greenindex weighting csv? Since the GreenIndex weighting csv only takes a list of:
- I quickly realized I need to split hundreds of roadways on OpenStreetMap in order to properly weight the small segments of roads I’m interested in having in my green weighting file. In other words, there are ~1/2 mile long roads spanning many many blocks (identified through one OSM ID). So if I wish to weight just a small segment of that road for bicycle routing, I would need to use the “OSM Split tool” to re-idenitify that segment of road with a unique OSM Way ID. Not sure if this issue has come up before? @nils?
Second, if I want to negatively weight a road, to deter routing, do I just use a negative value from 0 to 1, in that weighting file?
The most comprensive documentation I’ve found on the green index weighting file been from here which states:
factor: Values range from
0equals normal routing.
1will prefer ways through green areas over a shorter route.
If additional documentation on custom weighting profiles I’d gladly consume it. @nils curious on thoughts on this! Thanks in advance.