-
Notifications
You must be signed in to change notification settings - Fork 4
Home
Welcome to the CitySDK Linked Data API wiki. This wiki contains the documentation of the CitySDK LD API.
Note: users who are familiar with the URI structure of the old version of the API (version 0.9) should have a look at the wiki page comparing the old and new version.
CitySDK is creating a toolkit for the development of digital services within cities. With open and interoperable digital service interfaces, CitySDK enables a more efficient utilisation of the expertise and know-how of developer communities. See the CitySDK project website for a comprehensive overview of the complete CitySDK toolkit.
The Linked Data API offers unified and direct access to open transport, mobility and geo data from government, commercial and crowd sources alike. It is designed to work closely with other open source projects as OpenTripPlanner, Analyst, Open311 and OpenStreetMap.
In the CitySDK Linked Data API, data sets are called layers. Each layer can contain objects, and each object contains, per layer, key/value data. In the API, real-world objects like buildings, bus stops and municipalities are represented by objects, which can contain data on one or more layers. This way, multiple data sets can tell something about one single object.
You can use the map viewer and data page on the project's website to see and test example API calls, and to view the data on a map.
The pages below describe the URI structure of the API, and the data those API calls require and return.
-
/: Endpoint metadata -
/layers: Layers -
/objects: Objects -
/owners: Owners
Questions, suggestions, comments: citysdk@waag.org.