On Thu, Jun 13, 2013 at 4:12 PM, Nathan Mills nat...@nwacg.net wrote:
(I switched to talk-us for this reply because it doesn't touch on import
issues)
I don't think it's so much a bug in the stylesheet as much as a bug in the
world we're trying to map. Many cities simply have excessive
I agree this should ideally be addressed at the data level. If all parking
nodes had some capacity / access information, the renderer could prioritize
for larger public parking when zooming out, for example. And entering every
strip of street parking spots as parking in OSM does not make sense to
To amplify what Serge said about Washington, no distinction was made for
the behind-the-house, 1-2 vehicle private space versus large public lots.
So if you were to look at the WashDC map, you'd be misled into thinking
there is parking everywhere! I rather like the suggestion of addressing it
2013/6/14 Steven Johnson sejohns...@gmail.com
To amplify what Serge said about Washington, no distinction was made for
the behind-the-house, 1-2 vehicle private space versus large public lots.
So if you were to look at the WashDC map, you'd be misled into thinking
there is parking everywhere!
Makes sense to me. Private parking and parking accessible to the public should
certainly be tagged and rendered differently. I would not be surprised if some
people, trying to use an OSM map to find a place to park, and instead being
directed again and again to parking that turned out to be
5 matches
Mail list logo
