Transcript How Geospatial Standards are Created: A brief history of

Chris Cialek & Mark Kotz
Standards Committee
January 11, 2011
Year
Standard
1997 Codes for MN Counties
1998 State Agency Coordinate Interchange
1998 Geographic Metadata
2000 Positional Accuracy
1994 Codes for the Identification of States
2002 Codes for Lake and Wetland Basins
2006 Codes for Watersheds
2008 River Reach/Water Course IDs
2009 City,Township and Unorganized Territory Identifiers
2009 U.S. National Grid
- Stormwater Conveyance
- Thoroughfare, Landmark, and Postal Address Data Standard
- MN Geocode Model
Governor’s Council on Geographic Information



Created by E.O. in 1991
Representing MN’s Geospatial Community
Sectors: State, County, Local, Private, Federal, Academic
Work conducted by Thematic Committees
Standards Committee Strategic Plan
"In order to encourage the sharing of information among government
agencies in Minnesota and to reduce costs and avoid duplication of
effort, the Governor's Council will commission the development and
implementation of STANDARDS . . . to be used for the development,
exchange, analysis and output of geographic information."
Roles and Responsibilities

Committee - Identify needs, work with SMEs to develop
solution, facilitate public review, recommend to GCGI, promote

GCGI - Evaluate committee recommendations; approve on
behalf of the GI Community, recommend results to IPO

IPO - Evaluate and sanction standards brought to it by GCGI

State Agencies - Be involved in process; agree to commit to
sanctioned standards

Local Government, Private sector, etc – Invited to get
involved; encouraged to commit
Approved Process for Developing Policies, Standards and Guidelines
Approved Process
for Developing Policies, Standards and Guidelines
Problem / Need
Identified
need
Identified
need
GI Council
Agency
"Community
of interest"
Office of
Technology
Stakeholder/
partner input
IPC
1.0
Propose Policy,
Standard or
Guideline
Sponsor
Proposed policy,
standard or guideline
Admin
Reviewer
input
Responsible
authority input
2.0
Develop Policy,
Standard or
Guideline
Proposed Policies,
Standards and
Guidelines
Developed policy,
standard or guideline
IPC formal
recommendations
External
reviewer input
(comes from
external sources)
3.0
Adopt Policy,
Standard or
Guideline
Developed Policies,
Standards and
Guidelines
OT/Admin adopted policy,
standard or guideline
LEGEND:
= out of scope
Adopted Policies,
Standards and
Guidelines
4.0
Implement Policy,
Standard or
Guideline
= process
= data / information (store)
= organization / stakeholder
\\adm-data.admin.state.mn.us\admindept\gda\home\ccialek\STANDARDS\Workgroups\IPO Process\Approved
Process for PSG's for IPC-v2 B&W 3.vsd
Year Standard
1997
1998
1998
2000
Codes for MN Counties
State Agency Coordinate Interchange
Geographic Metadata
Positional Accuracy
2005
 IPC sunsets
 OET created and IPO incorporated into it
 Process to ratify standards interrupted
2007
 Standards Committee formed Geospatial Standards
Authorization Workgroup to try to influence reinstatement of
standards process (see 2008 work plan)
2008
 Met with OET Director of Strategic Planning:
Offered to include GI standards on OET web site without
ratification pending development of a new governance
model that is in progress
Year Standard
1994
2002
2006
2008
2009
2009
Codes for the Identification of States
Codes for Lake and Wetland Basins
Codes for Watersheds
River Reach/Water Course IDs
City,Township and Unorganized Territory Identifiers
U.S. National Grid
 Subject Matter Experts
 Info/Data Domain Team
 Architecture Review Board
 All CIO Team
 State CIO
Year
Standard
1997 Codes for MN Counties
1998 State Agency Coordinate Interchange
1998 Geographic Metadata
2000 Positional Accuracy
1994 Codes for the Identification of States
2002 Codes for Lake and Wetland Basins
2006 Codes for Watersheds
2008 River Reach/Water Course IDs
2009 City,Township and Unorganized Territory Identifiers
2009 U.S. National Grid
- Stormwater Conveyance
- Thoroughfare, Landmark, and Postal Address Data Standard
- MN Geocode Model
1. OET consider the four previously ratified
IRM standards and guidelines as state
approved, and that OET inform the All-CIO
Team of that decision.
2. OET address the issue of the second set of
six standards by sending them directly to
the ARB to consider ratification.
3. OET provide advice and guidance to the
Standards Committee and Data Domain
Team to help each prepare for the
introduction of newly proposed standards
expected in 2011.
4. MnGeo adopt a procedure that includes
the reporting of instances of noncompliance to the Standards Committee
for action.