Being an American has nothing to do with a really bad data design.
I've been an American 35 years and I think this is really not a good
way to model sidewalks.
The problem (aside from the issue of data clutter) is that the
sidewalk data can't be used for pedestrian routing because the
information
2014-05-08 11:58 GMT+02:00 Serge Wroclawski emac...@gmail.com:
Being an American has nothing to do with a really bad data design.
I've been an American 35 years and I think this is really not a good
way to model sidewalks.
+1, agree, my main concern is that as pedestrian you can actually
On Thu, May 8, 2014 at 7:36 AM, Mike Dupont
jamesmikedup...@googlemail.com wrote:
On Thu, May 8, 2014 at 4:58 AM, Serge Wroclawski emac...@gmail.com wrote:
I've been an American 35 years and I think this is really not a good
way to model sidewalks.
Ok, serge, well how do you address my
Bill,
You're right that we should map what exists on the ground. I think we
need to really consider a few factors here:
1. Why we map sidewalks at all (in either style)
2. What benefits one mapping method has over another
3. The data as it exists now
1. Why map sidewalks
This is a judgement
2014-05-08 16:32 GMT+02:00 Serge Wroclawski emac...@gmail.com:
1. Why map sidewalks
This is a judgement call. In NYC it's reasonable to assume that a road
has a sidwalk. It would be better to map roads without sidwalks than
roads with them, because a vast majority of roads have sidewalks.
On Thu, 2014-05-08 at 05:58 -0400, Serge Wroclawski wrote:
The problem (aside from the issue of data clutter) is that the
sidewalk data can't be used for pedestrian routing because the
information about the street is not captured. You can't tell someone
to follow Main Street, because the path
2014-05-08 17:46 GMT+02:00 James Umbanhowar jumba...@gmail.com:
Could this problem be alleviated with a tag on the separately mapped
footway, e.g. road_name? Or even just addr:street?
why not make it simple and use name? As long as the sidewalk is part of
the road this would be correct.
On Thu, May 8, 2014 at 7:32 AM, Serge Wroclawski emac...@gmail.com wrote:
The biggest issue here is usage. It's not what mappers should do,
but What mappers actually do and what mappers actually do is not to
create relations. Most sidewalks are either mapped as separate ways,
as attributes,
On Thu, May 8, 2014 at 12:59 PM, Clifford Snow cliff...@snowandsnow.us wrote:
Routing doesn't need names, it just needs connected ways and a means to
display the route. I agree that without names, it is difficult to give
written directions. But how often do we need written directions any more?
On Thu, May 8, 2014 at 1:55 PM, Chris Lawrence lordsu...@gmail.com wrote:
Audio routing (so you can put your phone in your pocket and listen to
headphones) and audio/braille descriptions for the disabled would be
the most obvious use cases for names. In fact, I'd imagine the
disabled are a
I'm trying to work out how using name=* on the sidewalks isn't the easiest,
most obvious answer.
On Thu, May 8, 2014 at 6:09 PM, Clifford Snow cliff...@snowandsnow.uswrote:
On Thu, May 8, 2014 at 1:55 PM, Chris Lawrence lordsu...@gmail.comwrote:
Audio routing (so you can put your phone in
Duplication of data, possibly?
Regarding the detection of the nearest street, the risk here is at the
intersection, where the sidewalk might be attributed to the other street.
--
Saikrishna Arcot
On Thursday, May 08, 2014 07:02:16 PM Paul Johnson wrote:
I'm trying to work out how using name=*
On Thu, May 8, 2014 at 8:02 PM, Paul Johnson ba...@ursamundi.org wrote:
I'm trying to work out how using name=* on the sidewalks isn't the easiest,
most obvious answer.
Because there are walking paths with names, and that's not what you're
talking about.
What you want is essentially a
13 matches
Mail list logo
