IFLA Section of Geography and Map Libraries
If you have any suggestions, comments or items that you would like to see added to this collection, please direct your messages to: libmap1@uconnvm.uconn.edu

Title	Digital Map Librarianship: Metadata : Typology of metadata for cartographic and spatial data
Colour	Colour intensities in Band One to Four signify use by mapcurators/librarians/spatial data specialists Quality Simple =========> =========> Rich Quality Level Band One Band Two Band Three Band Four Diffusion =========> =========> <========= <========= Availability Internet Internet Internet / Intranet Internet / Intranet Purpose Location Selection Evaluation Analysis Unit of information Individual digital information object Logical set of digital objects; no links between documents Publication; links between whole and parts Databases with links between whole and parts on all levels Standards proprietary emerging standards generic standards used in information world standards used in specialist subject domains Form of record Proprietary simple records Dublin Core ISBD FGDC, CEN, ISO Format * Unstructured Attribute value pairs (Dublin Core DTD) Subfields, qualifiers (MARC), (USMARC), (UKMARC), (UNIMARC) Highly structured mark up (Base DTD) Input Robot generated Robot plus manual input Manually input High level of manual input Protocol http with CGI form interface directory service protocols (whois++) with query routing (Common Indexing Protocol) Z39.50 Z39.50 (in future with collection navigation) User Community Internet-surfers Producers Libraries / Cartographic Information Centers Producers / Documentation Centres / Clearinghouses Modified after BIBLINK - LB 4034, D1.1 Metadata Formats. 23 December 1996. * A review of description formats for various kinds of metadata can be found in the document A review of metadata: a survey of current resource description formats, which is deliverable RE 1004 of the DESIRE project (Development of a European Service for Information on Research and Education). (Abstract: This study provides background information to the DESIRE project to enable the implications of using particular metadata formats to be assessed. Part I is a brief introductory review of issues including consideration of the environment of use and the characteristics of metadata formats. A broad typology of metadata is introduced to provide a framework for analysis. Part II consists of an outline of resource description formats in directory style. This includes generic formats, but also, to give an indication of the range of development, domain-specific formats. The focus is on metadata for 'information resources' broadly understood rather than on the variety of other approaches which exist within particular scientific, engineering and other areas.). Band Two should be used for images which are put on the Internet. The metadata may derive from existing ISBD(CM) descriptions. When the images are downloaded for archiving in the local electronic collection Band Two metadata should be enriched to create ISBD(CM) descriptions. Band Three should be used for all images, whether analogue or electronic, which are part of the local collection. The metadata may be enriched Band Two data, prime ISBD(CM) data or data extracted from Band Four descriptions. In case of a Cartographic Information Center Band Three data may also pertain to items which are not actually held by the Center, as this functions as a one-stop-shop for more than one collection. Band Four should be used for databases, raster or vector or a combination thereof, where the metadata are mainly created to evaluate and facilitate transfer of data.
The Dublin Core Elements	The Dublin Core Elements Subject The topic addressed by the work. Title The name of the object. Author The person(s) primarily responsible for the intellectual content of the object. Publisher The agent or agency responsible for making the object available in its current form. Other Agent The person(s), such as editors, transcribers, and illustrators who have made other significant intellectual contributions to the work. Date The date of publication. Object type The genre of the object, such as novel, poem or dictionary. Form The physical manifestation of the object, such as PostScript file or Windows executable file. Identifier String or number used to uniquely identify the object. Relation Relationship to other objects. Source Objects, either print or electronic, from which this object is derived, if applicable. Language Language of the intellectual content. Coverage The spatial location and/or temporal duration characteristics of the object. The 1995 Dublin Metadata Workshop is described in greater detail in: [Weibel, et al. 1995] and [WEIB95b] . The reference description of the element set can be found at: http://purl.org/metadata/dublin_core_elements
HTML	Elements can have the form of: <META NAME="TITLE" CONTENT="The creation and integration of metadata in spatial data collections"> or <META name = "DC.title" content = "The Warwick Metadata Workshop: A framework for the deployment of resource description"> Unfortunately the core-elements only are named or defined but their contents has not been normalized. This means that there are no schemes behind the content which prescribe how the data has to be processed. E.g <META name = "DC.author" content = "Jan Smits"> or <META name = "DC.author" content = "Smits, Jan"> or <META name = "DC.author" content = "Smits, J.">. It is even worse, of course, when no scheme is mentioned in <META name = "DC.subject" content = "......">. This matter is somewhat more comprehensibly discussed in Metadadata: to be, or not to be (catalogued) / Gordon Dunsire. All my web-documents begin presently with this template in my HTLM-editor: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN//3.2"> <HTML> <HEAD><TITLE></TITLE> <META NAME="TITLE" CONTENT="............."> <META NAME="AUTHOR" CONTENT="................"> <META NAME="ADMIN" CONTENT="Jan Smits"> <META NAME="DEPT" CONTENT="SKD"> <META NAME="KEYWORDS" CONTENT="................."> <META NAME="DATE" CONTENT="YYYY-MM-DD"> </HEAD> <BODY> <img src="/kb/graphics/karto-nl" alt="Kartografische Collectie"> <HR> <P> Text or image <P> <HR> <P> <a href="file name"><img src=""/icons/alexeng.gif" border=0 alt ="[nederlands]"></a> <a href="/kb/kbinfo/comment-nl.html"><img src="/icons/alexhelp.gif" border=0 alt="[helpdesk]"></a> <a href="/home-en.html"><img src="icons/alexnaam.gif" border=0 alt="[home]"></a> </BODY> </HTML> The template includes automatically logo's and end-buttons.
ISBD	The ISBD-description of the "Digital topographic subject map of The Netherlands" might look something like this: [Digital topographic subject map of The Netherlands] / Topografische Dienst Nederland. - Situation on 31-12-1992. - Representational scale 1:5,000 to 1:25,000, standard deviation 1.8 m ; with coordinates of the shifted Dutch triangulation system (E 3 20-E 7 15/N 53 35-N 50 45). - Emmen : Topografische Dienst Nederland, 1991-... - ca. 1,980 Mb data. Mapping scale 1:10,000. Update: depending on area 4, 6 or 8 years; the update programme is drawn up according to the present requirements of the Ministry of Defence. Extent of database: urban area ca. 1.6 Kb per hectare; rural area ca. 0.3 Kb per hectare. Format of delivery: SUF2, DGN (microstation format), DXF, DWG (autocad format); 9 inch magnetic reeltape, Exabite (8 mm cassette); small files on diskette. Deliverable on 31-12-1992: Sheet 9W, 9O, 14W, 14O, 15W, 19W, 19O, 20W (excl. Texel); delivery per sheet or part thereof. Language: English Contents: Coded vector-database with all topographic point-, line- and area- information, as is represented on the present maps of 1:10,000 and 1:25,000; classification of several topographic features ('layers') such as roads, water, buildings, etc.; within each theme there is subcoding. Structure: All line-segments are noded and, when they have an identity of their own, fitted with their own coding; the polygons (objects) which thus are created are coded with a centroid. Literature: Van basisbestand naar kernbestand : de Topografische Dienst als producent van een kernbestand 1:10.000 / P.W. Geudeke. In: Kartografisch tijdschrift, 1993.XIX.2, pp. 24-28. Classification: <4.210>; 273 Sign. DNP: KC4.210    -0000/001/00000/00/1991/1                          D9400001 From: SMITS, Jan. Describing digital maps with ISBD and MARC: problems and possible solutions. The LIBER Quarterly 5(1995)3, pp. 292-311.
UNIMARC	The UNIMARC-description of the "Digital topographic subject map of The Netherlands" might look something like this: TAG  1  2  SF  TEXT 001                 D9400001 020          $a    NL$D9400001 100    * * $a    19940101i19919999u**a*engy01******BA 101    1 * $a    eng$cdut 102    * * $a    NL 120    * * $a    byygk**afaa**ba 121    * * $a    a*ahyyxz 122    2 * $a    d1986******$ad9999****** 123    3 * $a    D$b00005000.000025000$de00320**$ee00715**$fn5335**$gn5045**$02M 124    * * $a    a$bd$cacai$hbc$iz 131    * * $a-l  ? 135    * * $a    c 200    1 * $a    [Digital topographic subject map of The Netherlands] - $b[Cartographic Material] $fTopografische Dienst Nederland 205    * * $a    Situation on 31-12-1992 $r19921231 206    * * $a    Representational scale 1:5,000 to 1:25,000, standard deviation 1.8 m, stereographic proj., with coordinates of the shifted Dutch triangulation system (E 3 20-E 7 15/N 53 35-N 50 45) 210    * * $a    Emmen$cTopografische Dienst Nederland$d1991-... 215    * * $a    Ca. 1,980 Mb data 305    * * $a    Update: depending on area: 4, 6 or 8 years; the update programme is drawn up according to the current require ments of the Ministry of Defence 307    * * $a    Extent of database: urban area ca. 1.6 Kb per hectare, rural area ca. 0.3 Kb pe hectare 310    * * $a    Deliverable on 31-12-1992: Sheet 9W, 9O, 14W, 14O, 15W, 19W, 19O, 20W (excl. Texel); delivery per sheet or part thereof 315    * * $a    Mapping scale 1:10,000 327    1 * $a    Contents: coded vector-database with all topographic point-, line and area-information, as is represented on the present maps of 1:10,000 and 1:25,000; classification of several topographic features ('layers') such as roads, water, buildings, etc.; within each theme there is subco ding; structure: all line-segments are noded and, when they have an identity of their own, fitted with their own coding; the polygons (objects) which are thus created are coded with a centroid 337    * * $a    Format of delivery: SUF2, DGN (microstation format), DXF, DWG (autocad format); classic 9 inch magnetic tape, Exabite (8 mm cassette); small files on diskette 488    * * $a    REFERENCE LITERATURE : Van basisbestand naar kernbestand: de Topografische Dienst als producent van een kernbestand 1:10.000 / P.W. Geudeke. In: Kartografisch tijdschrift, 1993,XIX.2, pp. 24-28 675    * * $a    273$v3$zDUT 686    * * $a    <4.210> $dcck 710    0 2 $a    NA098714$aNederland (state)$bTopografische Dienst Nederland$c(civil service)$4180 801    * 0 $a    NL$bCCK$c19940901$gISBD(CM) Italics are information added to the current Unimarc-format. For explanation see: SMITS, Jan. Describing digital maps with ISBD and MARC: problems and possible solutions. The LIBER Quarterly 5(1995)3, pp. 292-311.
Suggested Citation	Smits, Jan, "The creation and integration of metadata in spatial data collections." Digital Map Librarianship: a working syllabus, 63rd IFLA Conference, Copenhagen, Denmark. (18, Aug. 1997) <http://magic.lib.uconn.edu/ifla/meta-table.htm>

Jan Smits Koninklijke Bibliotheek The Hague jan.smits@konbib.nl