Hi ORS Community,
Here in Australia, similar to many other countries, our roads have specific ratings which are dependent on the size of your vehicle, weight it can carry, different axle groupings, different trailer couplings, etc, etc.
As a reference, an example of just one of these grouping charts can be found here:
https://www.mainroads.wa.gov.au/globalassets/heavy-vehicles/getting-a-permit/tri-drive/tri-drive-prime-mover-trailer-combinations-vehicle-categories-and-descriptions.pdf
However, the government has been progressive enough to give open access to the Spreadsheet, KML or Shape files for each one of these restricted networks!
For reference, the overall map & an example data set (for one restricted network) follows:
https://mrwebapps.mainroads.wa.gov.au/hvsnetworkmap
Is it possible to have ORS calculate routes with respect to these individual restricted networks?
The “hackiest” method I can think up (that might actually work) would be literally to just have numerous different ORS instances running which are all pointing to manual subset .pbf files that represent each one of these restricted road networks, then increase the snapping/search radius and voila. However, this is obviously far, far, faaaaar from optimal - it would require hundreds of different instances of ORS to be running.
As a more logical starting point, leveraging ORS profiles seems to be the proper way to figure out a way to have this custom pathing functional. Would it be possible to create a profile for each “restriction classification” which when called will tell ORS to only calculate routes using a subset of the overall .pbf file; a subset which is somehow determined by the Shape files provided by the government?
It seems like this functionality is already somewhat present within ORS, as it’s possible to toggle on restrictions = “true” in the app.config file. However, I couldn’t find many details on what this functionality is actually doing on the backend (and I’m not skilled enough to trace back the code).
Hopefully this all makes sense, and hopefully I’m not re-posting an already asked question (had a search and couldn’t find anything too similar).
TL;DR - is it possible to essentially only calculate the route on some smaller subset of the overall road network (.pbf file), where this subset is is different dependent on which route profile you make the API call with? (And, each profile’s subset of the network is predetermined by some Shape file).
Any help or just information on how this functionality might work if it’s already possible (links to resources to build my understanding), or if it’s not possible functionality tips of what might be the best way to go about beginning to implement it, would be very, very, verrry appreciated.
Really grateful for the amazing community this product has gathered - and ORS is a truly awesome toolkit - everyone who’s contributed should be very proud in what they’ve built!
Hopefully this wasn’t too much incoherent babbling - haha
Cheers,
Troy