Makes sense to me.
I would point out that the client does a have a dirt road road setting. I had been assuming that this setting would still apply to the renamed "unpaved" road type and would be changed to be the unpaved roads settings. If "unpaved" become a checkbox property, I would still think that setting should apply so that user can decide whether they want to be routed over unpaved roads.
We would then need an additional setting as to whether the user wants to include "4x4/Offroad" roads if these are ever to be included in routes.
The other issue that comes to mind is that I have seen in reference to unpaved roads are roads that are only open seasonally. Is this something that should be addressed within the options for these road types, addressed with time based restrictions, or addressed manually as the roads open and close.
I would point out that the client does a have a dirt road road setting. I had been assuming that this setting would still apply to the renamed "unpaved" road type and would be changed to be the unpaved roads settings. If "unpaved" become a checkbox property, I would still think that setting should apply so that user can decide whether they want to be routed over unpaved roads.
We would then need an additional setting as to whether the user wants to include "4x4/Offroad" roads if these are ever to be included in routes.
The other issue that comes to mind is that I have seen in reference to unpaved roads are roads that are only open seasonally. Is this something that should be addressed within the options for these road types, addressed with time based restrictions, or addressed manually as the roads open and close.
Re: Unpaved as a checkbox instead of road type?