Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is it possible to convert more features to RDF along with geographic information by using TripleGeo? #5

Open
mesuresh opened this issue Jan 14, 2014 · 2 comments

Comments

@mesuresh
Copy link

Dear all,

I have converted shape file(.shp file) using tripleGeo tools. There are different shape files types(POINT, LINE, POLYGON).

For point type .shp file, it converted coordinates to RDF as shown below for point 42. But shape file also contain other features ( attributes seen using qgis tool) like name, airportID, class etc. Is it possible to convert other features as well like POINT long, lat, features.


http://agrinepaldata.com/gisGeom_point_42
a sf:Point ;
geo:asWKT "POINT (80.58499844842123 29.859203481982888)"^^geo:wktLiteral .

http://agrinepaldata.com/gispoint_42
a http://agrinepaldata.com/gisfeatureWithoutClass , geontology:Feature , http://agrinepaldata.com/gispoint ;
http://www.w3.org/2000/01/rdf-schema#label
"42"@en ;
http://agrinepaldata.com/gisname
"featureWithoutName"@en ;

geo:hasGeometry http://agrinepaldata.com/gisGeom_point_42 .

For line type and polygon type .shp files, I have same issue. there is also other attributes like POLOY1, POLY2 etc. and if possible, I want to convert them to RDF as well.


http://agrinepaldata.com/gisGeom_line_878
a sf:LineString ;
geo:asWKT "LINESTRING (82.37655639648438 28.477615356445312, 82.37582397460938 28.47881507873535, 82.3741226196289 28.483083724975586, 82.37492370605469 28.485795974731445, 82.37882995605469 28.488542556762695, 82.3797836303711 28.485862731933594, 82.38086700439453 28.48341178894043, 82.38408660888672 28.480989456176758, 82.38350677490234 28.476743698120117, 82.38198852539062 28.474708557128906, 82.37899017333984 28.475643157958984, 82.3770751953125 28.477397918701172, 82.37655639648438 28.477615356445312)"^^geo:wktLiteral .

http://agrinepaldata.com/gisline_878
a http://agrinepaldata.com/gisfeatureWithoutClass , geontology:Feature , http://agrinepaldata.com/gisline ;
http://www.w3.org/2000/01/rdf-schema#label
"878"@en ;
http://agrinepaldata.com/gisname
"featureWithoutName"@en ;

geo:hasGeometry http://agrinepaldata.com/gisGeom_line_878 .

Is there any way can we can convert others attributes besides coordinates to RDF as well?

Kind Regards,
Suresh Pokharel

@KostasPatroumpas
Copy link
Member

Saresh, thanks a lot for your feedback.

The current version of TripleGeo is intended to handle mainly geographic information. That's why, it can only support very few other attributes (i.e., identifiers, class, name). Support for more such attributes (i.e., non-spatial data columns) is among our plans for a future release, hopefully in a few months.

Regarding your second question, do all these POLY1, POLY2, etc. attributes contain geometries? TripleGeo can handle only one geometric column, which can be point, linestring, or polygon. As far as we know, this is the rule in most systems (both DBMS and GIS). Having more than one geographic representations for the same entity is rarely the practice in industry. Thus, we do not intend to support more than one geometric columns per file.

@Naurah
Copy link

Naurah commented Dec 9, 2015

HI..

just want to ask, for the class and name parameters, do they read only text/string data type?
and for ignore parameters, why do we set it UNK? does it mean unknown? Im sorry, but i really don't understand about that.
Then, based on what u say, that TripleGeo can handle only one geometric column but how about the the different column of coordinates that have latitude and longitude columns?

TQ in advance for answering my questions.. ;-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants