shapes.geojson

[brechtvdv]

What do we need: List of all coordinates of the trackshape between stationX and stationY. Platforms must be excluded so we can calculate the first/last point to the correct platform. Inside the properties-key of the geojson, you specify the start- and stopStation by using its URI.

TODO

• [x] Make geojson-ld file with context
• [x] Add shape between two stations as example (you can use geojson.io for the coordinates)
• [x] Generate todo.csv of all combinations of stations (one direction), so people know what has to be done.

[brechtvdv]

@pietercolpaert What do you think of the context? Should originStop and destinationStop have @id in the context, because they're URIs?

[pietercolpaert]

Most certainly!

"@context": {
    "@context": {
      "geojson": "http://ld.geojson.org/vocab#",
      "Feature": "geojson:Feature", 
      "features": {
        "@id": "geojson:coordinates", 
        "@container": "@set"
      }, 
      "title": "http://purl.org/dc/terms/title", 
      "coordinates": {
        "@id": "geojson:coordinates"
      }, 
      "type": "@type", 
      "description": "http://purl.org/dc/terms/description",
      "properties": "geojson:properties", 
      "geometry": "geojson:geometry", 
      "FeatureCollection": "geojson:FeatureCollection", 
      "LineString": "geojson:LineString",
      "gtfs": "http://vocab.gtfs.org/terms#",
      "stop": {
          "@id":"gtfs:Stop",
          "@type" : "@id"
      }
    }
  }

Furthermore, gtfs:originStop and gtfs:destinationStop don't exist. Arrival stop and departure stop from http://semweb.mmlab.be/ns/linkedconnections# come close to what you want if you want this shape to be directed. Do we want to have a direction? Otherwise, I'd just use gtfs:stop here

[pietercolpaert]

Furthermore, it looks like the project geojson-ld is pretty much inactive, judging from checking out https://github.com/geojson/geojson-ld/issues/22

Other suggestion

Maybe we shouldn't use geojson-ld, seeing its maturity? We could use plain geojson for adding the data to github, and add a script which transforms the geojson to gtfs shapes.txt. From there we're can transform the shapes.txt to triples using https://github.com/OpenTransport/gtfs-csv2rdf

What do you think?

[sgillies]

Don't wait for GeoJSON-LD if you don't need to. The vocab (minus temporal terms) is stable, but there's no activity on the Leaflet example.

[brechtvdv]

I'll keep the context, because the vocab is stable and doesn't matter for the transformation script (and json-ld is awesome.)

[pietercolpaert]

Alright!

[pietercolpaert]

@brechtvdv OK to use the @context, but remove the mapping with coordinates, as this makes json-ld parsers crash :)