rendering problem of cycle lanes

[dr.kludge.gm@…]

I generally try to stay current with JOSM releases. However, I went back to 7287 because of the 7347 release. I think ​http://josm.openstreetmap.de/changeset/7330/josm is unfortunate because MapCSS does not match the XML version. Where I feel MapCSS is a defect is in the treatment of cycle lanes. The braided colors of cycle lanes made for a quick scan of the highway having the cycleway tag or not. It appears to me that a dashed relationship rendering has replaced the cycleway in importance. The relationship rendering is a good idea but its just not that important to me. I'll be happy to fully embrace MapCSS once it finally matches the orignal XML defaults. Until then the XML defaults should remain in the releases until the MapCSS is complete.

[Don-vip]

Can you please attach a small dataset showing the problem ? Thanks.

[bastiK]

Yes, the rendering of cycle lanes has been changed: It now visualizes if the cycle lane is on the left, the right or on both sides of the highway. This additional information is an improvement and we will not outright revert to the previous state.

Could you explain the problem in more detail, I do not understand, what the issue with the new rendering is, exactly? Any ideas how the new rendering can be further improved, so it works better for your use case?

[Klumbumbus]

If you don't want to see the cycleway lane/track dashes, you can use an additional mapcss file with the following content:

way.lR::core_cycleway,
way.tR::core_cycleway
{
	width: 0;
}
way[prop("tL","core_cycleway")]::core_cycleway2,
way[prop("lL","core_cycleway")]::core_cycleway2
{
	width: 0;
}

In the list of mappaint styles in the preferences this style should be below the internal style (which means higher priority).