steffenz / php-gtfs-mysql Goto Github PK

Currently the route_id column is INT (11). The GTFS spec does not mandate that this field is an integer. https://developers.google.com/transit/gtfs/reference#routes_fields

Transport for NSW (TfNSW) use alpha-numerics in their route identification, and this is breaking current importing, eg "11954_710a".

Hi,

thanks for this piece of code! It helped me a lot...

i was importing the San Francisco MTA GTFS when i found a problem... All coords that were
longer than this : 99.999999 they were written as "99.999999" so a coord like -122.493847
in the database was: -99.999999

Here the simple fix: source/sql/makeTables.php

$sqlStops = "
CREATE TABLE stops(
stop_id int(11),
stop_code varchar(255),
stop_name varchar(255),
stop_desc varchar(255),
stop_lat decimal(9,6), // 9,6 instead 8,6
stop_lon decimal(9,6), // 9,6 instead 8,6
zone_id int(11),
stop_url varchar(255),
location_type int(2),
parent_station int(11),
PRIMARY KEY(stop_id)
)";

It would be nice to add support for the shape.txt file. This contains the polyline map coordinates of every route.