http://creativecommons.org/licenses/by/3.0/ Megan Katsumi Ontology to capture concepts related to space. Reuses the GeoVocab Spatial ontology. November 29, 2016 iCity Spatial Ontology icity-spatial http://ontology.eil.utoronto.ca/icity/Spatial/ Reuses the GeoVocab Spatial Ontology. Copyright @ 2016 Megan Katsumi, iCity Research Group 1.0 Under development. Please see report on iCity Ontology v1. Annotation property added for organizational purposes, to identify annotation properties defined in the GeoVocab Spatial ontology. The WGS84 altitude of a SpatialThing (decimal meters above the local reference ellipsoid). altitude The WGS84 latitude of a SpatialThing (decimal degrees). latitude The relation between something and the point, or other geometrical thing in space, where it is. For example, the realtionship between a radio tower and a Point with a given lat and long. Or a relationship between a park and its outline as a closed arc of points, or a road and its location as a arc (a sequence of points). Clearly in practice there will be limit to the accuracy of any such statement, but one would expect an accuracy appropriate for the size of the object and uses such as mapping . location The WGS84 longitude of a SpatialThing (decimal degrees). longitude Relation C(x,y), read as 'x is connected with y'. This relation holds when two regions share a common point. It is the primitive relation in the RCC theory. connects with testing Relation DC(x,y), read as 'x is disconnected from y'. In order to prevent an exponential growth of triples when handling large amounts of data, a closed world assumption may also be possible. More precisely, by considering not explicitely connected regions as discrete regions. Moreover, discrete regions, which are not explicitely labeled as externally connected, would be considered disconnected from eachother. disconnected from testing Relation DR(x,y), read as 'x is discrete from y'. In order to prevent an exponential growth of triples when handling large amounts of data, a closed world assumption may also be possible. More precisely, by considering not explicitely connected regions as discrete regions. Moreover, discrete regions, which are not explicitely labeled as externally connected, would be considered disconnected from eachother. discrete from testing Relation EC(x,y), read as 'x is externally connected with y'. This relation holds, when the two regions share at least one common point of their borders, but share no points of their interiors, i.e. they do not overlap. externally connected with testing Relation x=y, read as 'x is identical with y'. This relation holds when two regions are spatially co-located. equals testing Relation NTPP(x,y), read as 'x is a non-tangential proper part of y'. This relation holds, whenever a region x is labeled as a proper part of a region y, and they do not share common point in their borders. is non-tangential proper part of testing Relation NTPPi(x,y), read as 'x non-tangentially properly contains y'. Inverse of the NTPP(x,y) relation. non tangentially properly contains testing Relation O(x,y), read as 'x overlaps y'. A region x overlaps a region y, if they share at least one common point of their interiors. overlaps testing Relation P(x,y), read as 'x is a part of y', holds whenever the region x is contained within the borders of the region y. is part of testing Relation PO(x,y), read as 'x partially overlaps y'. A region x overlaps a region y, if they share at least one common point of their interiors, and one does not contain the other within its borders. partially overlaps testing Relation PP(x,y), read as 'x is a proper part of y', means that the region x is contained within the borders of the region y, and region y is not contained within the borders of the region y, which means they are not equals. is proper part of testing Relation PPi(x,y), read as 'x properly contains y'. Inverse of the PP(x,y) relation. properly contains testing Relation Pi(x,y), read as 'x contains y'. Inverse of the P(x,y) relation. contains testing Relation TPP(x,y), read as 'x is a tangential proper part of y'. This relation holds, whenever a region x is labeled as a proper part of a region y, and they share at least one common point in their borders, which means that they are externally connected. is tangential proper part of testing Relation TPPi(x,y), read as 'x tangentially properly contains y'. Inverse of the TPP(x,y) relation. tangentially properly contains testing Although this relation is not a part of the RCC theory, it has been introduced in order to detect relations between regions which are inconsistent with the RCC axioms. inconsistent with unstable Property added for organizational purposes, to identify properties defined in the GeoVocab Spatial ontology. A geographical feature, capable of holding spatial relations. Feature testing Class added for organizational purposes, to identify classes defined in the GeoVocab Spatial ontology. $Date: 2009/04/20 15:00:30 $ A vocabulary for representing latitude, longitude and altitude information in the WGS84 geodetic reference datum. Version $Id: wgs84_pos.rdf,v 1.22 2009/04/20 15:00:30 timbl Exp $. See http://www.w3.org/2003/01/geo/ for more details. WGS84 Geo Positioning: an RDF vocabulary Recent changes to this namespace: $Log: wgs84_pos.rdf,v $ Revision 1.22 2009/04/20 15:00:30 timbl Remove the time bits which have been deal with elsewhere eg in iCal. Revision 1.21 2009/04/20 12:52:47 timbl try again Revision 1.20 2009/04/20 12:42:11 timbl Add Event (edited ages ago and never checked in), and location (following discussion http://chatlogs.planetrdf.com/swig/2009-04-20#T12-36-09) Revision 1.19 2009/04/20 12:36:31 timbl Add Event (edited ages ago and never checked in), and location (following discussion http://chatlogs.planetrdf.com/swig/2009-04-20#T12-36-09) Revision 1.18 2006/02/01 22:01:04 danbri Clarified that lat and long are decimal degrees, and that alt is decimal metres about local reference ellipsoid Revision 1.17 2004/02/06 17:38:12 danbri Fixed a bad commit screwup Revision 1.15 2003/04/19 11:24:08 danbri Fixed the typo even more. Revision 1.14 2003/04/19 11:16:56 danbri fixed a typo Revision 1.13 2003/02/19 22:27:27 connolly relaxed domain constraints on lat/long/alt from Point to SpatialThing Revision 1.12 2003/01/12 01:41:41 danbri Trying local copy of XSLT doc. Revision 1.11 2003/01/12 01:20:18 danbri added a link to morten's xslt rdfs viewer. Revision 1.10 2003/01/11 18:56:49 danbri Removed datatype range from lat and long properties, since they would have required each occurance of the property to mention the datatype. Revision 1.9 2003/01/11 11:41:31 danbri Another typo; repaired rdfs:Property to rdf:Property x4 Revision 1.8 2003/01/11 11:05:02 danbri Added an rdfs:range for each lat/long/alt property, http://www.w3.org/2001/XMLSchema#float Revision 1.7 2003/01/10 20:25:16 danbri Longer rdfs:comment for Point, trying to be Earth-centric and neutral about coordinate system(s) at the same time. Feedback welcomed. Revision 1.6 2003/01/10 20:18:30 danbri Added CVS log comments into the RDF/XML as an rdfs:comment property of the vocabulary. Note that this is not common practice (but seems both harmless and potentially useful). revision 1.5 date: 2003/01/10 20:14:31; author: danbri; state: Exp; lines: +16 -5 Updated schema: Added a dc:date, added url for more info. Changed the rdfs:label of the namespace from gp to geo. Added a class Point, set as the rdfs:domain of each property. Added XML comment on the lat_long property suggesting that we might not need it (based on #rdfig commentary from implementors). revision 1.4 date: 2003/01/10 20:01:07; author: danbri; state: Exp; lines: +6 -5 Fixed typo; several rdfs:about attributes are now rdf:about. Thanks to MortenF in #rdfig for catching this error. revision 1.3 date: 2003/01/10 11:59:03; author: danbri; state: Exp; lines: +4 -3 fixed buglet in vocab, added more wgs links revision 1.2 date: 2003/01/10 11:01:11; author: danbri; state: Exp; lines: +4 -4 Removed alt from the as-a-flat-string property, and switched from space separated to comma separated. revision 1.1 date: 2003/01/10 10:53:23; author: danbri; state: Exp; basic geo vocab geo A comma-separated representation of a latitude, longitude coordinate. lat/long