Shouldn't we keep the schema to something that is easily compatible with the
Google Transit GTFS format instead of developing something different all
together? I believe the GTFS was developed after extensive research on how
transit companies actually manage their data and how that data can be
On 29.06.2010 09:33, Tiziano D'Angelo wrote:
+1
On Tue, Jun 29, 2010 at 08:23, Arun Ganesh arun.plane...@gmail.com
mailto:arun.plane...@gmail.com wrote:
Shouldn't we keep the schema to something that is easily
compatible with the Google Transit GTFS format instead of
developing
Am 29.06.2010 10:22, Michał Borsuk:
On 29.06.2010 09:33, Tiziano D'Angelo wrote:
+1
On Tue, Jun 29, 2010 at 08:23, Arun Ganesh arun.plane...@gmail.com
mailto:arun.plane...@gmail.com wrote:
Shouldn't we keep the schema to something that is easily
compatible with the Google Transit
Oxomoa is suggesting bus stop on the way only for the most basic bus
stop (think of a bus stop on a crossing on the country side with just a
sign). If you have a more advanced bus stop with waiting positions for
passengers on both sides of the street you add a
public_transport=stop_position on
Am 28.06.2010 22:16, Michał Borsuk:
More details in the graphics here:
http://wiki.openstreetmap.org/wiki/User:Oxomoa/Public_transport_schema#Examples_for_the_application_of_the_model_for_stops
The link you provided is a very good example of oxomoa's weakness.
While the first simple
In the UK as part of the Naptan import we already have decided that bus stops
must be marked exactly where they are on the ground and added to the route
relation of the bus route.
Shaun
On 28 Jun 2010, at 19:07, Michał Borsuk wrote:
Hi everybody again:
This time I'd like to propose a
To Claudius and Shaun: why don't we have those rules written?
--
Best regards, mit freundlichen Grüssen, meilleurs sentiments, Pozdrowienia,
Michał Borsuk
___
Talk-transit mailing list
Talk-transit@openstreetmap.org
