When generating linked data, the full URI identifiers are used instead of lat, long. This might be related to a fix which changed the data type from strings to floats, a couple of months ago.
Expected output:
the "longitude" keyword, which is defined in the linked data header, should be used in stead of http://www.w3.org/2003/01/geo/wgs84_pos#long . The same goes for latitude.
When generating linked data, the full URI identifiers are used instead of lat, long. This might be related to a fix which changed the data type from strings to floats, a couple of months ago.
Current output: {"@id":"http://irail.be/stations/NMBS/007015400","alternative":[{"@language":"fr","@value":"Londres Saint Pancras"},{"@language":"nl","@value":"Londen Saint Pancras"}],"avgStopTimes":"0","country":"http://sws.geonames.org/2635167/","http://www.w3.org/2003/01/geo/wgs84_pos#lat":"51.5310399","http://www.w3.org/2003/01/geo/wgs84_pos#long":"-0.1260606","name":"London Saint Pancras International"}
Expected output: the "longitude" keyword, which is defined in the linked data header, should be used in stead of http://www.w3.org/2003/01/geo/wgs84_pos#long . The same goes for latitude.
The commit which might have introduced this: https://github.com/iRail/stations/commit/e1a112040601031d10eaed0e749013d2fe40f637
This issue affects api.irail.be, but only in the staging area at this moment. api.irail.be can't be updated until this is fixed.