[Talk-us] importing bus stops

Metcalf, Calvin (DOT) calvin.metcalf at state.ma.us
Thu Apr 12 12:41:13 BST 2012


Hey guys sorry I haven't been paying more attention to this of late, but I wanted to help as I did do a rather large bus import in the Massachusetts area that seemed go off fine (nobody complained to me at least).

First I would recommend looking at the Google transit feed files for the UTA rather then the state gis layer.  If Utah gis is anything like massgis then the their official gis layer is just based on an out of date gtfs, you can grab the most up to date uta gtfs here http://www.gtfs-data-exchange.com/agency/utah-transit-authority/latest.zip and it's from 4/6/12.  The main advantage of this was that it gave ref tags that could theoretically be hooked in to the real time transport data.  


If your interested I can give you slightly more details about how I did that import. 
-- 
Calvin Metcalf 
Massachusetts Department of Transportation 
Office of Transportation Planning 
617.973.7027 

 

>-----Original Message-----
>From: Paul Norman [mailto:penorman at mac.com] 
>Sent: Wednesday, April 11, 2012 12:52 AM
>To: 'Martijn van Exel'; 'OpenStreetMap US Talk'
>Subject: Re: [Talk-us] importing bus stops
>
>> From: Martijn van Exel [mailto:mvexel at gmail.com]
>> Subject: [Talk-us] importing bus stops
>> 
>> Hi,
>> 
>> Anyone here with experience importing bus stops? Any particular
>> considerations?
>> 
>> To make it more concrete, I have permission to import all UTA stops.
>> They come in a shapefile similar to the one available for 
>download here:
>> 
>> http://gis.utah.gov/sgid-vector-download/utah-sgid-vector-gis-data-
>> layer-download-index?fc=BusStops_UTA
>> 
>> (That particular set of files is out of date, though)
>> 
>> There's a number of properties that would map to OSM nodes pretty
>> nicely:
>> MAILBOX -> create a separate node amenity= LIGHT -> lit=yes 
>SHELTER ->
>> shelter=yes BENCH -> bench=yes (?)
>
>Unfortunately, all of these attributes are null.
>
>> 
>> I was planning to just use what I know which is 
>highway=bus_stop for the
>> bus stops, and railway=tram_stop for the light rail stops. 
>
>What differentiates them in the shapefile? I don't know the 
>area so I don't
>know where there are any light rail stops
>
>> 
>> To get back on topic, if anyone wants to help out devise a 
>mapping from
>> UTA stops file to OSM, I'd welcome some help. I've never done a local
>> import before, and I'm not a particularly big fan of 
>imports, so I want
>> to proceed with caution.
>
>I threw together a draft translation file at
>https://github.com/pnorman/ogr2osm-translations/blob/master/utahbus.py
>
>To go farther, a local would need to provide some knowledge.
>
>1. Are there unique ref numbers on the stops? Every bus stop here has a
>unique ID on its sign. If so, do these correspond to LOCATIONID?
>
>2. What are the names of some bus stops? If they're named by the street
>they're on and the cross-street it should be possible to 
>construct a name
>from the shapefile for each stop. (e.g. northbound far side 
>1st ave and main
>street)
>
>3. The shapefile appears to have address data for each stop. Should the
>addr:*=* information be added?
>
>I also noticed a couple of other things when looking at the data.
>
>The spatial accuracy is decent. Some stops are a few meters 
>off and on the
>road, not the sidewalk, but they're all near the shelters that 
>I can see.
>
>Conflating this data with the existing data will be the hard 
>part. If there
>hasn't been too much manual mapping of bus stops this could be 
>done by hand.
>If there has, then you need to look at how to conflate the data.
>
>
>
>_______________________________________________
>Talk-us mailing list
>Talk-us at openstreetmap.org
>http://lists.openstreetmap.org/listinfo/talk-us
>


More information about the Talk-us mailing list