hotosm / HDM-CartoCSS

CartoCSS project focused on the Humanitarian Data Model
Other
138 stars 41 forks source link

Is it intentional that cycleways are rendered like footways? #164

Closed matkoniecz closed 10 years ago

matkoniecz commented 11 years ago

both highway=cycleway and highway=path, highway=footway with bicycle=designed are rendered like normal path.

Obviously, it may be a design decision, but as map is displaying way less important details - I am not sure.

alexrollin commented 11 years ago

Recommendations for rendering are welcome. In my experience this is a great thing, this rendering, because this is really a comment on the size the way in the real world, and for development situations that's important, whereas a bicycle map might care about whether car drivers would be ticketed for driving on the way.

Maybe changing the color slightly for each one? I think that closely related colors would be good, though, in general.

danstowell commented 11 years ago

Remember that this rendering is for a specific purpose - information relevant to humanitarian mapping. I don't know who made the design decisions, but it seems to make sense that cycle-vs-foot is unlikely to be an important feature for such mapping. Rendering too much "extra" detail would obscure the important detail.

westis commented 11 years ago

I think the surface of a path/cycleway/footway is more interesting in HOT contexts, although some kind of differentiation between the three also would make sense (even though combined cycle-/footways are often tagged as highway=path + bicycle=designated + foot=designated, which should render more like a cycleway than a path).

It would make sense to render a paved path/cycleway/footway stronger than an unpaved. I suppose, especially in HOT contexts, that unpaved is default?

alexrollin commented 11 years ago

+1 to paved vs unpaved, but not at the expense of classing them all together as a "small way".

matkoniecz commented 10 years ago

is seems to be WONTFIX

skorasaurus commented 10 years ago

It would make sense to render a paved path/cycleway/footway stronger than an unpaved. I suppose, especially in HOT contexts, that unpaved is default?

A highway tagged with primary/secondary/tertiary/ and maybe unclassified (if I remember correctly) is assumed by default to be paved.

A highway tagged with residential, track, footway, path. cycleway, pedestrian, is assumed to be unpaved.

I can't speak for @yohanboniface - the main designer; but as an assistant, but cycleways are generally tagged as highway=cycleway when ways are dedicated or explicitly to be used for bicycling and the occurrences of these in HOT environments and lower income countries is extremely rare.

This reason and the design principle that we didn't want to add too much information to the map, are two reason why we didn't style the highway=cycleway or other bicycle related tags.