You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I totally agree. This has been in the to-do list for long and will be tackled with the next batch of work related to "ways" (there are several other issues including road signs, signals, lanes...).
Resolving this, however, is not as easy as changing a style definition, because way geometry has to be cut where outlines intersect and reassigned to the container area (and hopefully, in the future, add ramps and other area and kerb-related transitions).
Also, the aim is to keep the path geometry so it can be inspected as a separate object for OSM workflows (even if not visually different), while keeping the possibility of merging the geometry completely for more real-time usage.
currently highway=footpath is cut out of a highway=footpath that is an area
it should look something like this:
adding a footpath as a line on top of a footpath area is common practice, as it makes routing easier for map apps
https://3dsmaps.com/3d/@51.7506157,-0.2368136,24a,35y,241.4h,45.49t
The text was updated successfully, but these errors were encountered: