Sadless74 / googletransitdatafeed

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

validate stop_headsign and trip_headsign are consistent #31

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
The spec is not very clear and the validator doesn't check. I don't think
it is intentional. We need to fix both.

Original issue reported on code.google.com by tom.brow...@gmail.com on 19 Aug 2007 at 7:08

GoogleCodeExporter commented 9 years ago
What constitutes 'consistent'?  By definition stop_headsign should be different 
from 
trip_headsign; if it isn't there's no reason to use it.

Original comment by THix...@juno.com on 12 Jan 2009 at 8:29

GoogleCodeExporter commented 9 years ago
Ideally for each trip either trip_headsign is set or a stop_headsign is given 
for
each stop. Anything else is ambiguous because the spec isn't clear. I need to
investigate use of trip/stop_headsign mixes and sparse setting of stop_headsign 
in
existing data before trying to clear up the spec and validator.

Original comment by tom.brow...@gmail.com on 12 Jan 2009 at 8:57

GoogleCodeExporter commented 9 years ago

Original comment by tom.brow...@gmail.com on 16 Nov 2009 at 4:24

GoogleCodeExporter commented 9 years ago
Moved to https://github.com/google/transitfeed/issues/31

Original comment by bdfer...@google.com on 7 Oct 2014 at 7:52