fakhrikharrat / googletransitdatafeed

Automatically exported from code.google.com/p/googletransitdatafeed
0 stars 0 forks source link

invalid character in header row isn't detected #52

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
Unitrans published their feed (yeah!) but had a subtle error not detected
by the validator. From

http://iportal.sacrt.com/GTFS/Unitrans/20080331/google_transit.zip
transfers.txt

00000000  66 72 6f 6d 5f 73 74 6f  70 5f 69 64 2c 74 6f 5f  |from_stop_id,to_|
00000010  73 74 6f 70 5f 69 64 2c  66 72 6f 6d 5f 72 6f 75  |stop_id,from_rou|
00000020  74 65 5f 69 64 2c 74 6f  5f 72 6f 75 74 65 5f 69  |te_id,to_route_i|
00000030  64 2c 74 72 61 6e 73 66  65 72 5f 74 79 70 65 2c  |d,transfer_type,|
00000040  6d 69 6e 5f 74 72 61 6e  73 66 65 ad 72 5f 74 69  |min_transfe­r_ti|
00000050  6d 65 2c 73 65 72 76 69  63 65 5f 69 64 0d 0a     |me,service_id..|

The 0xad at offset 0x4b is bogus.

Original issue reported on code.google.com by tom.brow...@gmail.com on 9 Apr 2008 at 9:50

GoogleCodeExporter commented 8 years ago
Umm, the validator isn't going to detect a problem in a file it doesn't know 
about. I
suspect this will be detected when we add transfers to the spec and 
transitfeed.py

Original comment by tom.brow...@gmail.com on 10 Apr 2008 at 12:20

GoogleCodeExporter commented 8 years ago
indeed, this now generates a Unrecognized Column warning

Original comment by tom.brow...@gmail.com on 18 Sep 2009 at 5:03