-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Render surface=unpaved paths, tracks and highways like is done with dirt/gravel #367
Comments
You're right it should be rendered but how ?
Unpaved just say it's not quality road bike, shall we use trekking, mtb, unknown ? Example : https://www.openstreetmap.org/way/189303200#map=15/48.7582/2.7316 |
I would say definitely trekking/gravel unless there is a smoothness tag set to very bad or worse. |
Definitely ? Well, unpaved can mean mud ! |
From my experience unpaved is used broadly for roads that have no asphalt but usable by normal cars. So trekking and gravel bikes appear appropriate. The same way with paved we assume smooth tarmac and road bikes. However paved and unpaved are both rather generic tags. |
Any progress on this ? Seems very simple to implement and it would be SOOOOO useful for people doing gravel riding. Until unpaved roads are properly rendered the COSM map does not allow to plot a gravel ride. |
We can go with paved as first quality road (road bike) because the wiki says But for unpaved «Using more specific value is always preferable as surface=unpaved may mean everything from surface=compacted to surface=mud. » is clear. |
In surface sql code there is a bug :
Bug visible with https://www.openstreetmap.org/way/458050536#map=17/48.66085/2.84911 |
I know in my area and pretty much everywhere in north america, the unpaved value is used for roads that are not asphalt, and then sometimes something more specific is used. This is certainly NOT equivalent to unknown. It means it is known that asphalt is NOT used. Which is the main thing to know about road surface in reality. So please make sure surface=unpaved is rendered in a way that can be distinguished from paved and asphalt or no surface value at all. We cannot change the thousands if not millions of unpaved tags out there. People use this value a lot because the other values, dirt and gravel are not always adequate, most roads are really made of a mix of dirt, gravel and sand. It is essential that the rendering show surface=unpaved roads. Thanks.
… On Jun 3, 2020, at 16:27, Florimondable ***@***.***> wrote:
We can go with paved as first quality road (road bike) because the wiki says
«A feature that is predominantly paved; i.e., it is covered with paving stones, concrete or bitumen. This value gives only a rough description; use a more precise value if possible.»
But for unpaved «Using more specific value is always preferable as surface=unpaved may mean everything from surface=compacted to surface=mud. » is clear.
I'd set it as unknown surface
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#367 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIGA7HGIJTY6WRL2K2MFQXTRU2W4NANCNFSM4NEB6VHQ>.
|
I should have added that clearly in my area, surface=unpaved is best associated with cyclocross in your logic, which is closest to gravel bikes. The fact that a way is associated with MTB has more to do with smoothness than surface. My suggestion is for highway={primary, secondary, tertiary, residential, unclassified} default surface=unpaved to cyclocross. If it good for cars it should be fine on a gravel bike. For highway={track, path} you can refine your selection using smoothness and pick MTB if smoothness is very bad or worse. In practice gravel bikes and cyclocross bikes can handle quite a bit.
Thanks.
… On Jun 3, 2020, at 16:36, Florimondable ***@***.***> wrote:
In surface sql code there is a bug :
the final ELSE should be 'unknown' not NULL, otherwise real unknown surface is not rendered as such (or we can use NULL value).
And a typo with 'bad' in surface.
WHEN tags->'smoothness' IS NULL AND tracktype IS NULL AND surface IS NULL
THEN 'unknown'
WHEN tags->'smoothness' IN ('horrible', 'very_horrible', 'impassable')
THEN 'mtb'
WHEN tags->'smoothness' IN ('bad', 'very_bad')
THEN 'cyclocross'
WHEN tracktype IN ('grade4', 'grade5')
THEN 'mtb'
WHEN tracktype IN ('grade2', 'grade3')
THEN 'cyclocross'
WHEN surface IN ('bad', 'pebblestone', 'dirt', 'earth', 'grass', 'grass_paver', 'gravel_turf', 'ground', 'mud', 'sand')
THEN 'mtb'
WHEN surface IN ('concrete:lanes', 'concrete:plates', 'gravel', 'sett', 'unhewn_cobblestone', 'cobblestone', 'wood', 'compacted', 'fine_gravel', 'woodchips')
THEN 'cyclocross'
ELSE NULL
END AS surface_type,
Bug visible with https://www.openstreetmap.org/way/458050536#map=17/48.66085/2.84911 <https://www.openstreetmap.org/way/458050536#map=17/48.66085/2.84911>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#367 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIGA7HEGH7PUQZ5ECRC6PCLRU2X3LANCNFSM4NEB6VHQ>.
|
Is this very useful yet simple to implement enhancement been put on the back burner ? Anybody doing gravel cycling, which is a big thing right now, is in need of this simple fix. |
Fixed, and added an explicit test case for surfaces which are to be considered as good for road bikes then (based on https://github.com/abrensch/brouter/blob/master/misc/profiles2/trekking.brf#L69).
Fixed
Done
Sorry, but CyclOSM is not about North America, or anywhere else in the world. It is meant to be global. Looking around, I found that Therefore, next version will draw |
If I got the current situation right, if a path or track is tagged with surface=dirt, gravel, it is rendered with a sort of dash pattern. However if it is tagged with surface=unpaved it is not, it just renders with a regular line. I would suggest you process unpaved just like dirt or gravel. In my area unpaved is used a lot and it would be useful to see that.
I would think the same request applies to other type of highway (minor, tertiary, residential). Given the rise of gravel biking it is very useful to render the surface={unpaved, dirt,gravel} so one can see that when planning a route. Thank you.
The text was updated successfully, but these errors were encountered: