[Talk-us] Parking rendering

[John F. Eldredge]

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 off-limits, ended up giving up on the use of OSM altogether.


Steven Johnson <sejohnson8 at gmail.com> wrote:
> 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
> through capacity, public/private, and access. Scale-dependent display
> would
> help, as well.
> 
> -- SEJ
> -- twitter: @geomantic
> -- skype: sejohnson8
> 
> There are two types of people in the world. Those that can extrapolate
> from
> incomplete data.
> 
> 
> On Fri, Jun 14, 2013 at 10:09 AM, Martijn van Exel <m at rtijn.org>
> wrote:
> 
> > 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 me.
> >
> > As it is, it's probably better to have mappers being exposed to this
> > 'over-parking' in some areas, so that we actually have this
> discussion.
> > Whether that exposure should be on the main map or on a separate
> data
> > dashboard is a non-issue until we actually have these data
> dashboards ;)
> >
> > Martijn
> >
> >
> > On Fri, Jun 14, 2013 at 7:25 AM, Serge Wroclawski
> <emacsen at gmail.com>wrote:
> >
> >> On Thu, Jun 13, 2013 at 4:12 PM, Nathan Mills <nathan at 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
> amounts of
> >> parking and that shows up on the map.
> >>
> >> This is partially (though not entirely) a US "problem", and while
> we
> >> can argue the issues around parking in general, the map clutter is
> due
> >> to a combination of rendering issues and other problems.
> >>
> >> For example, in the Washington, DC area, there are many small,
> narrow
> >> parking areas which are in reality just street parking that has
> been
> >> improperly imported.
> >>
> >> I suspect that if we examine many areas where parking is so
> cluttered,
> >> we will find some combination of rendering issues and data issues.
> >>
> >> The data issues will need addressing, then the rendering problems
> are
> >> likely going to be fairly solvable.
> >>
> >> - Serge
> >>
> >> _______________________________________________
> >> Talk-us mailing list
> >> Talk-us at openstreetmap.org
> >> http://lists.openstreetmap.org/listinfo/talk-us
> >>
> >
> >
> >
> > --
> > Martijn van Exel
> > http://oegeo.wordpress.com/
> > http://openstreetmap.us/
> >
> > _______________________________________________
> > Talk-us mailing list
> > Talk-us at openstreetmap.org
> > http://lists.openstreetmap.org/listinfo/talk-us
> >
> >
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Talk-us mailing list
> Talk-us at openstreetmap.org
> http://lists.openstreetmap.org/listinfo/talk-us

-- 
John F. Eldredge -- john at jfeldredge.com
"Reserve your right to think, for even to think wrongly is better than not to think at all." -- Hypatia of Alexandria
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk-us/attachments/20130614/6ffdc6da/attachment-0001.html>