Upload
elfrieda-hampton
View
215
Download
0
Embed Size (px)
Citation preview
FGDC CAP Kickoff MeetingDenver, CO
September 28-29, 20041
Introduction to Metadata
Lynda WayneGeoMaxim / FGDC
2
Introductions
Name Organization Metadata Experience Workshop Expectations
3
Objectives
After the workshop, students can:
develop a metadata template that uses a range of mandatory, conditional, & optional CSDGM elements
effectively read and comprehend metadata
make the business case for metadata
discriminate between minimal and quality metadata
locate and access online resources
4
What IS Metadata?
Data ‘reporting’
WHO created the data?
WHAT is the content of the data?
WHEN was it created?
WHERE is it geographically?
HOW was the data developed?
WHY was the data developed?
5
What IS Metadata?
title
supplemental information
abstract
time period
author
sources
(file) size
6
What IS Metadata?
entity
attributes
view actual metadata record
7
Let’s Make Metadata
Turn to your neighbor and document the following:
Title (name) Theme Keywords (work, play,
life) Supplemental Information
8
Value of Metadata
Preserves investments in geospatial data development
people forget…………..people move on
9
Value of Metadata
Serves as a valuable resource to data use and analysis
10
Projection?
Attributes?
Time Period?
Value of Metadata
Provides data consumers & stewards:
• a common language • a context for data resources• needed information about the
data Albers, I think?
Yes
I’ll have get back to you…
11
Value of Metadata
Supports data management• maintenance and update• project status• value assessment / cba• project estimates• deliverable and performance measures
12
Value of Metadata
13
Who creates metadata?
OfficiallyFederal organizations producing digital geospatial dataFederally funded projects that produce digital geospatial data
Morally and practicallyAnybody that creates digital data
It’s the right thing to do!
14
Why metadata?
Be a part of the BIG picture
Federal Geographic Data Committee (FGDC)- coordinates national geospatial data development
National Spatial Data Infrastructure (NSDI)- creation and distribution of seamless national
geospatial dataGlobal Spatial Data Infrastructure (GSDI)- creation and distribution of seamless global
geospatial data
15
Why metadata?
National Spatial Data Infrastructure
Old perspective………………….
……………………………….New perspective
16
Why metadata?
NSDI Framework Data- cooperatively-designed data dictionaries for
seven key ‘reference’ themes
• Elevation and Bathymetry
• Hydrography
• Geodetic Control
• Cadastral
• Transportation
• Governmental Units
• Orthoimagery
17
Why metadata?
NSDI Geospatial Data Clearinghouse- international network of metadata distribution ‘nodes’
• FGDC• EROS• ESRI• NRCS• NOAA CSC• ALASKA GDC
internationalGINA
AGDC
ASGDC
Anchorage state / local
national
query
available metadata records
user internet Clearinghouse nodes
18
Why metadata?
NSDI Geospatial One Stop
metadata and links to data webmapping services data acquisition plans data category communities
…..fast tracking the NSDI
19
Why Metadata?
FGDC
Geospatial One-stop
National Map
data
access
coordinationnation
al •
sta
te •
loca
l • p
riva
te
metadata • services • com
munity
policies • standards • partnerships
20
How Do I Create Metadata?
the metadata gospel…
It’s not pretty
It’s not easy
But sure is thorough…..
CSDGM
ISO
21
CSDGM
1. Identification InformationGeneral bibliographic information including:
title, originator, data contact, status, date, time period of content, abstract, purpose, keywords, geographic location
2. Data Quality InformationLineage and data assessments
sources, process methods, accuracy, data processing contact
22
CSDGM
3. Spatial Data OrganizationData format:
vector, point, raster
4. Spatial Reference InformationCoordinate system parameters:
horizontal / vertical coordinate system, projection, datum
23
CSDGM
5. Entity and Attribute InformationDatabase design
entities, attributes, domains, description of data values
6. Distribution InformationHow to acquire the data
distribution contact, available formats, online distribution website, costs
24
CSDGM
7. Metadata Reference Information
General information about the metadata record itselfmetadata contact, metadata standard used, metadata creation date, metadata review date
25
CSDGM Elements
26
CSDGM Elements
27
CSDGM Elements
28
CSDGM Elements
Turn to page 35 in the Green Book
29
CSDGM Elements
30
CSDGM Elements
Calendar DatesYYYYMMDD
Time of DayHHMMSSSS
CoordinatesLat/Lon Decimal Degrees
Network addresses & file namesService://hostname:port/path/filename
31
CSDGM Production Rules
16
What’s Mandatory? What’s Not?
Mandatory if Applicable - must be provided if the data set exhibits the defined characteristic.
Optional - provided at the discretion of the data set producer.
Mandatory - must be provided.
MeaningData
ElementCompoundElement
10/06/95
32
CSDGM Production Rules
24
Using the Graphics to Make Decisions - 1
All elements are colored yellow, so all are mandatory and must be reported.
M M / A O
CompoundElement 1
CompoundElement 1.1
DataElement 1.1.1
DataElement 1.1.2
DataElement 1.2
10/06/95
33
CSDGM Production Rules
26
Using the Graphics to Make Decisions - 2
Compound Element 1 is mandatory.
Compound Element 1.1 is optional. The producer must decide if it wants to provide the element.
If yes, Data Elements 1.1.1 and 1.1.2 are mandatory.
If no, do not report Compound Element 1.1, Data Element 1.1.1 or 1.1.2, and skip to Data Element 1.2.
Data Element 1.2 is mandatory. M M / A O
CompoundElement 1
CompoundElement 1.1
DataElement 1.1.1
DataElement 1.1.2
DataElement 1.2
10/06/95
34
CSDGM Production Rules
28
Using the Graphics to Make Decisions - 3
Compound Element 1 is mandatory.
Compound Element 1.1 is mandatory.
Data Element 1.1.1 is mandatory.
Data Element 1.1.2 is mandatory if applicable. The producer must decide if the data set has the characteristic defined by the data element. If yes, then Data Element 1.1.2 is mandatory. If no, then Data Element 1.1.2 is not reported.
Data Element 1.2 is optional. M M / A O
CompoundElement 1
CompoundElement 1.1
DataElement 1.1.1
DataElement 1.1.2
DataElement 1.2
10/06/95
35
CSDGM Production Rules
30
Using the Graphics to Make Decisions - 4
Compound Element 1 is mandatory if applicable. If not applicable to the data set, do not report any elements. If applicable, it is mandatory and:
Compound Element 1.1 is mandatory.
Data Element 1.1.1 is mandatory if applicable. If not applicable, do not report it. If applicable, it is mandatory.
Data Element 1.1.2 is mandatory.
Data Element 1.2 is optional. M M / A O
CompoundElement 1
CompoundElement 1.1
DataElement 1.1.1
DataElement 1.1.2
DataElement 1.2
10/06/95
36
CSDGM
37
CSDGM
Section One: Identification
Elements you use to ‘shop’ for a data set of interest:
WHO ? title, originator, publication date
WHAT ? abstract, keywords, native data set (software)
environment
WHERE ? geographic extent (mbr), browse graphic
WHEN ? time period of content
Availability? access/use constraints, status
38
CSDGM
39
CSDGM
Section Two: Data Quality
How was the data set developed?• Source Information
• Data processing
What checks were made of the data set?• Logical Consistency
• Positional Accuracy
• Attribute Accuracy
40
CSDGM
41
CSDGM
Section Three: Spatial Data Organization
Point, Line, or Vector?
42
CSDGM
43
CSDGM
Section Four: Spatial Reference Information
Coordinate System
44
CSDGM
45
CSDGM
Section Five: Entity & Attribute Information
Database Description
46
CSDGM
47
CSDGM
Section Six: Distribution Information
How can I get the data set?• Distribution Contact Information
• Available Formats (digital and hardcopy)
• Standard and Custom Order Processes
• Online option
• Offline media
• Distribution Liability
• Fees
48
CSDGM
49
CSDGM
Section Seven: Metadata Information
Elements that describe the metadata record itself:
WHO wrote the metadata record
WHAT metadata standard was used?
WHEN was the metadata created/updated?
Is the metadata available?
metadata access and use constraints
50
CSDGM
51
CSDGM
Supporting Sections
Eight: Citation InformationTitle, Originator, Publisher
Nine: Time Period InformationDate and Hour
Ten: Contact InformationName, Job Title, Address, Phone, Email
52
CSDGM
53
Metadata Collection Tools
Shareware corpsmet - USACE tkme / xtme - USGS/FGDC NPSmeta (ArcCatalog Extension) MetaD - ISO
54
Metadata Collection Tools
GIS Internal ESRI ArcCatalog Intergraph SMMS for
Geomedia
55
Metadata Collection Tools
SoftwareCommercial SMMS Data Logger Blue Marble
56
Metadata Collection Tools
Forms hardcopy or online
57
Metadata Validation Tools
mp - Metadata Parser Checks for CSDGM syntax
Element namesMandatory elementsElement content (domains and logical consistency)
Embeds tags for NSDI Clearinghouse Distribution
cns – Chew ‘N Spit Rectifies indentationInserts capitalization and underbars
FGDC ‘compliant’ metadata must pass mp!
58
Metadata Resources:The Greenbook
An easy to use guide to implementing the CSDGM (is not the standard itself)
Background and Descriptive Information CSDGM history, value of meta, formats
CSDGM Elementsdefinitions, domains, FAQs, common values
Sample MetadataNWI and DGL
Glossary of Terms
59
Metadata Resources:Online Resources
http://www.fgdc.gov/metadata//online_resources
tutorialsmetadata guidance websitessoftwarepublicationsthesauri sources
60
Making Metadata Part of the Process
New tools enable us to better integrate metadata creation into the data development process
61
Making Metadata Part of the Process
If metadata were collected throughout the data process…
1.more accurate (no guessing)2.more details3.better decision-making.
metadata
62
Making Metadata Part of the Process
But what can I do to better incorporate metadata into the data development process?
63
Make the business case:• preserve data investments• limit data liability• manage data resources• find new data resources• easier data transfer• more efficient data distribution
step one:build adminstrative
support
64
Emphasize individual benefits:
• reduce workload..in the long term• field fewer data inquiries• document personal contributions
step two:build technical support
65
Support your staff• include in job descriptions &
performance measures• provide
staff supporttoolstraining
step two:build technical support
66
For each common data type: identify pertinent fields populate fixed fields
standardized language distribution methods standards used
build source and contact libraries
step three:create organizational
templates
67
map fields to the work flow establish and assign responsibilities
technicians - lineage analyst - process methodology field scientists - accuracy
assessments IT managers - tools, collection,
management
step four:distribute the effort
68
step four:distribute the effort
Data Planning:Section 1: Identification Info
title originator purpose content time period
theme keywords abstract
69
step four:distribute the effort
Data PlanningSection 3: Data Organization Indirect Spatial Reference
FIPS codes, county monikers, etc Object-type
point, vector, or raster
70
step four:distribute the effort
Data PlanningSection 5: Data Organization Entities and Attributes
database design and configurationHighways name surface [asphalt, concrete, unpaved] year_built restrictions [haz, 2axle, flood] district [A, B, C, D, E]
71
step four:distribute the effort
Data ProcessingSection 2: Data Quality completeness report
missing or omitted data positional accuracy
digitize rms error, GPS triangulation, survey/photogrammetry/IP method
72
step four:distribute the effort
Data ProcessingSection 2: Data Quality lineage
data set source filesdata compilation process
mapsphotos
dbases GIS
73
step four:distribute the effort
Data AnalysisSection 2: Data Quality attribute accuracy
field checks, cross-checks, statistical analyses
lineagedata analysis process
74
step four:distribute the effort
Data AnalysisSection 3: Data Organizations object type
number of points, pixels, lines
Section 5: Entity and Attributesattribute values
75
step four:distribute the effort
Data AnalysisSection 7: Metadata Reference
metadata contact and dates
76
Managers Can WRITE metadata data planning fields
title abstract purposegeographic extent keywordsand many more…
and manage the effort metadata coordination metadata enforcement
step five:lead by example
77
Establish Policies: mandate use of standards and templates develop boilerplate metadata deliverable
language for data contractors require units to publish their metadata publish metadata SOP to document policies and procedures
step six:policies and procedures