Location Table

Source: CORVEG.LOCATION

Example row:

LOCATION_ID	DERIVATION_ID	MAP_NAME	MAP_NUMBER	MAP_SCALE_ID	PASTORAL_DISTRICT	LOCALITY	LOCATION_PRECISION	LOCATION_ZONE	EASTING	NORTHING	LATITUDE	LONGITUDE	UPDATE_USER	LAST_UPDATE	BIOREGION_ID	IS_DD_ORIGINAL	PROJECT_ID

LOCATION_ID	DERIVATION_ID	MAP_NAME	MAP_NUMBER	MAP_SCALE_ID	PASTORAL_DISTRICT	LOCALITY	LOCATION_PRECISION	LOCATION_ZONE	EASTING	NORTHING	LATITUDE	LONGITUDE	UPDATE_USER	LAST_UPDATE	BIOREGION_ID	IS_DD_ORIGINAL	PROJECT_ID
3614	2	CAPE MELVILLE	7968	2	COOK	APPROXIMATELY 8 KM NW OF CAPE FLATTERY TOWNSHIP, ON THE ROAD TO LOOKOUT POINT		55	311895	8348476	-14.97486704	145.2510978	5	2007-05-18 13:08:00	4	0	265

Interpretation in TERN Plot Ontology

Encoding each row in RDF requires:

A plot:Location to capture most of the column values with its datatype properties.
A geosparql:hasGeometry to capture the latitude and longitude coordinates.
A plot:locationMethod to capture the method used to determine the location.
A plot:Location is location of a plot:Site (plot-x:isLocationOf)

RDF Example

@prefix corveg-cv: <http://linked.data.gov.au/def/corveg-cv/> .
@prefix corveg-location: <http://linked.data.gov.au/dataset/corveg/location/> .
@prefix dct: <http://purl.org/dc/terms/> .
@prefix geo: <http://www.w3.org/2003/01/geo/wgs84_pos#> .
@prefix geosparql: <http://www.opengis.net/ont/geosparql#> .
@prefix locn: <http://www.w3.org/ns/locn#> .
@prefix plot: <http://linked.data.gov.au/def/plot/> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .

corveg-location:l-13727 a plot:Location ;
    rdfs:label "Location 13727" ;
    plot-x:isLocationOf corveg-site:site-13864 ;
    plot:locationMethod corveg-cv:bfdac18b-eb08-4842-8a7c-0f0571379b61 ;
    plot:mapScale corveg-cv:c010e5db-04c7-4bdb-a492-e7aa1d2a0d32 ;
    plot:mapsheetName "SCORIA" ;
    plot:mapsheetNumber "9048" ;
    dct:description "COPPIN LOGGING AREA, COOMINGLAH STATE FOREST NORTHWEST OF MONTO (TSP)." ;
    dct:identifier 13727 ;
    geosparql:hasGeometry [ a geo:Point ;
            geo:lat -24.77091153 ;
            geo:long 150.95303268 ] ;
    locn:geographicName "BURNETT" .

Mapping Table

Source Column	Destination RDF Predicate	Comments

Source Column	Destination RDF Predicate	Comments
`LOCATION_ID`	`dct:identifier`	Encoded in the URIs of the `plot:Location` instance, displayed in the `rdfs:label`, and also encoded as `dct:identifier` for querying purposes.
`DERIVATION_ID`	`plot:locationMethod`	Domain: `plot:Location` Range: A narrower value of Location Coordinate Methods matching on the `skos:hiddenLabel`.
`MAP_NAME`	`plot:mapsheetName`	Domain: `plot:Location` Range: String literal
`MAP_NUMBER`	`plot:mapsheetNumber`	Domain: `plot:Location` Range: String literal
`MAP_SCALE`	`plot:mapScale`	Domain: `plot:Location` Range: A narrower value of Mapscale Values matching on the `skos:hiddenLabel`.
`PASTORAL_DISTRICT`	`locn:geographicName` attention - Simon Cox removed this predicate from the Plot Ontology. We may need to ask him to add it back in. He wanted to reduce the number of namespaces used and switched `locn:geometry` out for `geosparql:hasGeometry` and at the same time, removed `locn:geographicName`.	Domain: `plot:Location` Range: String literal
`LOCALITY`	`dct:description`	Domain: `plot:Location` Range: String literal
`LOCATION_PRECISION`	attention - May need to create a new property in `plot:Location` to capture `LOCATION_PRECISION` (GPS error). We could capture it as a `sosa:Observation` but then we would need to make `plot:Location` a sub-class of `sosa:FeatureOfInterest` or `sosa:Sample` to allow for a connection to the `ssn-ext:ObservationCollection`.	Not captured by TERN Plot Ontology. Custodian comment: This is precision or accuracy in meters of the site location. These days it is the error provided by the GPS.
`LOCATION_ZONE`		Not captured by TERN Plot Ontology. Can be derived from latitude and longitude.
`EASTING`		Not captured by TERN Plot Ontology. Can be derived from latitude and longitude.
`NORTHING`		Not captured by TERN Plot Ontology. Can be derived from latitude and longitude.
`LATITUDE`, `LONGITUDE`	`geosparql:hasGeometry`	Domain: `plot:Location` Range: `geo:Point` instance `geo:lat`: latitude value `geo:long`: longitude value
`UPDATE_USER`		Not captured by TERN Plot Ontology.
`LAST_UPDATE`	`dct:modified`	Database entry or last modified time. Encoded with literal as type `xsd:dateTime`.
`BIOREGION_ID`	`ssn-ext:hasUltimateFeatureOfInterest`	Domain: `plot:Location` Range: concept in concept scheme Queensland Bioregions matching on the `skos:hiddenLabel`.
`IS_DD_ORIGINAL`		Not captured by TERN Plot Ontology. Custodian comment: This is a field which indicates if Decimal Degrees is the original source of the coordinate location. I assume this is used in the process of calculating the Easting and Northings or vice versa. I would not think that this is useful for users.
`PROJECT_ID`		Not captured by TERN Plot Ontology. Custodian comment: Projects are an internal way of organising our sites for our benefit. No use to users

Action Items

@Edmond Chuc (Unlicensed) Ask Simon if he can add in locn:geographicName or if there is another existing property that is suitable.

@Edmond Chuc (Unlicensed) Determine if capturing LOCATION_PRECISION is worthwhile. If yes, then contact Simon to make changes to the Plot Ontology.