Guy McGarva, EDINA National Data Centre
Rajendra Bose, DCC and School of Informatics
University of Edinburgh
Tuesday 15 May 2007
CLADDIER Project Workshop, Chilworth, Southampton, UK
Safeguarding the Citation Lifecycle for
Geospatial Repositories
Contents
• Issues
– Datasets vs. Features
• Citation of Geospatial Features
– OS MasterMap
®
example
• Dataset Citation
– Example using Go-Geo! and GRADE
Geospatial Dataset vs Geospatial Features
Citation may need to be at either Dataset or Feature
level because:
- You need to cite the dataset, if:
• Dataset is small (num. features, extent etc.)
• Whole dataset used in analysis
• Not feature based (e.g. raster/surface)
– But, you need to cite specific features, if:
• Only small extent from very large geodatabase
• Only specific features used in analysis
Geospatial Feature Citation
• Some Assumptions for features within a geospatial
repository:
– Every feature has a unique ID
• e.g. OS TOIDs (Topographic Object IDs)
– Features have version numbers/time-stamps
• Note: Talking about vector data that could be used
to produce cartographic products, but not the
journal article
citation creation
(future) discovery
of citation
citation included
in published work
retrieve/ resolve
citation
citation target
access a copy of
article held in a library or
institutional repository
journal article
article held in a library or
institutional repository
geospatial data
citation creation
(future) discovery
of citation
citation included
in published work
retrieve/ resolve
citation
citation target
reassemble geospatial
database contents
Author, 2006, Citation target,…
<web_link>
Author, 2006, Citation target,…
<web_link>
article held in a library or
institutional repository
journal article
data held in
geospatial repository
Citation lifecycle (broken) for geospatial data
D e l a w a r e , O h i o [ m a p ] . 1 8 8 5 . S c a l e n o t g i v e n . “ S a n b o r n F i r e I n s u r a n c e M a p s , 1 8 6 7 - 1 9 7 0 – O h i o ” . O h i o L I N K D i g i t a l M e d i a C e n t e r .
citation creation
(future) discovery
of citation
citation included
in published work
retrieve/ resolve
citation
citation target
reassemble geospatial
database contents
Author, 2006, Citation target,…
<web_link>
Author, 2006, Citation target,…
<web_link>
article held in a library or
institutional repository
journal article
data held in
geospatial repository
1
2
3
Citation lifecycle for geospatial data
toid="osgb1000042724588" version="2"
toid="osgb1000000334380650" version="1"
toid="rkb_20070328_2"
toid="rkb_20070329_1"
Sample Feature Data
e.g. OS MasterMap
Researcher_1
References:
Map1…
link
Jan 2007
Jan 2007
Jan 2007
<M>
…
GIS_1
base
data
Citation creation:
generation of
manifest
incorporation into
“bridge service”
web page (with
embedded
manifest)
<html>
…
citation in
publication links to
bridge service (via
doi?)
other data
source
<M>
…
= toid="osgb1000042724588 " version="2" toid="osgb1000000334380 650" version="1" toid="rkb_20070329_1" toid="rkb_20070328_2"where,
e.g. OS MasterMap
Bose, Rajendra. 2007. “Building geohazard data set”. University of Edinburgh Database
Group.
<link to manifest in bridge service that provides standard geospatial metadata>
Sample Citation
And 'bridge service', is a web site that provides access to geospatial
metadata
Where, 'manifest' is XML file containing list of feature
identifiers and version numbers
Example of how bridge service would work:
DNF Schema to support data association
Sample XML data based on DNF schema
-
can be used to transfer object identifiers and
version numbers
- can be used to associate users data with
reference data
Object Identifier
Version number
<gml:featureMember>
<!--This object contains a simple association with a version and a multiple association. The referenceLayer attribute is used to show that this object belongs to "Yon Layer".-->
<exaro:ExampleApplicationReferenceObject gml:id="yonr22222222" dnf:version="2" dnf:referenceLayer="Yon Layer"> <exaro:exampleProperty1>Some application layer specific information</exaro:exampleProperty1>
<exaro:meaningfulAssociationName>
<!--In addition to the idReference this association specifies an individual version of the object. It also indicates the referenceLayer attribute showing that the referred to object is in the layer "That Layer".-->
<dnf:SimpleAssociation xlink:href="#that11111111" dnf:version="2" dnf:referenceLayer="That Layer"/> </exaro:meaningfulAssociationName>
<exaro:meaningfulListName>
<!--The order of the sequence is the order in which the association appear in this file i.e. this is a sequence of objects that22222222, that11111111 and that33333333 in that order.-->
<dnf:SimpleAssociationList> <dnf:simpleAssociations>
<dnf:SimpleAssociation xlink:href="#that22222222" dnf:referenceLayer="That Layer" dnf:version="2"/> <dnf:SimpleAssociation xlink:href="#that11111111" dnf:referenceLayer="That Layer" dnf:version="3"/> <dnf:SimpleAssociation xlink:href="#that33333333" dnf:referenceLayer="That Layer" dnf:version="4"/> </dnf:simpleAssociations>
</dnf:SimpleAssociationList> </exaro:meaningfulListName>
