PTNA: news for Public Transport Network Analysis

@ToniE Would it be possible to include the Transport Victoria GTFS data https://opendata.transport.vic.gov.au/dataset/gtfs-schedule?

This is covered by the CC BY waiver we have at File:DTP Waiver signed.pdf - OpenStreetMap Wiki

1 Like

Thanks for pointing, I’ll work on that. I also received the same idea by @LittleJimmyR (not present here?)

I will publish this as AU-VIC-DTP

Any ideas or wishes for PTNA analysis of OSM data in that area, similar to AU-SA-Adelaide-Metro and AU-NSW-Sydney

I need some more time for this.

The link does not point to a gtfs.zip who’s structure is as requested/defined by the GTFS reference.
Instead this gtfs.zip includes 8 other (correct) GTFS zip files as described in their GTFS Release Notes at page 3

So, what you’ll get from PTNA are 8 GTFS feeds:

  • AU-VIC-DTP-1 for Regional Train
  • AU-VIC-DTP-2 Metropolitan Train
  • AU-VIC-DTP-3 for Metropolitan Train
  • AU-VIC-DTP-4 for Metropolitan Bus
  • AU-VIC-DTP-5 for Regional Coach
  • AU-VIC-DTP-6 for Regional Bus
  • AU-VIC-DTP-10 for Interstate
  • AU-VIC-DTP-11 for SkyBus

I need some more time to set up these 8 configs taking care to download the global gtfs.zip only once and not 8 times.

Fortunately, checking for update using “curl -sI ...” and checking for ‘last-modified’ header is OK.

P.S.: I did not check whether the 8 zips (their individual *.txt) can easily and correctly be merged and repacked …

1 Like

Yeah I guess similar would be good. I went through the errors reported by AU-NSW-Sydney and fixed a bunch, so that was helpful.

I don’t quite understand though in Sydney why we have the busses listed once at the top with …to be completed, but then we have the complete list further down under “Other Public Transport Lines > Bus (bus)” I tried to read the documentation but couldn’t understand how it works.

Ideally, section 2. lists all routes which exit in reality, section 3. lists all others, e.g. artefacts, routes from other areas, networks, …

The routes which exit in reality can be defined in he CSV data in the OSM wiki.
For those routes, PTNA can link route-masters and routes and perform some more checks. In addition to that, PTNA can complain if a route listed there (e.g. bus 234) is missing in OSM. Having GTFS data allows creation of the CSV list using the GTFS., there’s an ‘export’ button.

Btw. AU-VIC-DTP-* GTFS will be prepared starting 13:15 CEST UTC+02

Bad news: although I had success yesterday, today I get “HTTP/2 404” not found.

I’ll have to investigate whether there is a perma-link available or whether I have to parse some HTML page to extract the daily changing URL for the GTFS data.

Having a perma-link is requested in the “GTFS best practice”.

So, this is the 2nd annoyance after gtfs.zip not being a real GTFS zip but containing 8 GTFS zips.

1 Like

No perma-link available, I have to scan a web page for the URL.
This is nothing new for PTNA, there are some other feeds which must be handled like this.

Another start preparing AU-VIC-DTP-* at 14:30 UTC+02, 4 minutes to go

… done, successfully

1 Like

I just released a new feature for PTNA: better support of Life-cycle prefix for (public transport) route relations

You’ll see the results after the usual nightly (your local time) analysis run, starting with East-Australia in 40 minutes, ending with Alaska in 19h40m

This morning I added support for the analysis of public-transport data to ptna for

based on a PM by @donmac703

Yesterday, a new gtfs feed for public-transport data has been added to ptna

  • DE-BW-BWGesamt
    • Gesamtgebiet Baden-Württemberg
    • published by NVBW - Nahverkehrsgesellschaft Baden-Württemberg mbH on behalf of Ministry of Traffic of Baden-Württemberg
    • covering all public transport lines in this state of Germany
      • benefit: includes: regional trains, Flixbus, IC, ICE, TGV, … in and through this area
      • draw-back: many routes with identical ‘ref’: e.g. 23 times bus number “1” in different locations
1 Like