Skip to content
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

Bridges on service=driveway #269

Closed
mmd-osm opened this issue Nov 24, 2013 · 4 comments
Closed

Bridges on service=driveway #269

mmd-osm opened this issue Nov 24, 2013 · 4 comments

Comments

@mmd-osm
Copy link

mmd-osm commented Nov 24, 2013

Line widths for ways tagged as highway=service and service=driveway seem to increase a bit when a bridge=* tag is added. This looks odd on the map as different driveway parts no longer fit together nicely.

Example:

http://www.openstreetmap.org/browse/way/202404013
http://www.openstreetmap.org/#map=19/50.76640/7.27209

@matthijsmelissen
Copy link
Collaborator

Thanks for reporting, I will look at it.

@malenki
Copy link

malenki commented Jan 11, 2014

A footway with bridge=yes gets a white surrounding, too: http://www.openstreetmap.org/#map=19/40.50139/20.22511
(Note that the footway with bridge=swing doesn't get rendered at all - in return?)

matthijsmelissen added a commit to matthijsmelissen/openstreetmap-carto that referenced this issue Mar 6, 2014
This collapses, per road type, definitions that are the same for normal
roads, tunnels and/or bridges.
In addition, it gives some instances clearer names.
This makes it more easy to maintain the code, and to detect inconsistent
definitions.

Changes in rendering:
* Render minor service roads on bridges and tunnels smaller and on higher
  zoomlevels only, just like minor service roads that are not on a
  bridge or tunnel. This solves gravitystorm#269 on Github and 3883 on trac.
* Restore bridges of bridleway, footway, cycleway, path, lightrail on
  z13.
@matthijsmelissen
Copy link
Collaborator

The original issue has now been solved.

@malenki Could you please create a new issue for each separate issue?

@malenki
Copy link

malenki commented Mar 29, 2014

math1985 wrote:

The original issue has now been solved.

@malenki Could you please create a new issue for each separate issue?

Done at
#440

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants