Based on Translink's new nightbuses, I just added analysis support of public-transport data of osm to ptna for
I’m not very knowledgeable about this kind of data, but on Translink’s page Freedom of Information and Open Data | Legal Information | Translink it says “Data released by Translink will be under the Open Government Licence or through Translink’s Access to Information Licence.”
Their datasets are published at Portal | Search
and info on their API is here Public Transport API | Translink
Also, some of Translink’s long distance bus routes are tagged on OSM with the key ‘network=Goldline’ or ‘Goldliner’
Another variant is ‘network=Ulsterbus Town Services’
And ‘network=Glider’ is an important one (big bendy busses! 
)
Thanks for the links. Unfortunately, there is no GTFS data. Routes and timetables are given in *.cif files or the like, not suitable.
Thanks for this!
I added those and also “Ulsterbus”.
Kindly let me know whether I’ve gone a bit too far with that.
A new analysis is in the pipeline, will be started in 5 minutes
Oh well Translink are not exactly at the bleeding edge of technology, I am always slightly amazed they have any data at all 
I don’t know if it’s something your PTNA project uses, but Translink do (sort of) participate in the UK’s NaPTAN thing, meaning they endeavour to allocate a unique ‘ATCO’ code to all of their bus stops.
OSM mapping of Translink bus stops is still rather patchy, but I have just completed retroffitting ‘naptan:AtcoCode=’ tags to all the bus stops on their currently-mapped PTv2 bus routes.
No, PTNA (currently) supports only GTFS as this has a world-wide coverage and is quite easy to handle (f.m.p.o.v.).
In Europe, there’s also NExT NeTEx with obviously smaller coverage.
‘Foyle Metro’, ‘Airport Express’, ‘Metro’ and ‘NIR’ are also all Translink network brands. (‘NIR’ = Northern Ireland Railways)
I just added those and the analysis is again in the pipeline. Should be available at 7:02 PM your time.
the error log on the PTNA listing is very helpful in fixing a lot of little bugs in the routes. 
I have done a little bit of clean-up on the ‘network=’ tags for Translink bus routes.
I have standardised the Goldliner ones as ‘network=Goldliner’ (so we can forget about the ‘Goldliner Express’ and ‘Goldline’ value)
Also ‘network=Airport Express’ I have changed to ‘network=Translink Ulsterbus’ with ‘name=Airport Express’.
Done, and in the pipeline.
Based on the discussion related to Github issue #74 for ptna-www initiated by @MxxCon I just released a small feature:
In the popup window for a GTFS stop, show:
You might have to push Ctrl-R or Ctrl-F5 to refresh the browser cache and reload the JavaScript.
Edit: fixed 2 typos
Based on a missing feature / a bug in JOSM’s remote control interface, PTNA cannot inject data into route_master or route relations which include the pipe symbol ‘|’.
As a work-around, PTNA suppresses this data and gives a hint.
Please re-load pages with Ctrl-R or Ctrl-F5
Mouse-over the yellow string shows a hint: “String includes ‘|’”
Mouse-over the injection needle shows which tags get added and which not.
Related to #14490 (Support for escaping pipe character in remote control addtags parameters) – JOSM which seems to gain momentum
