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

Missing geo data in lobid GND data: blank nodes lost during conversion from ntriples to json-ld #503

Closed
dr0i opened this issue Jul 4, 2014 · 3 comments
Labels

Comments

@dr0i
Copy link
Member

dr0i commented Jul 4, 2014

In the GND reside some geo data, see e.g. http://d-nb.info/gnd/4074335-4.
In lobid this data is missing , see e.g. http://lobid.org/subject?id=4074335-4, also the data is correctly loaded into hdfs - try:

hduser@weywot1:~$ hadoop fs -cat extlod/gnd/407.nt | grep 4074335-4 | grep hasGe

This yields the triple:

<http://d-nb.info/gnd/4074335-4> <http://www.opengis.net/ont/geosparql#hasGeometry> _:BX2D7baa6ceeX3A1464867c069X3A2440 .

After the conversion to json-ld, thsi triple is missing

hadoop fs -cat output/json-ld-gnd/* | grep '"@value":"(DE-588c)4074335-4' | grep hasGe

It seems that blank nodes are lost when ntriples are converted to json-ld.

@dr0i
Copy link
Member Author

dr0i commented Aug 28, 2014

Bnodes are generally a problem - see e.g. http://api.lobid.org/resource/HT014818440. Would call that "dangling bnode".

@acka47
Copy link
Contributor

acka47 commented Nov 4, 2015

Werner Greßhof reported multiple times that he would be happy to have the geodata in GND.

@acka47
Copy link
Contributor

acka47 commented Jul 12, 2017

This will be fixed in 2.0, wonÄt be fixed in 1.0. Closing.

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

No branches or pull requests

2 participants