<div dir="ltr">Hi Martijn - <div><br></div><div style>I love the transit info.</div><div style><br></div><div style>Have you tried asking the data owners for exceptions to any of the onerous terms of their current license?</div>
<div style><br></div><div style>Thanks, Jeff</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Apr 23, 2013 at 5:59 AM, Elliott Plack <span dir="ltr"><<a href="mailto:elliott.plack@gmail.com" target="_blank">elliott.plack@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Looks good. I've been pondering a similar import, but the stop location data isn't very accurate in my jurisdiction. Many are in the middle of the intersection, in a building, or nearby. Do you find that each stop is very close to where the actual stop pole/sign is?</div>
<div class="gmail_extra"><div><div class="h5"><br><br><div class="gmail_quote">On Sun, Apr 21, 2013 at 10:54 PM, Martijn van Exel <span dir="ltr"><<a href="mailto:m@rtijn.org" target="_blank">m@rtijn.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi all,<br>
<br>
I posted the message below to talk-us and imports-us earlier, but after reviewing the import guidelines I thought it appropriate to also post here.<br>
<br>
It was pointed out to me that I have not followed all the suggested steps outlined on the import guidelines page. Let me just add that I don't intend to go forward with this until I have performed all the steps deemed appropriate for a data import. This is the first time I am attempting an import and I fully intend to get it right. Even if that means that the import won't happen.<br>
<br>
It was also pointed out to me that it is not clear under what license the original data is being released. While I got verbal confirmation that I can do 'anything I please' with this data, I will seek written confirmation that the data is released under terms that agree with ODbL.<br>
<br>
More feedback that I have already received:<br>
* is_in is considered deprecated, I will likely drop these tags.<br>
* Some find/replace operations were too greedy ('Salt Lake is_in:city').<br>
* use the modern public transport tagging scheme in addition to bus_stop.<br>
<br>
I look forward to hearing your feedback.<br>
<br>
Martijn van Exel<br>
<br>
=========================%<===<u></u>==============================<u></u>===========<br>
<br>
<br>
Hi all,<br>
<br>
During the edit-a-thon today I finally got around to working on preparing a relatively small import of bus stop point data for the UTA service area (comprising a half dozen counties along the Utah Wasatch Front). There are ~6450 bus stops in the data I got from my contact at UTA. This data is being released to the public through the Utah GIS data portal [1], but the data I got directly from UTA is more recent (Dec 2012).<br>
<br>
Data processing consisted of removing empty and irrelevant fields, and sanitizing the fields that are relevant. I kept:<br>
COUNTY --> is_in:county<br>
CITY --> is_in:city<br>
ACCESS --> wheelchair = yes|limited|no<br>
BENCH --> bench = yes|no<br>
LOCATIONID --> uta:stop_id<br>
<br>
I checked the existing bus stop data and there are 92 existing nodes. I have saved these as an OSM file and intend to manually conflate these after the fact. This will mean most existing bus stop nodes will be removed, I spot checked a dozen and so far did not find a any added value. There are a few non-UTA stops (Airport parking lot shuttle stops etc) that will be retained.<br>
<br>
The source data I received can be found here: <a href="https://www.dropbox.com/s/tyxdhf9hlpuc9z8/BusStops_UTA_shp.zip" target="_blank">https://www.dropbox.com/s/<u></u>tyxdhf9hlpuc9z8/BusStops_UTA_<u></u>shp.zip</a><br>
<br>
The processed data can be found in OSM XML format here: <a href="https://www.dropbox.com/s/v3c0tsgfhlc6izx/busstops_uta.osm" target="_blank">https://www.dropbox.com/s/<u></u>v3c0tsgfhlc6izx/busstops_uta.<u></u>osm</a><br>
<br>
Future updates will be handled using the persistent uta:stop_id. A new stops file is released around once a year.<br>
<br>
Light rail stops are captured in a separate dataset that I do not intend to import, as these stops and stations are mostly already captured in greater detail in OSM.<br>
<br>
I am running this by all of you because I have not really done any external data imports before. This is a relatively small one, but I would like your opinion on the following:<br>
<br>
* Is this data import properly prepared?<br>
* If not, which steps should I revisit / add and how?<br>
* Do you recommend using a separate account for uploading the external data?<br>
<br>
Looking forward to your feedback.<br>
Martijn<br>
<br>
[1] <a href="http://gis.utah.gov/data/sgid-transportation/transit/" target="_blank">http://gis.utah.gov/data/sgid-<u></u>transportation/transit/</a><span><font color="#888888"><br>
-- <br>
Martijn van Exel<br>
<br>
-- <br>
Martijn van Exel<br>
<br>
______________________________<u></u>_________________<br>
Imports mailing list<br>
<a href="mailto:Imports@openstreetmap.org" target="_blank">Imports@openstreetmap.org</a><br>
<a href="http://lists.openstreetmap.org/listinfo/imports" target="_blank">http://lists.openstreetmap.<u></u>org/listinfo/imports</a><br>
</font></span></blockquote></div><br><br clear="all"><div><br></div></div></div><span class="HOEnZb"><font color="#888888">-- <br><div dir="ltr">Elliott Plack</div><div dir="ltr"><a href="http://about.me/elliottp" target="_blank">http://about.me/elliottp</a></div>
</font></span></div>
<br>_______________________________________________<br>
Imports mailing list<br>
<a href="mailto:Imports@openstreetmap.org">Imports@openstreetmap.org</a><br>
<a href="http://lists.openstreetmap.org/listinfo/imports" target="_blank">http://lists.openstreetmap.org/listinfo/imports</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><font size="1">Jeff Meyer<br>Global World History Atlas<br><a href="http://www.gwhat.org" target="_blank">www.gwhat.org</a><br><a href="mailto:jeff@gwhat.org" target="_blank">jeff@gwhat.org</a><br>
206-676-2347</font><div><font size="1"><br></font></div><div><span style="font-size:x-small">OpenStreetMap: Mapping with a Human Touch</span><font size="1"><br></font><div><font size="1"><a href="http://www.openstreetmap.org/user/jeffmeyer" target="_blank"><img src="http://wiki.openstreetmap.org/w/images/thumb/7/79/Public-images-osm_logo.svg/24px-Public-images-osm_logo.svg.png"></a> </font><span style="font-size:x-small">osm: <a href="http://wiki.openstreetmap.org/wiki/Open_Historical_Map" target="_blank">Open Historical Map (OHM)</a> / <a href="http://www.openstreetmap.org/user/jeffmeyer" target="_blank">my OSM user page</a></span></div>
<div><img src="http://lincs.ed.gov/sites/default/files/twitter-icon-24x24.png"> <font size="1">t: <a href="https://twitter.com/GWHAThistory" target="_blank">@GWHAThistory</a></font></div><div></div><div><img src="http://external.ak.fbcdn.net/safe_image.php?d=AQCki9dbi3qyfa_g&w=155&h=114&url=http%3A%2F%2Fsocialmediachapter.com%2Fimages%2F09825d933fd5044ce4ae18101982a012_u1mq.png"> <font size="1">f: <a href="https://www.facebook.com/GWHAThistory" target="_blank">GWHAThistory</a></font></div>
<div><br></div><div><font size="1"><br></font><br></div></div>
</div>