osm:maxspeed is an URI according to the context

[hdelva]

The context currently contains

osm:maxspeed: {
  "@type": "@id"
}

Which doesn't really make sense since it's just a numeric value. We don't need to specify its type at all in the context, the JSON-LD specification does it for us.

[xivk]

Would it be feasible to auto-generate the context? Any thoughts on that?

[akuckartz]

it's just a numeric value

Is it? Which unit?

[hdelva]

All values that make it into a maxspeed property are in km/h, other units such as mp/h get converted. Values such as RO:urban are problematic though, those just disappear at the moment but that should be fixed with #31.

I hope we can find a better solution though. RO:urban feels like something that should get its own URI. So perhaps we can model those as

{
  "@context": {
    "osm": "https://w3id.org/openstreetmap/terms#"
  },
  "@graph": [
    {
      "@id": "some_road",
      "osm:maxspeed": 50
    },
    {
      "@id": "some_other_road",
      "osm:maxspeed": {
        "@id": "osm:RO_urban"
      }
    }
  ] 
}

[xivk]

More information can be found here about RO:urban:

https://wiki.openstreetmap.org/wiki/Key:maxspeed#Values