I finally got around to making the quasi-static metadata files only update when the contents changes — this allows you to use a HEAD query to tell if the data has changed and thus avoid uneccessary pulls or cache files locally if you’re writing a non-web based client.
– added a query to return the ownership and open statuses of the facilities for a given CP: http://web3.wwiionline.com/xmlquery/facilities.xml?cp=300
– added ‘cpdetail’ metadata files which provide counts of facilities and links within a cp: http://web3.wwiionline.com/js/cpdetail.js
– added ‘links’ metadata files to provide details of CP linkage: http://web3.wwiionline.com/xml/links.xml
The way we do links is a little strange-seeming at first, they’re uni-directional: i.e. there is a link from Antwerp to Schilde *and* a link from Schilde to Antwerp; if there is a firebase pair between the two towns, they are split between the two links – so the Antwerp-Schilde Firebase is on the link that connects Antwerp to Schilde. The opposite firebase is on the reverse link.
If you want to know the open/closed status of FBs, you have to query the facility statuses for the CP on the *left* side of the link. I.e. to find out the Kalmthout->Roosendaal FB status, get the facilities for Kalmthout.
Documentation in the usual place.
I really think I need to make CSV versions of the data because with the XML version I’m very conscious that spelling labels out fully adds bandwidth to every single row.