I took a quick look at this sample data. Some of it seems to match to data we already map, while some of it doesn't. Here's how I'd match it up.

Note that I haven't actually looked at the area to see how things are currently tagged, so if they're using e.g. the older highway=bus_stop tagging this matching would have to be adapted.


Rout ID / RouteNum / RouteName => one of these would be route_ref=* on a public_transport=platform. But which one? What's the difference?

Stop ID => Why is this always 0 in the sample data? Does it mean anything?

Stop # => ref=* on a public_transport=platform

Stop Name => name=* on a public_transport=platform (but not if you made these names up yourself, which I've seen people do)

Features / FeaturesUnabbreviated => What are near side stop, far side stop, and corner stop? shelter can go to shelter=yes on public_transport=platform

Transfers => We wouldn't tag this in OSM. Instead, we'd make sure all the routes are listed in route_ref=* and also make sure the platform is a member of route relations for each applicable route.

STOP_SEQ => We wouldn't tag this in OSM. Instead, we'd make sure stop positions and platforms are listed in order in a route relation.

Direction => We wouldn't tag this in OSM. Instead, each direction would be a separate route relation

Intersection => We wouldn't tag this in OSM.

Notes => We wouldn't tag this in OSM. It could be inferred from the geometry in the route relation.

Date Revised => We wouldn't tag this in OSM.

Latitude / Longitude => This would be the coordinates of the points entered. Hopefully many of these stops have already been entered, though!

Stop Type / StopTypeUnabbreviated / StopLength => We do not currently have any way of tagging this in OSM. Do you think it would be useful information for the users you work with? If so, we can work out what the best way of incorporating it is.

Access => What does this refer to, and what does the value "A" mean?

Shelter => If it's not important to keep the ID, this can just be shelter=yes on a public_transport=platform (as mentioned in features, above). If it IS important to keep the ID, you can map the shelter as a separate object, tag ref=* on the shelter, and then associate the shelter to the platform with a stop_area relation. Personally I'd drop the ID.

Muni Notes => Does anything here need to be kept?


Those are of course just my quick opinions on how I'd match it. Anything in there that doesn't work for you? Or more information about the bits I wasn't sure about?

--Andrew


On 08/19/2015 04:32 PM, Scott Blanks wrote:
Hi all,

I'm following up from a post I sent to the list a couple weks back. I
work at the LightHouse for the Blind in San Francisco. We have data we
hope to upload to OSM, and I had planned to share examples of the data
much sooner than today. Nonetheless, here is a glimpse at the the type
of information we have. I can attach an Excel doc if that's easier,
but for now I'll just post the raw data below. After taking a look at
this, I'd appreciate hearing from anyone about whether this is an
appropriate type of POI to upload to OSM. Keep in mind our goal is to
make this data available particularly to blind travelers, as it
contains key details that our community needs when traversing the
city.

Rout ID RouteNum        RouteName       Stop ID Stop #  Stop
Name    Features        FeaturesUnabbreviated   Transfers       STOP_SEQ        
Direction       Intersection    Notes   Date
Revised Latitude        Longitude       Stop
Type    StopTypeUnabbreviated   StopLength      Access  Shelter Muni Notes
9152    1       1-California    0       14277   Geary Blvd and 33rd Ave ncs     
near side
stop; corner stop; shelter      1ax; 18; 38; 38ax;
38r     i101    inbound 3308    Right turn onto 33rd
Ave.    5/12/2015       37.779833       -122.493178     BZ      Bus Zone        
187 feet        A               terminal
9152    1       1-California    0       13555   33rd Ave and Clement St ncs     
near side
stop; corner stop; shelter      1ax; 18 i102    inbound 3305    Right turn onto
Clement St, left turn onto 32nd
Ave.    4/29/2013       37.7815 -122.49337      BZ      Bus Zone        75 feet 
A       1226
9152    1       1-California    0       13548   32nd Ave and Clement St fcs     
far side stop;
corner stop; shelter    1ax     i103    inbound 3205    none    4/29/2013       
37.781995       -122.492335     BZ      Bus
Zone    80 feet A       519
9152    1       1-California    0       13546   32nd Ave and California St      
nc      near side
stop; corner stop       1ax     i104    inbound 3203    Right turn onto 
California
St.     4/29/2013       37.783419       -122.492442     PS      Pole Stop       
        A
9152    1       1-California    0       13844   California St and 30th Ave      
fcs     far side
stop; corner stop;
shelter 1ax     i105    inbound 5293    none    4/29/2013       37.783578       
-122.490087     PS      Pole
Stop            A       1284


_______________________________________________
Imports-us mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/imports-us

Reply via email to