Agencies and information resource communities must develop and manage government data consistent with the public information policies and requirements of the Minnesota Government Data Practices Act, to ensure public access to government data, and the protection of rights of subjects of government data. Identification of the classification of data and issues of statutory compliance shall begin during the early stages of strategic planning and data modeling. The effects of the data's classification and attention to compliance with statutory requirements shall continue through design, installation, and maintenance.
IRM Standard 7, Current version , July 1, 1994
A data model is critical to sharing information and ensuring that data support the information needs of the organization. High-level data models help an agency or information resource community manage and share its data effectively. Models collectively describe project data and how they are used to support business functions.
Minnesota Recordkeeping Metadata Standard
IRM Standard 20, Current Version, 1.2, April 2003
The purpose of the standard is to facilitate records management by government entities by providing a standard set of metadata elements that address access restrictions, data practices, records disposition and retention.
Web Metadata Standard
IRM Standard 21, Current Version, 1 (June 2002)
The purpose of this standard is to increase relevancy and ranking of search results, increase accuracy of the search engine's browseable topic categories and allow retention scheduling of web publications for recordkeeping or archival purposes. It does not cover implementation or technical issues.
Codes for the Identification of Cities, Townships and Unorganized Territories (CTUs) in Minnesota
(3-25-2009) This standard provides a set of codes that uniquely identify more than 2700 cities, townships and unorganized territories (CTUs) within the state of Minnesota. These codes originate from the U.S. Geographic Names Information System and are recognized as a formal federal standard. Read the document.
Codes for the Identification of Counties in Minnesota
IRM Standard 15, Version 1 (4-3-1997)
This standard provides a single, common coding scheme for counties in Minnesota. It is intended to be used primarily when data are being transferred between a state agency and some external customer. Its use will improve the shareability of data resources created by Minnesota state and local government by avoiding unnecessary duplication and incompatibilities in the collection, processing and dissemination of data. Read the document.
A Methodology for Measuring and Reporting Positional Accuracy in Spatial Data
IRM Standard 19, Version 1: (6-12-00) The purpose of this standard is to provide a single, uniform statistical methodology for estimating the positional accuracy of points on maps and in digital spatial data. Read the Full Document
CTU Identifier Codes
This standard provides a set of codes that uniquely identify more than 2700 cities, townships and unorganized territories (CTUs) within the state of Minnesota. (3-25-09) Read the Full Document
Codes for the Identification of Basins in Minnesota
This standard provides a common convention for identifying lakes and wetland basins in Minnesota. This standard has been developed to improve sharing and exchange of information about lake and wetland basins in Minnesota. The Minnesota Department of Natural Resources' Division of Waters has the authority and responsibility for naming and numbering basins in Minnesota. (6-12-02) Read the Full Document
Codes for the Identification of River Reaches and Watercourses in Minnesota
This standard describes two related concepts for identifying rivers, streams, and ditches in Minnesota. It brings together current state and federal river naming and identification practices into a common framework for data sharing and transfer. The standard comprises two concepts: 'reach' and 'watercourse.' (6-9-08) Read the Full Document
Codes for the Identification of Watersheds (Hydrologic Units) in Minnesota
This standard provides a common convention for identifying watersheds in Minnesota. This standard enables the transfer of data among agencies and external customers, provides consistency between state practices and federal identification and naming conventions for watersheds (referred to as hydrologic units), and promotes data integration across state lines and with national data sets.(6-21-06) Read the Full Document
Codes for the Identification of the States and the District of Columbia
The purpose of this standard is to provide a common coding scheme for states. It is intended to be used primarily when data are being transferred between a state agency and some external customer. Its use will improve the shareability of data resources created by Minnesota state and local government by avoiding unnecessary duplication and incompatibilities in the collection, processing and dissemination of data.(12-1-94) Read the Full Document
Coordinate Specifications for Spatial Data Exchange Between Minnesota State Agencies
IRM Standard 17, Version 1: (6-9-98) The purpose of this standard is to define a common framework for spatial data exchange. This benefits all consumers of state-produced data by eliminating the need to prepare customized procedures for processing coordinate information. Deploying the standard allows for the streamlining of exchange procedures between data producers and consumers, thereby reducing costs associated with data processing and handling. Read the Full Document
United States National Grid
This standard describes a method for presenting the United States National Grid (USNG) in cartographic products. (3-25-09) Read the Full Document
Data Administration: A Data Naming Primer
IRM Guideline 9, Version 1: (8-31-95)
The purposes of this guideline are to: 1) inform managers and decision-makers of the need for a good datanaming program, 2) explain the business benefits of a good data naming program, 3) show how data naming fits within a larger data administration function, and 4) identify action steps that enable agencies to begin realizing the benefits of a data naming program. Read the full document.
Data Administration: A Data Naming Practitioner's Guide
IRM Guideline 10, Version 1: (8-31-95)
This document provides assistance to technical data practitioners who need to establish data naming policies, standards and methods, or create standard data names; establishes "best practices" for data naming; and provides "starter kit" standards and examples of standard data names. Read the full document.
Data Administration: Application Naming
This document provides help in naming aplications. The goals for naming applications include making names memorable, describing business purpose, and retaining names despite implementation changes. Read the full document.
Minnesota Geographic Metadata
The purpose of this guideline is to provide that common approach for documenting all types of geographic data. (10-7-98) Read the Full Document