search

koch-t / ndovextract

DEPRECATED - Replaced by https://github.com/bliksemlabs/bliksemintegration
1 stars 4 forks source link

GVB TimingPointCode vs UserStopCode #2

Open dsbaars opened 9 years ago

dsbaars commented 9 years ago

I tried to match the TimingPointCode from GTFS exports at http://gtfs.ovapi.nl/gvb/ with the GVB TimingPointCodes from the API.

It looks like it missing in the KV1 data-files, and available in the KV7 files.

How I tested with with TPC 30005033 (UserStopCode 05025):

# MD5 (GVB.20140908.TBM.zip) = a39d7877d6c4b89cb84f7109df3647b6
$ unzip GVB.20140908.TBM.zip
$ grep 30005033 USRSTOPXXX.tmi
# output: (empty)
$ grep 05025 USRSTOPXXX.tmi
# output: USRSTOP|1|I|GVB|050252||Y|Y|N|Centraal Station|Amsterdam||-|||0||

# MD5 (gtfs-kv1gvb-20150517.zip) = a4fda8274052691f5e17f99a269011e7
$ unzip gtfs-kv1gvb-20150517.zip
$ grep 30005033 stops.txt
# output: (empty)
$ grep 05025 stops.txt
# output:
# GVB:05025,05025,"Amsterdam, Centraal Station",52.378216,4.897511,0,stoparea:GVB:05025,,0,F,
# GVB:05026,05026,"Amsterdam, Centraal Station",52.377984,4.89791,0,stoparea:GVB:05025,,1,F,
# GVB:05030,05030,"Amsterdam, Centraal Station",52.377632,4.897767,0,stoparea:GVB:05025,,1,F,
# GVB:05033,05033,"Amsterdam, Centraal Station",52.377705,4.89781,0,stoparea:GVB:05025,,0,F,
# GVB:05034,05034,"Amsterdam, Centraal Station",52.377651,4.89781,0,stoparea:GVB:05025,,0,F,
# stoparea:GVB:05025,,"Amsterdam, Centraal Station",52.3778376,4.8977616,1,,,0,,

compared to CXX TPC 56332350

# MD5 (CXX.20150607.zip) = 178df57f7972273995fafd22bc841b5b
$ unzip CXX.20150607.zip 
$ grep 56332350 USRSTOP.TMI
# output: USRSTOP|1|I|CXX|56332350||true|true|N|Hoofddorp, Wilsonstraat|Hoofddorp||-|||0|||PASSENGER
# MD5 (gtfs-kv1connexxion-20150519.zip) = 31837e755eee36d19934bcb94f7a4715
$ unzip gtfs-kv1connexxion-20150519.zip
$ grep 56332350 stops.txt
# output: CXX:56332350,56332350,"Hoofddorp, Wilsonstraat",52.305609,4.680076,0,,,0,,

Is there any way to "merge" the GVB TimingPointCodes somehow from the KV7 feed to make the GTFS exports consistent with the KV78Turbo API?

koch-t commented 9 years ago

You are comparing userstopcodes with GOVI timingpointcodes, You're probably better off using KV7 data by OpenOV/GVB if you want to keep in the GOVI ecosystem.

On Sun, Jun 14, 2015 at 9:28 PM, Djuri Baars notifications@github.com wrote:

I tried to match the TimingPointCode from GTFS exports at http://gtfs.ovapi.nl/gvb/ with the GVB TimingPointCodes from the API.

It looks like it missing in the KV1 data-files, and available in the KV7 files.

How I tested with with TPC 30005033 http://v0.ovapi.nl/tpc/30005033 (UserStopCode 05025):

MD5 (GVB.20140908.TBM.zip) = a39d7877d6c4b89cb84f7109df3647b6

$ unzip GVB.20140908.TBM.zip $ grep 30005033 USRSTOPXXX.tmi# output: (empty) $ grep 05025 USRSTOPXXX.tmi# output: USRSTOP|1|I|GVB|050252||Y|Y|N|Centraal Station|Amsterdam||-|||0||

MD5 (gtfs-kv1gvb-20150517.zip) = a4fda8274052691f5e17f99a269011e7

$ unzip gtfs-kv1gvb-20150517.zip $ grep 30005033 stops.txt# output: (empty) $ grep 05025 stops.txt# output:# GVB:05025,05025,"Amsterdam, Centraal Station",52.378216,4.897511,0,stoparea:GVB:05025,,0,F,# GVB:05026,05026,"Amsterdam, Centraal Station",52.377984,4.89791,0,stoparea:GVB:05025,,1,F,# GVB:05030,05030,"Amsterdam, Centraal Station",52.377632,4.897767,0,stoparea:GVB:05025,,1,F,# GVB:05033,05033,"Amsterdam, Centraal Station",52.377705,4.89781,0,stoparea:GVB:05025,,0,F,# GVB:05034,05034,"Amsterdam, Centraal Station",52.377651,4.89781,0,stoparea:GVB:05025,,0,F,# stoparea:GVB:05025,,"Amsterdam, Centraal Station",52.3778376,4.8977616,1,,,0,,

compared to CXX TPC 56332350 http://v0.ovapi.nl/tpc/56332350

MD5 (CXX.20150607.zip) = 178df57f7972273995fafd22bc841b5b

$ unzip CXX.20150607.zip $ grep 56332350 USRSTOP.TMI# output: USRSTOP|1|I|CXX|56332350||true|true|N|Hoofddorp, Wilsonstraat|Hoofddorp||-|||0|||PASSENGER# MD5 (gtfs-kv1connexxion-20150519.zip) = 31837e755eee36d19934bcb94f7a4715 $ unzip gtfs-kv1connexxion-20150519.zip $ grep 56332350 stops.txt# output: CXX:56332350,56332350,"Hoofddorp, Wilsonstraat",52.305609,4.680076,0,,,0,,

Is there any way to "merge" the GVB TimingPointCodes somehow from the KV7 feed to make the GTFS exports consistent with the KV78Turbo API?

— Reply to this email directly or view it on GitHub https://github.com/skywave/ndovextract/issues/2.

dsbaars commented 9 years ago

Thanks for the quick reply, I'm trying to match OTP stopCodes with the TimingPointCode of the REST API. I built the graph using gtfs-nl since it looks like the stop_code of this export matches the TimingPointCode for all companies except for GVB. If I understand the KV1 documentation correctly, USRSTOP/UserStopCode is initally equal to the TimingPointCode. I was wondering where the TimingPointCode 30005033 comes from, so I can decide if creating a conversion table might be a safe enough solution.