Linked Data

The following REST/Linked Data services are provided:


Obtain the complete LGD ontology



Obtain information about a specific element of the LGD ontology



Obtain information about a particular way (identified by its OSM id):


http://linkedgeodata.org/triplify/way<OSMid>

An example obtaining information about the Alte Mensa at TU Dresden is:



Obtain information about a particular point of interest (identified by its OSM id):


http://linkedgeodata.org/triplify/node<OSMid>

An example obtaining information about the Cafe B'liebig in Dresden is:



Different return formats are supported via content negotiation. Some examples for querying different return formats:


curl -LH "Accept: application/rdf+xml" http://linkedgeodata.org/triplify/way27743320
curl -LH "Accept: text/turtle" http://linkedgeodata.org/triplify/way27743320
curl -LH "Accept: text/plain" http://linkedgeodata.org/triplify/way27743320

Note: 'L' tells curl to follow redirects, 'H' is required to specify the accept header.

REST Interface


Obtain information about points of interest in a circular area:


http://linkedgeodata.org/api/3/intersects/%latitude%,%longitude%/%radius%

An example obtaining points of interest in a 1km radius around the center of Dresden is:



Obtain information about points of interest in a circular area having a certain property:


http://linkedgeodata.org/api/3/intersects/%latitude%,%longitude%/%radius%/%category%

Obtain information about points of interest in a circular area having a certain property value:


http://linkedgeodata.org/api/3/intersects/%latitude%,%longitude%/%radius%/%property%=%value%

An example obtaining pubs in a 1km radius around the center of Dresden is:



Obtain information about points of interest in a circular area belonging to a certain class:


http://linkedgeodata.org/api/3/intersects/%latitude%,%longitude%/%radius%/class/%class%

An example obtaining places of worship in a 1km radius around the center of Dresden is:



Obtain information about points of interest in a rectangular area:

(Currently only implemented for points)
http://linkedgeodata.org/api/3/intersects/<latmin>-<latmax>,<lonmin>-<lonmax>



Notes

  • latitude and longitude are WGS84 coordinates (do not use scientific notation e.g. 6.0221418E-23)
  • radius is in metres

Below functionality is currently not available


Additional filtering
Currently it is possible to filter by area, class and label.
Filtering by class or label is optional, however if filtered by both, the class must appear before the label:


/near/<area>[[/class/<className>][/label/<lang>/<matchPredicate>/<value>]]
<area> can be
  circular: <lat>,<lon>/<radius>
  rectangular: <latMin>-<latMax>,<lonMin>-<lonMax>

<className>
  any resource in the ontology namespace (e.g. if there is a resource lgdo:Amenity, then Amenity is the className)

<lang>
  a language tag, or the string "any" for all.

<matchPredicate> can be
  startsWith
  contains
  case sensitive versions (cstartsWith, ccontains)


Example: Find all amenities within the specified area, whose label contains the substring “ki” in any language:


http://linkedgeodata.org/page/near/51.033333,13.733333/1000/class/Amenity/label/any/contains/ki



 
There are no files on this page. [Display files/form]
There is no comment on this page. [Display comments/form]

Information

Last Modification: 2012-06-12 01:02:55 by Claus Stadler