One of the advantages of the dwc_area:Area encoding, is that it creates one urn for each combination of lat, long, radius.
In practice, this is similar to one urn for each GPS reading.
An alternative way to get the same list would be a query that includes geo:lat, geo:long and radius.
Most people want to think of this as one thing, a point with a PointRadiusSpatialFit- type error measure.
I created this demonstration query that finds the BioBlitz observations with geo coordinates and sorts the resulting data by Observer.
It also allows you to pick and display different Areas from the list of returned records. *Note I have only 708 occurrence records with GPS coordinates.
* I still include the geo:lat and geo:long since most toolkits do not understand the proposed
ietf.org proposed geo standard.
Here is the query
select distinct ?s, ?o as ?image, ?class, ?order, ?family, ?sciname, ?cname, ?observer, ?lat, ?long, ?area where {
?s rdf:type txn:Occurrence.
?s txn:class ?class.
?s txn:order ?order.
?s txn:family ?family.
?s txn:hasScientificName ?sciname.
?s cc:attributionName ?observer.
?s geo:lat ?lat.
?s geo:long ?long.
?s txn:occurrenceHasArea ?area.
optional {?s foaf:depiction ?o.
?s txn:commonName ?cname.
}.
}
limit 708
-- Pete
------------------------------------------------------------------------------------
Pete DeVries
Department of Entomology
University of Wisconsin - Madison
445 Russell Laboratories
1630 Linden Drive
Madison, WI 53706
Email:
pdevries@wisc.eduTaxonConcept &
GeoSpecies Knowledge Bases
A Semantic Web,
Linked Open Data Project
--------------------------------------------------------------------------------------