<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
On 08/28/2011 06:34 AM, Stefan de Konink wrote:
<blockquote cite="mid:4E5A43F9.6060707@konink.de" type="cite">
<pre wrap="">-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Op 28-08-11 06:24, Bryce Nesbitt schreef:
</pre>
<blockquote type="cite">
<pre wrap="">The name in the proposal is not a true bus stop name, but
a mashup of the street name.
</pre>
</blockquote>
<pre wrap="">
How are the stops generally identified then?
</pre>
</blockquote>
In the data supplied by Fairfax County, there is a primary key.<br>
On the street the poles are simply stuck in the ground.<br>
In the osm data we have a choice: even if the name field is blank
the icon will render just fine. If tools can't deal with bus stops
without name then the tools need improvement.<br>
<br>
(In bus operations it is typical that the only documentation for bus
stops is the actual pole in the ground. The drivers look for the
pole when driving, and no electronic or even paper record exists of
the bus stop. The agency itself has to survey the lines to build
any sort of database, and that database is highly subject to both
survey error and bit-rot over time.<br>
<br>
Some regions have assigned unique stop IDs (for example the UK ad
the San Francisco Bay Area). But for many operators it is just a
sign by the road... with no name and nobody to record it other than
an eagle eyed osm mapper with a <a
href="http://wiki.openstreetmap.org/wiki/JOSM/Plugins/public_transport#Map_Stops_with_a_Tracklog_and_a_Stopwatch">stopwatch</a>.<br>
<br>
Quite probably the osm mapper could provide data <i>to</i> such
operators, in <u>reverse of the usual import pattern.</u> Osm
--> gtfs would be an interesting experiment.<br>
<br>
)<br>
</body>
</html>