Skip to content
This repository has been archived by the owner on Jun 23, 2020. It is now read-only.

Geodata from DNB isn't included in API data yet #396

Closed
acka47 opened this issue Mar 26, 2014 · 4 comments
Closed

Geodata from DNB isn't included in API data yet #396

acka47 opened this issue Mar 26, 2014 · 4 comments
Assignees

Comments

@acka47
Copy link
Contributor

acka47 commented Mar 26, 2014

rapper -o turtle http://d-nb.info/gnd/4074335-4 yields (excerpt):

<http://d-nb.info/gnd/4074335-4>
    gndo:preferredNameForThePlaceOrGeographicName "London" ;
    gndo:variantNameForThePlaceOrGeographicName "Londinium" ;
    geo:hasGeometry [
        geo:asWKT "Point ( -000.125740 +051.508530 )"^^geo:wktLiteral ;
        a sf:Point
    ] ;
    a gndo:TerritorialCorporateBodyOrAdministrativeUnit ;
    owl:sameAs <http://sws.geonames.org/2643743> ;
    foaf:page <http://de.wikipedia.org/wiki/London> .

We neither have the geo coordinates nor the links to geonames in the data.

See also http://de.slideshare.net/larsgsvensson/enriching-thegermannationallibraryslinkeddataservicewithgeographiccoordinates.

@dr0i
Copy link
Member

dr0i commented Mar 28, 2014

The gnd data is not transformed, just converted into ntriples. I looked it up and can confirm that the geo data of 4074335-4 resides in the hdfs as ntriples.

@acka47
Copy link
Contributor Author

acka47 commented Mar 28, 2014

I will also add the new properties to the JSON-LD context, see #398.

@acka47
Copy link
Contributor Author

acka47 commented Nov 21, 2014

Still missing, see http://lobid.org/subject?id=4074335-4.

@acka47
Copy link
Contributor Author

acka47 commented Nov 21, 2014

Duplicate to #503. Closing.

@acka47 acka47 closed this as completed Nov 21, 2014
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants