Home
                          Who We Are
                              Organization
                                
                				History
								Policies & Planning
    							
								FGDC Secretariat
                          What We Do
                              ADVANCEMENT OF THE NSDI
                                      Geospatial Data Act

                                      Collaboration & Partnerships

									  Develop Geospatial Shared Services
										Geospatial Platform
											Cloud Computing
											Geospatial InteroperabilityManage Federal Geospatial Resources
										A-16 NGDA Portfolio Management
											Geospatial Platform Marketplace
									  Standards Development
									  Geospatial Metadata

                          Initiatives
                              Current
                                        NSDI Strategic Plan 2021-2024
                    						Geospatial Platform Shared Services
            								NGDA Management Plan
            								Open Water Data Initiative
                                            National Address Database
                                            GeoPathways
                                            Disaster Risk ResilienceEmerging Topics
			                            Geolocation Privacy
											Crowdsourcing								
                                            Education & Workforce Development
                                            New Geodetic DatumsPast Activities
			                            Cooperative Agreements Program
                                            
											Fifty States Initiative
                                            Geospatial Line of Business
											SmartBUY
                          
                          Organization
                            Overview
								Steering Committee
								Executive Committee
								National Geospatial Advisory Committee
								Coordination Group
								Working Groups
								Subcommittees
								FGDC Secretariat
								Collaborating Partners
								Membership Directory
                          Resources
                            Key Publications
    							Download Geospatial Standards
								Policies & Planning
                                Lexicon of Geospatial Terminology
								
								
                                FGDC Geospatial Services Status Checker            
								News
                                
								Calendar
								Media Resources FGDC Geospatial Standards Home
    Standards
    FGDC Geospatial Standards The standards in the table below, were endorsed by the FGDC prior to the release of the Geospatial Data Act.
All FGDC Endorsed Standards
Under Development
Discontinued Standards**Standard****Where to find****Publisher / Creator****PublicationDate****Constraints**FGDCEndorse-mentDate**Fees****Comment****Keywords****United States Thoroughfare, Landmark, and Postal Address Data Standard FGDC-STD-016-2011 Part 1 Introduction**
Link
FGDC
2011
unrestricted
2011
No

Address**United States Thoroughfare, Landmark, and Postal Address Data Standard FGDC-STD-016-2011 Part 2: Address Data Content**
Link
FGDC
2011
unrestricted
2011
No
Part 2 defines address elements, their attributes, and address reference system elements.
Address, data content**United States Thoroughfare, Landmark, and Postal Address Data Standard FGDC-STD-016-2011 Part 3: Address Data Classification**
Link
FGDC
2011
unrestricted
2011
No
Part 3 classifies addresses according to their syntax, that is, their address elements and the order in which those elements are arranged. Syntax determines the record structure needed to hold and exchange an address, and often it is all that is known about the addresses in a given file. Classifying addresses by syntax rather than semantics (i.e. meaning) allows users to focus on record structures and avoid making any assumptions about what Address Feature Type the address might identify.
Address, data classification**United States Thoroughfare, Landmark, and Postal Address Data Standard FGDC-STD-016-2011 Part 4: Address Data Quality**
Link
FGDC
2011
unrestricted
2011
No
Part 4 helps users assess the quality of their address data. It provides ways to measure the quality of each element, attribute, and classification. Some measures compare values to Address Reference System (ARS) specifications or domains of values, while others check internal consistency. Measures describe ways to discover anomalies, in isolation, in relationships between data, and in relationship to the ARS, and how to report the quality of the data.
Address, data quality**United States Thoroughfare, Landmark, and Postal Address Data Standard FGDC-STD-016-2011 Part 5: Address Data Exchange**
Link
FGDC
2011
unrestricted
2011
No
Part 5 provides: (1) a template for the XML documents and metadata for data exchange; (2) information on preparing address data to be packaged; and (3) information on unpackaging address data. Part 5 simplifies implementation of data exchange by providing a flexible data structure for exchanging street address data. The Address Data Standard is designed to be flexible enough to fit within current data sharing methods. The Address Data Standard supports two basic forms of sharing data: (1) monolithic, in which all records are in the exchange package and (2) transactional, in which the exchange package records include commands to add or remove a record from the local copy of records.
Address, data exchange**United States Thoroughfare, Landmark, and Postal Address Data Standard FGDC-STD-016-2011 Part 6: Reference Standards and Specifications**
Link
FGDC
2011
unrestricted
2011
No

Address**United States Thoroughfare, Landmark, and Postal Address Data Standard FGDC-STD-016-2011 Part 7 Appendices**
Link
FGDC
2011
unrestricted
2011
No
Part 7 consists of a normative Appendix A on XSD Schemas and informative appendices for Examples of Exchange Packages (B), Table of Element Relationships (c), Element - Measure Index (D), Attribute - Measure Index (E), Classification - Measure Index (F), Quality Measures by Data Quality Report (G), Relationship of Addresses to Transportation Features and Linear Reference Locations (H), and Compatibility of the Address Standard with the FGDC Geographic Information Framework Data Content Standard (I).
Address**OpenGIS® Sensor Planning Service Implementation Specification, version 1.0.0 [OGC® 07-014r3]**
Link
OGC
2007
OGC Policies
2011
No
Sensor Planning Service (SPS) defines an interface to task any form of sensor or model. It enables a client to determine collection feasibility for collection requests for one or more mobile sensors/platforms, or a client may submit collection requests directly to these sensors/platforms. Using SPS, sensors can be reprogrammed or calibrated, sensor missions can be started or changed, and simulation models can executed and controlled. The feasibility of a tasking request can be checked and alternatives may be provided. SPS implementations cover a wide range of application scenarios. SPS is used to control assets such as simple web cams and satellite missions. This standard should be used for the development of any system that requires the ability to task any form of sensor or model.
Sensor Web Enablement, Sensor Planning Service**Unified Model Language (UML) 2.2**
Link
OMG
2009
OMG® Governance, Policies, Procedures
2011
No
UML is a standardized general-purpose modeling language for software engineering. It includes graphic notation techniques to create visual models of software-intensive systems.
Link directs user to the Infrastructure and Superstructure specifications (both in PDF)
UML**Geopolitical Entities, Names, and Codes (GENC) Standard (GENC) version 2**
Link
NCGIS
2014
unrestricted
2014
No
The GENC Standard specifies a profile of ISO 3166, Codes for the representation of names of countries and their subdivisions. This profile addresses U.S. Government requirements for recognition of the national sovereignty of a country; identification and recognition of geopolitical entities not included in ISO 3166; and names of countries and country subdivisions that the U.S. Board on Geographic Names (BGN) has approved. The US Government cannot use ISO 3166 directly. US Public Law 80-242 (1947) requires the US Government to use geographic names that the BGN has approved. ISO 3166 contains some country and subdivision names that vary from BGN-approved names. The geopolitical entities included in ISO 3166 are those that United Nations (UN) recognizes. GENC is the US Government implementation of ISO 3166-1 that conforms to BGN and US Government recognition policy. The National Geospatial-Intelligence Agency has developed a registry to maintain the data content of the GENC.
Governmental Units, Registers**INCITS/ISO 19157:2013[2014] Geographic information -- Data quality**
Link
ANSI
2014
End User License Agreement
2016-12
Yes
ISO 19157:2013 establishes principles for describing the quality of geographic data. It defines components for describing data quality; specifies components and content structure of a register for data quality measures; describes general procedures for evaluating the quality of geographic data; and establishes principles for reporting data quality. ISO 19157:2013 also defines measures for evaluating and reporting data quality. It applies to data producers who provide quality information to describe and assess how well a data set conforms to its product specification and data users who determine whether specific geographic data are of sufficient quality for their particular application. ISO 19157:2013 does not attempt to define minimum acceptable levels of quality for geographic data.
The link directs users to the PDF file.
Data quality**OGC GeoPackage 1.0 [12-128r10]**
Link
OGC
2015-02
OGC Policies
2015
No
OGC GeoPackage 1.0 defines GeoPackages for exchange and GeoPackage SQLite Extensions for “direct use” of vector geospatial features and/or tile matrix sets of earth images and raster maps at various scales. Direct use is the ability to access and update data without intermediate format translations in an environment (e.g. through an API). GeoPackage guarantees data model and data set integrity and identical access and update results in response to identical requests from different client applications. GeoPackages are interoperable across all enterprise and personal computing environments and are particularly useful on mobile devices like cell phones and tablets.
GeoPackage**Content Standard for Digital Geospatial Metadata (version 2.0), FGDC-STD-001-1998**
Link
FGDC
1998
unrestricted
1998
No
CSDGM provides a common set of terminology and definitions for the documentation of digital geospatial data. It establishes the names of data elements and compound elements, the definitions of these compound elements and data elements, and information about the values to be provided for the data elements.
Metadata, data content**Content Standard for Digital Geospatial Metadata: Part 1, Biological Data Profile, FGDC-STD-001.1-1999**
Link
FGDC
1999
unrestricted
1999
No
This standard is a profile of the FGDC Content Standard for Digital Geospatial Metadata (CSDGM) for documenting biological resources data and information. It supports increased access to and use of biological data among users. It helps broaden understanding and implementation of the CSDGM within the biological resources community. It specifies metadata content for the full range of biological resources data and information, including biological data that are explicitly geospatial in nature and data that are not explicitly geospatial (such as data resulting from laboratory-based research, research reports, field notes and specimen collections).
Metadata, Biodiversity and Ecosystems**Content Standard for Digital Geospatial Metadata: Part 2, Metadata Profile for Shoreline Data, FGDC-STD-001.2-2001**
Link
FGDC
2001
unrestricted
2001
No
The Shoreline Metadata Profile is a profile of the CSDGM that addresses shoreline data and data that intersects with the shoreline.
Metadata, Water - Oceans and Coasts**Cadastral Data Content Standard, FGDC-STD-003**
Link
FGDC
2008
unrestricted
2008
No
The Cadastral Data Content Standard provides semantic definitions of objects related to land surveying, land records, and land ownership information to facilitate data sharing. It provides common definitions for cadastral information found in public records, suggested attribute values, and guidance and direction for land records and land surveying professionals. It standardizes definition of entities and objects, including survey measurements and transactions related to interests in land, general property descriptions, and boundary and corner evidence data. It supports automation and integration of publicly available land records information. It is intended for use by all levels of government and the private sector. It does not contain spatial and topological linkages and spatial features required to build and maintain a GIS. It does not guide procedures or processes for land surveying. The intended geographic scope of the standard is all 50 states of the United States, including onshore and marine cadastral information.
Cadastre, data content**Classification of Wetlands and Deepwater Habitats in the United States, FGDC-STD-004-2013**
Link
FGDC
2013
unrestricted
2013
No
The FGDC Wetlands Classification Standard (WCS) provides minimum requirements and guidelines for classification of wetlands and deepwater habitats. It is designed for use over all U.S. States and Territories. It is mandatory for all Federal or federally funded wetlands inventory mapping. It is used to map nontidal deepwater habitats, except the Great Lakes, and all coastal and inland wetlands except for permanently flooded tidal freshwater wetlands, which are covered by the Coastal and Marine Ecological Classification Standard (CMECS; FGDC-STD-018-2012). It does not support legal, regulatory, or jurisdictional analyses of wetlands mapping products. It does not define the limits of proprietary jurisdiction of any Federal, Tribal, state, or local government or establish the geographical scope of the regulatory programs of government agencies.
Water - Inland, Water - Oceans and Coasts, data classification**National Vegetation Classification Standard (Version 2), FGDC-STD-005-2008**
Link
FGDC
2008
unrestricted
2008
No
The National Vegetation Classification Standard (NVCS) establishes procedures for classifying existing vegetation for the U.S. and its Trust Territories and minimum metadata requirements to ensure consistent reporting. It classifies vegetation by inherent attributes and characteristics of the vegetation structure, growth form, species and cover, emphasizing both physiognomic and floristic criteria. Widespread use of the NVCS facilitates integration of existing vegetation data to address national and regional information needs. The NVCS does not preclude alternative classification approaches and systems: rather, it facilitates linkages to other classifications.
Biodiversity and Ecosystems, data classification**Soil Geographic Data Standard, FGDC-STD-006**
Link
FGDC
1997
unrestricted
1997
No
The Soil Geographic Data Standard standardizes names, definitions, ranges of values, and other characteristics of soil survey map attribute data developed by the National Cooperative Soil Survey (NCSS). Soil attribute data include physical and chemical properties, interpretative information, arrangement of soils into soil map units, and information about the soil map units themselves. The standard facilitates transfer and use of soil data and allows data users to receive data in a common format. It applies to tabular data associated with NCSS soil survey maps at scales of about 1:12,000 to 1:30,000. Data from individual points are classified using accepted procedures and grouped or aggregated into soil types. Soil types then become components of map units. The standard does not deal with description of landforms and landscapes or vegetation related to soil map units. It contains a list of data elements used to store physical, chemical, and interpretive data; an Entity Relationship Model; a list of table names with data elements contained in each; and a data dictionary.
Soils**Geospatial Positioning Accuracy Standards, Part 1: Reporting Methodology, FGDC-STD-007.1-1998**
Link
FGDC
1998
unrestricted
1998
No

data quality, positional accuracy**Geospatial Positioning Accuracy Standards, Part 2: Standards for Geodetic Networks, FGDC-STD-007.2-1998**
Link
FGDC
1998
unrestricted
1998
No
Part 2 applies to accuracy reporting for geodetic networks. Geodetic control surveys establish a basic control network (framework) from which supplemental surveying and mapping work. They are performed to accuracy that is far more rigorous and quality assurance standards than those for control surveys for general engineering, construction, topographic mapping, or cadastral purposes.
data quality, positional accuracy, geodetic control**Geospatial Positioning Accuracy Standards, Part 3: National Standard for Spatial Data Accuracy, FGDC-STD-007.3-1998**
Link
FGDC
1998
unrestricted
1998
No
The objective of the National Standard for Spatial Data Accuracy (NSSDA) is to facilitate sharing and interoperability of geospatial data through a statistical and testing methodology for positional accuracy of maps and geospatial data derived from sources such as aerial photographs, satellite imagery, or maps. The NSSDA omits accuracy metrics or threshold values that data must achieve; however, agencies may establish "pass-fail" criteria for their product standards and applications and contracting purposes. Ultimately, users must identify acceptable accuracies for their applications. While this standard evaluates positional accuracy at points, it applies to geospatial data sets that contain point, vector, or raster spatial objects.
data quality, positional accuracy**Geospatial Positioning Accuracy Standards, Part 4: Architecture, Engineering, Construction, and Facilities Management**
Link
FGDC
2002
unrestricted
2002
No
PART 4 provides accuracy standards for engineering drawings, maps, and surveys that support planning, design, construction, operation, maintenance, and management of facilities, installations, structures, transportation systems, and related projects. It supports geospatial mapping data used in various engineering documents, such as architectural, engineering, and construction (A/E/C) drawings, site plans, regional master planning maps, and related Geographical Information System (GIS), Computer-Aided Drafting and Design (CADD), and Automated Mapping/Facility Management (AM/FM) products. It defines accuracy criteria, accuracy testing methodology, and accuracy reporting criteria for object features depicted on A/E/C spatial data products and related control surveys. By using Part 4, end users of A/E/C products (e.g., planners, designers, constructors) can specify surveying and mapping accuracy requirements for their projects or specific CADD/GIS layers, levels, or entities. Data producers (e.g., surveyors, mappers, photogrammetrists) can determine instrumentation, procedures, and quality control processes required to obtain and verify the defined accuracies.
data quality, positional accuracy**Geospatial Positioning Accuracy Standards, Part 5: Standards for Nautical Charting Hydrographic Surveys, FGDC-STD-007.5-2005**
Link
FGDC
2005
unrestricted
2005
No
Part 5 provides minimum standards for horizontal and vertical accuracy of features associated with hydrographic surveys that support nautical charting. Features include, but are not limited to, water depths, objects on the seafloor, navigational aids, and shoreline. Hydrographic surveys determine the configuration of the bottom of water bodies and identify and locate features that may affect navigation. Nautical charts are compilations of data from numerous sources, principally hydrographic surveys, designed specifically to meet the requirements of marine navigation. The scope of these standards includes the coastal waters of the U.S. and its territories.
data quality, positional accuracy, Water - Oceans and Coasts**Content Standard for Digital Orthoimagery, FGDC-STD-008-1999**
Link
FGDC
1999
unrestricted
1999
No
This standard describes processing, accuracy, reporting, and applications considerations for digital orthoimagery. It sets a common baseline to ensure enhanced data sharing and minimize redundant data production.
Imagery, data content**Content Standard for Remote Sensing Swath Data, FGDC-STD-009-1999**
Link
FGDC
1999
unrestricted
1999
No
This data content standard defines a swath, which associates certain kinds of remote sensing data with their geolocation. It defines the minimum content for remote sensing swath data; provides a solid basis for developing interoperable data formats for remote sensing swath data; provides a common conceptual framework for encoding swath and swath-like data; and encourages use of swath and swath-like data through implementation of transfer standards within the conceptual framework. It does not specify encoding. It specifies only information that varies with time or from pixel to pixel. Information that is constant for all data points, such as the axes about which platform roll, pitch, and yaw are measured or the orientation of individual instruments relative to the platform, are specified elsewhere.
Imagery, data content, remote sensing**Utilities Data Content Standard, FGDC-STD-010-2000**
Link
FGDC
2000
unrestricted
2000
No
The Utilities Geospatial Data Content Standard specifies names, definitions, and domains for utility system components that can be geospatially depicted as feature types and their non-spatial attributes. It supports large-scale, intra-city applications such as engineering and life cycle maintenance of utility systems. It describes eleven feature classes: compressed air, electrical distribution, electrical monitoring/control, fuel distribution, heating/cooling systems, industrial waste, natural gas distribution, saltwater, storm drainage collection, wastewater collection, and water distribution. It does not contain all features necessary to describe or model communications, alarm systems, or long distance utilities networks that stretch between cities.
Utilities, data content**Standard for a U.S. National Grid, FGDC-STD-011-2001**
Link
FGDC
2001
unrestricted
2001
No
This standard defines a U.S. National Grid (USNG) for mapping applications at scales of approximately 1:1,000,000 and larger. It defines how to present Universal Transverse Mercator (UTM) coordinates at various levels of precision. It specifies use of those coordinates with the grid system defined by the Military Grid Reference System (MGRS). It addresses specific presentation issues such as grid spacing, UTM coordinate representation, the MGRS grid, and the specific grid presentation requirements.
Geodetic Control**Content Standard for Digital Geospatial Metadata: Extensions for Remote Sensing Metadata, FGDC-STD-012-2002**
Link
FGDC
2002
unrestricted
2002
No
This standard provides extensions to the FGDC Content Standard for Digital Geospatial Metadata to describe geospatial data obtained from remote sensing. Extensions include metadata describing the sensor, the platform, the method and process of deriving geospatial information from raw telemetry, and information needed to determine the geographical location of the remotely sensed data.
Metadata, Imagery, data content, remote sensing**Digital Cartographic Standard for Geologic Map Symbolization, FGDC-STD-13-2006**
Link
FGDC
2006
unrestricted
2006
No
The standard provides descriptions, examples, cartographic specifications, and notes on usage for symbols on a digital geologic map or related product (for example, cross-sections). It includes a revised CMYK color chart, a chart of commonly used geologic map patterns, a geologic age symbol font, and a variety of bar scales, mean declination arrows, and quadrangle location maps. It applies to geologic map information in both offset-print and plot-on-demand formats. It also is suitable for use in electronic publications (for example, PDF) and display by computer monitors.
The link directs the user to downloads of PDF documents.
Geology, Portrayal**Geographic information Framework Data Standard Part 0, Base document, FGDC-STD-014.0-2008**
Link
FGDC
2008
unrestricted
2008
No
Part 0 provides: a high-level view of the seven framework data themes; an overall integrating Unified Modeling Language (UML) model that is supplemented by detail in the part for each data theme; and terminology and other information common to two or more themes
Framework**Geographic information Framework Data Standard Part 1, Cadastral, FGDC-STD-014.1-2008**
Link
FGDC
2008
unrestricted
2008
No
The purpose of Part 1: Cadastral is to facilitate the exchange of cadastral (real property) data. Part 1 provides information necessary to identify the existence and source of parcel-level cadastral information. All elements in Part 1 are included in the Cadastral Data Content Standard.
Framework, Cadastre**Geographic information Framework Data Standard Part 2, Digital Orthoimagery, FGDC-STD-014.2-2015**
Link
FGDC
2008
unrestricted
2008
No
Part 2 is intended to facilitate interchange and use of digital orthoimagery data. It specifies data content and logical structure for description and interchange of digital orthoimagery. It provides guidelines for acquisition and processing of imagery and specifies documentation of steps. It sets a common baseline to ensure the widest utility of digital orthoimagery. It provides a base on which to collect, register, and integrate imagery data. It stresses complete and accurate reporting of information relating to quality control and standards used in testing orthoimagery data.
Framework, Imagery**Geographic information Framework Data Standard Part 3, Elevation, FGDC-STD-014.3-2008**
Link
FGDC
2008
unrestricted
2008
No
Part 3 defines data model entities and attributes for exchange of digital elevation data. It identifies geospatial data model elements required for digital elevation data. It includes an application schema expressed in Unified Modeling Language (UML). It covers common elevation data models (point, grid, contour, triangulated irregular network, and profile). It supports both topographic elevation data and bathymetric elevation data. Collecting and sharing NSDI digital elevation data consistent with Part 3 will assure common understanding of the data.
Framework, Elevation**Geographic information Framework Data Standard Part 4, Geodetic Control, FGDC-STD-014.4-2008**
Link
FGDC
2008
unrestricted
2008
No
Geodetic control surveys establish the positional framework for supplemental surveying and mapping. Part 4 provides a common methodology for creating datasets of horizontal and vertical coordinate values for geodetic control points. It provides a single data structure for relating coordinate values obtained by one geodetic survey method with coordinate values obtained by another geodetic survey method.
Framework, Geodetic Control**Geographic information Framework Data Standard Part 5, Governmental Unit and Other Geographic Area boundaries, FGDC-STD-014.5-2008**
Link
FGDC
2008
unrestricted
2008
No
Part 5 establishes content and organization requirements for collection and interchange of governmental units and other geographic area boundary data and facilitates maintenance and use of that data. It identifies and defines terminology, encoding schema, and data components required to describe a geographic area and its boundary. It does not specify a particular structure for interchange of boundary data. Data producers and users may structure geographic area boundary data in any format for their internal use.
Framework, Governmental Units**Geographic information Framework Data Standard Part 6, Hydrography, FGDC-STD-014.6-2008**
Link
FGDC
2008
unrestricted
2008
No
Part 6 supports exchange of data about surface water (hydrography) features and hydrologic networks. It seeks to decrease costs, simplify data exchange, and discourage duplicative data collection. It supports general requirements of natural resource managers, environmental and water resources agencies, and hydrography applications designers and developers. It can support some, but not all, business and decision-making needs. It establishes content requirements for data collection and interchange and facilitates maintenance and use of that data. It establishes a baseline for semantic content for data sharing and applications development. It describes geographic locations, interconnectedness, and characteristics of surface water features. It defines terminology, encoding schema, data components, and metadata for describing hydrographic features. It provides common definitions and syntax for development, use, and exchange of hydrography data. It defines components of networked and non-networked surface water features. It sets a common baseline of data content for exchange and accommodates exchange of different representations. It does not specify a particular structure for storage of hydrography data, nor capture criteria.
Framework, Water - Inland**Geographic Information Framework Data Content Standard Geographic information Framework Data Standard Part 7: Transportation Base FGDC-STD-014.7-2008**
Link
FGDC
2008
unrestricted
2008
No
Part 7: Transportation Base supports exchange of transportation data. It establishes a common baseline for semantic content of transportation databases. It seeks to decrease costs, simplify data exchange, and discourage duplicative data collection. Benefits of adopting Part 7 include long-term improvement of geospatial transportation data; improved integration of safety, emergency response, and enforcement data; and streamlined maintenance. Part 7 defines the data model for describing components of transportation systems for air, rail, road, transit, and inland waterways and integrates the five modes. The transportation system described in Part 7 comprises transportation features, which can have geographic locations and characteristics. These transportation features can interconnect in various ways and across modes. Content in Part 7 will support development of specialized networks for routing applications. Part 7 can be implemented using a variety of software packages and accommodate data encoded without geometry and data encoded in a variety of geographic information systems. It accommodates assets associated with the transportation system used for navigation, safety, and measurement.
Framework, Transportation**Geographic information Framework Data Standard Part 7b, Transportation - Rail, FGDC-STD-014.7b-2008**
Link
FGDC
2008
unrestricted
2008
No
Part 7b supports exchange of rail transportation data. It establishes a common baseline for semantic content of rail transportation databases. The rail system comprises rail features, which can have geographic locations and characteristics. Rail features can interconnect in various ways to represent rail networks for routing applications. Part 7b focuses on a generalized view of the rail network that enables the broadest variety of operational uses. It will be suitable for some, but not all, engineering applications. It can be implemented using various software packages and accommodate data encoded with or without geometry. It depicts the rail system at all levels of service and all functional classes that a data-providing agency may define. It accommodates assets associated with the rail system used for navigation, safety, and measurement. It is the intent of Part 7b to allow the widest utility of railway transportation data. It seeks to decrease costs, simplify data exchange, and discourage duplicative data collection. Benefits of adopting Part 7b include long-term improvement of geospatial rail transportation data; improved integration of safety, emergency response, and enforcement data; and streamlined maintenance. Because of the international scope of the railway network, Part 7b addresses differences between Canadian and U.S. definitions of railway, related concepts, and terminology in order to harmonize the models.
Framework, Transportation, Rail**Geographic information Framework Data Standard Part 7c, Transportation - Road, FGDC-STD-014.7c-2008**
Link
FGDC
2008
unrestricted
2008
No
Part 7c supports exchange of road transportation data; establishes a common baseline for semantic content; and defines components of a model for describing roads. The road model comprises features that can interconnect to represent road networks for path finding/routing applications. Part 7c can be implemented in various software packages. It can accommodate data with or without geometry. It accommodates data associated with the complete road system at all levels of service. It seeks to decrease costs, simplify exchange of road transportation data, and discourage duplicative data collection. It accommodates assets for navigation, safety, and measurement associated with roads. It uses linear reference systems (LRS) to support exchange of data about sign locations, pavement conditions, placement of transportation statistics such as traffic counts or accident data along the roads, the number of lanes, speed limits, etc. Benefits of adopting Part 7c include long-term improvement of the geospatial road transportation data; improved integration of safety, emergency response, and enforcement data; and streamlined maintenance.
Framework, Transportation, Road, linear reference systems**Geographic information Framework Data Standard Part 7d, Transportation - Transit, FGDC-STD-014.7d-2008**
Link
FGDC
2008
unrestricted
2008
No
Part 7d supports exchange of transit data; establishes a common baseline for semantic content; defines components of a model for describing transit systems; develops a set of common definitions for real world transit features; and includes a data dictionary based on the conceptual schema. To conform to Part 7d, the user shall satisfy the requirements of the data dictionary. Part 7d can be implemented using a variety of software packages. It is designed to accommodate data with or without geometry and depict the complete transit system at all levels of service and all functional classes. It sets a common baseline to foster the widest possible set of applications. It seeks to decrease costs, simplify data exchange, and discourage duplicative data collection. Emphasis is on data exchange on a regional level for itinerary planning, infrastructure inventories, and re-routing applications. Benefits of adopting Part 7d include long-term improvement of transit data; improved integration of safety, emergency response, and enforcement data; and streamlined maintenance procedures.
Framework, Transportation, Transit**Geographic information Framework Data Standard Part 7e, Transportation - Inland Waterways, FGDC-STD-014.7e-2008**
Link
FGDC
2008
unrestricted
2008
No
Part 7e supports exchange of navigable river (inland waterway) transportation data. It establishes a common baseline for semantic content of inland waterway data. It provides definitions and syntax for use and exchange of geospatial data content, as compiled for Inland Electronic Navigation Charts (IENC). It describes data content derived from the IENC. It seeks to decrease costs, simplify exchange of inland waterway data, and discourage duplicative data collection. It enables construction of a detailed multi-modal description of a transportation system. Benefits of adopting Part 7e include long-term improvement of geospatial inland waterway data; improved integration of safety, emergency response, and enforcement data; and streamlined maintenance procedures.
Framework, Transportation, Water - Inland**Wetlands Mapping Standard, FGDC-STD-015-2009**
Link
FGDC
2008
unrestricted
2008
No
The Wetlands Mapping Standard supports accurate mapping and classification of wetlands and provides mechanisms for revisions and update. If Federal funding is involved, then use of the proposed Standard is required; for all other efforts, use of the standard is strongly encouraged. It directs current and future digital mapping of wetlands, especially if mapping data is uploaded into the National Wetlands Inventory (NWI).
Water - Inland, Water - Oceans and Coasts, Wetlands**Federal Trails Data Standards, FGDC-STD-017-2011**
Link
FGDC
2011
unrestricted
2011
No
Federal Trails Data Standards include definition of a core set of trail data attributes, corresponding values, and definitions. These standards are applicable only to trails within the United States, including all U.S. territories and outlying possessions. Use of these standards will reduce duplicative efforts and production costs.
Transportation, Trails**Coastal and Marine Ecological Classification Standard (CMECS), FGDC-STD-018-2012**
Link
FGDC
2012
unrestricted
2012
No
CMECS is used to classify intertidal and subtidal coastal and marine habitats. It interfaces with the National Wetland Classification Standard and incorporates alliances and associations from the U.S. National Vegetation Classification Standard (Version 2.0), FGDC-STD-005-2008, as appropriate.
Water - Oceans and Coasts, data classification**GeoTIFF Revision 1.0**
Link
de facto
2000
GeoTIFF
2011
No
GeoTIFF defines Tagged Image File Format (TIFF) tags for describing geographic and cartographic information associated with TIFF imagery. Information might include projections, coordinate systems, ellipsoids, and datums.
Imagery, TIFF**Hierarchical Data Format V 5.0 (HDF 5)**
Link
de facto

HDF 5
2011
No
HDF5 is a data model, library, and file format for storing and managing data. It supports an unlimited variety of datatypes, and is designed for flexible and efficient I/O and high volume and complex data. It is portable and extensible, allowing applications to evolve in their use of HDF5. Its technology suite includes tools and applications for managing, manipulating, viewing, and analyzing data in the HDF5 format.**INCITS 31-2009, Information technology - Codes for the Identification of Counties and Equivalent Areas of the United States, Puerto Rico, and the Insular Areas**
Link
ANSI
2009
End User License Agreement
2011
Yes
This standard establishes a structure for the assignment of data codes to counties and county equivalents of the United States and its insular and associated areas, for the purpose of information interchange among data processing systems.
The codes are freely available at here
Governmental Units**INCITS 38-2009 Information technology - Codes for the Identification of the States and Equivalent Areas within the United States, Puerto Rico, and the Insular Areas.**
Link
ANSI
2009
End User License Agreement
2011
Yes
This standard establishes a structure for the assignment of data codes to states and state equivalents of the United States and its insular areas, for the purpose of information interchange among data processing systems.
The codes are freely available at here
Governmental Units**INCITS 446-2008, Information technology - Identifying Attributes for Named Physical and Cultural Geographic Features (Except Roads and Highways) of the United States, Its Territories, Outlying Areas, and Freely Associated Areas, and the Waters of the Same to the Limit of the Twelve-Mile Statutory Zone**
Link
ANSI
2008
End User License Agreement
2011
Yes
This standard applies to selected named physical and cultural geographic features, geographic areas, and locational entities that have achieved some landmark status, for any purpose that would lead to representation of the feature in printed or electronic maps and/or geographic information.
It applies to populated places, primary county divisions, American Indian and Alaska Native areas, counties and equivalent legal and statistical entities. It covers the 50 States; the District of Columbia; Puerto Rico; outlying areas (American Samoa, Guam, the Commonwealth of the Northern Mariana Islands, U.S. Virgin Islands of the United States, and U.S. Minor Outlying Islands); freely associated areas (the Federated States of Micronesia, the Marshall Islands and the Republic of Palau); and waters to the limit of the twelve mile statutory zone.
Names include, but are not limited to, names specified by the U.S. Board on Geographic Names and U.S. Bureau of the Census, in coordination with government agencies responsible for land and real property management.
Real Property**INCITS 453-2009[R2014], Information Technology - North American Profile of ISO 19115:2003 - Geographic Information - Metadata (NAP - Metadata)**
Link
ANSI
2009
End User License Agreement
2011
Yes
This standard identifies geospatial metadata for North American organizations to use to describe their geospatial data. It is based on ISO 19115:2003 and ISO 19106:2004, Geographic information - Profiles. It also includes service metadata from ISO 19119:2005, Geographic information - Services, and implementation perspectives from ISO/TS 19139:2007 Geographic information - Metadata - XML schema implementation. Extension of code lists supports geographic information discovery. Annex A provides adjustments made to the ISO 19115:2003 and ISO 19119:2005 UML models.
While the FGDC retains the NAP for information and guidance, it is mandated for use in Canada.
Metadata**INCITS 454 - 2009, Information technology - Codes for the Identification of Metropolitan and Micropolitan Statistical Areas and Related Statistical Areas of the United States and Puerto Rico**
Link
ANSI
2009
End User License Agreement
2011
Yes
This standard establishes a structure for the assignment of data codes to uniquely identify metropolitan and micropolitan statistical areas and related statistical areas (for example, metropolitan divisions, combined statistical areas, New England city and town areas (NECTAs), NECTA divisions, and combined NECTAs) of the United States and Puerto Rico, for the purpose of information interchange among data processing systems.
The codes may be downloaded as .xls files here
Governmental Units**INCITS 455-2009[R2014] Information Technology - Codes for the Identification of Congressional Districts and Equivalent Areas of the United States, Puerto Rico, and the Insular Areas**
Link
ANSI
2009
End User License Agreement
2011
Yes
This standard establishes a structure for the assignment of data codes to congressional districts of the United States and its insular and associated areas, for the purpose of information interchange among data processing systems
Codes for the 113rd Congress are freely available here
Governmental Units**INCITS/ISO 19107:2003[R2013], Geographic Information - Spatial schema**
Link
ISO
2009
End User License Agreement
2011
Yes
INCITS/ISO 19107:2003[R2013] specifies conceptual schemas for describing spatial characteristics of geographic features and spatial operations consistent with these schemas. It defines spatial operations for access, query, management, processing, and exchange of geographic information for spatial objects of up to three topological dimensions embedded in coordinate spaces of up to three axes.
Features, conceptual schema**INCITS/ISO 19108:2002[R2013], Geographic information – Temporal schema**
Link
ISO
2002
End User License Agreement
2011
Yes
INCITS/ISO 19108:2002[R2013] defines concepts for describing temporal characteristics of geographic information. Temporal characteristics include feature attributes, feature operations, feature associations, and metadata elements that take a value in the temporal domain. The standard also specifies a model for describing temporal reference systems such as calendars and temporal coordinate systems.
Time, conceptual schema**INCITS/ISO 19108:2002/COR 1:2006 [R2015]  Geographic information - Temporal schema Technical Corrigendum 1**
Link
ISO
2006
End User License Agreement
2011
Yes

Time, conceptual schema**INCITS/ISO 19110:2005 [R2015] Geographic information - Methodology for feature cataloguing**
Link
ISO
2002
End User License Agreement
2011
Yes
ISO 19110:2005 defines how to catalog feature types and specifies how to organize classification of feature types into a feature catalogue. Its principles can apply to cataloguing other forms of geographic data. It does not apply to collection and representation of feature instances. It excludes schemas specified in ISO 19107, ISO 19108, and ISO 19117. It may be used to define the “universe of discourse” that is modelled in a particular application or standardize general aspects of real world features that are modelled in more than one application.
Features, feature catalog, feature type**INCITS/ISO 19111:2007[R2012] Geographic information - Spatial referencing by coordinates**
Link
ISO
2002
End User License Agreement
2011
Yes
INCITS/ISO 19111:2007 defines the conceptual schema for the description of spatial referencing by coordinates, optionally extended to spatio-temporal referencing. It defines the minimum data required to define 1-, 2- and 3-D spatial coordinate reference systems, with an extension for spatial-temporal reference systems. It allows additional descriptive information. It also describes the information required to change coordinates from one coordinate reference system to another.
conceptual schema, spatial referencing systems**INCITS/ISO 19111-2:2009 [R2015] Geographic information - Spatial referencing by coordinates - Part 2: Extension for parametric values**
Link
ISO
2009
End User License Agreement
2011
Yes
This standard defines the conceptual schema for the description of spatial referencing using parametric values or functions. It applies the schema of ISO 19111 to combine a position referenced by coordinates with a parametric value to form a spatio‐parametric coordinate reference system (CRS).
Intended users of ISO 19111-2:2009 are producers and users of environmental information. ISO 19111-2:2009 does not address parameters that are non-spatial attributes of spatial locations or features.
Conceptual schema, coordinate reference system**INCITS/ISO 19112:2003[R2014] Geographic information - Spatial referencing by geographic identifiers**
Link
ISO
2003
End User License Agreement
2011
Yes
INCITS/ISO 19111-2:2009 [R2015] defines the conceptual schema for spatial references based on geographic identifiers. It establishes a general model for spatial referencing using geographic identifiers and defines essential components of a gazetteer. A mechanism for recording complementary coordinate references is included. This standard enables producers of data to define spatial reference systems using geographic identifiers and assists users in understanding the spatial references used in datasets.
Conceptual schema, geographic identifier, gazetteer**INCITS/ISO 19115:2003 [R2008] ISO 19115:2003 w/ ISO 19115 Cor. 1:2006 Geographic information - Metadata + Corrigendum 1**

ISO
2003
End User License Agreement
2011
Yes
ISO 19115:2003 defines the conceptual schema for describing geographic information and services. It provides information about identification, extent, the quality, spatial and temporal schema, spatial reference, and distribution of digital geographic data.
Metadata, data content, conceptual schema**INCITS/ISO 19115-1:2014[2014] Geographic information -- Metadata -- Part 1: Fundamentals**
Link
ISO
2014
End User License Agreement
2016
Yes
INCITS/ISO 19115-1:2014 Geographic information -- Metadata -- Part 1: Fundamentals is the foundational geospatial metadata standard for providing information about identification, extent, quality, spatial and temporal aspects, content, spatial reference, portrayal, distribution, and other properties of digital geographic data and services. Significant changes incorporated in INCITS/ISO 19115-1:2014 include addition of metadata for services, removal of data elements for data quality (now placed in INCITS/ISO 19157:2013[2014]), and inclusion of feature catalogs.
Metadata, data content, conceptual schema**INCITS/ISO 19115-2:2009[R2014] Geographic information - Metadata - Part 2: Extensions for imagery and gridded data**
Link
ISO
2009
End User License Agreement
2011
Yes
ISO 19115-2:2009 extends ISO 19115:2003 by defining the schema required for describing imagery and gridded data. It provides information about the properties of the measuring equipment used to acquire the data, the geometry of the measuring process employed by the equipment, and the production process used to digitize the raw data. It deals with metadata needed to describe the derivation of geographic information from raw data, including properties of the measuring system and numerical methods and computational procedures used in the derivation. ISO 19115:2003 addresses metadata required for coverage data.
Metadata, Imagery, conceptual schema**INCITS/ISO 19118:2005 [2006] Geographic information - Encoding**
Link
ISO
2005
End User License Agreement
2011
Yes
ISO 19118 specifies the requirements for defining encoding rules for interchange of data that conform to the ISO 19100 series of geographic information standard. It specifies requirements for creating encoding rules based on UML schemas, creating encoding services, and XML-based encoding rules for neutral interchange of data. It does not specify digital media, define transfer services or transfer protocols, or specify how to encode inline large images.
Encoding**INCITS/ISO 19119:2005 [R2015] Geographic information - Services**
Link
ISO
2005
End User License Agreement
2011
Yes
ISO 19119 identifies and defines the architecture patterns for service interfaces used for geographic information, defines its relationship to the Open Systems Environment model, and presents a geographic services taxonomy and geographic services placed in the services taxonomy. It prescribes how to create a platform-neutral service specification and derive conformant platform-specific service specifications. It provides guidelines for selection and specification of geographic services from both platform-neutral and platform-specific perspectives.
Open web services,**INCITS/ISO 19119:2005/AM 1:2008[R2013] Geographic information -- Services - Amendment 1: Extensions of the service metadata model**
Link
ISO
2008
End User License Agreement
2011
Yes

Open web services**INCITS/ISO 19123:2005[R2011] Geographic information - Schema for coverage geometry and functions**
Link
ISO
2005
End User License Agreement
2011
Yes
ISO 19123 defines a conceptual schema for the spatial characteristics of coverages. Coverages are the prevailing data structures in areas such as remote sensing, meteorology, and mapping of bathymetry, elevation, soil and vegetation. Examples of coverages include raster, triangulated irregular networks, point coverages and polygon coverages. Coverages support mapping from a spatial, temporal or spatiotemporal domain to feature attribute values, where feature attribute types are common to all geographic positions within the domain. A coverage domain consists of a collection of direct positions in a coordinate space up to three spatial dimensions and a temporal dimension.
ISO 19123 defines the relationship between the domain of a coverage and its associated attribute range. It defines characteristics of the spatial domain, but not characteristics of the attribute range.
Conceptual schema, coverages**INCITS/ISO 19132:2007[R2013] Geographic information - Location-based services - Reference model**
Link
ISO
2007
End User License Agreement
2011
Yes
ISO 19132:2007 defines a reference model and a conceptual framework for location-based services (LBS) and describes the basic principles by which LBS applications may interoperate. This framework references or contains an ontology, a taxonomy, a set of design patterns and a core set of LBS service abstract specifications in UML. ISO 19132:2007 further specifies the framework's relationship to other frameworks, applications and services for geographic information and to client applications.
Location-based services, LBS, Transportation**INCITS/ISO 19133:2005[R2011] Geographic information - Location-based services - Tracking and navigation**
Link
ISO
2005
End User License Agreement
2011
Yes
ISO 19133:2005 describes the data types and associated operations for implementation *of tracking and navigation services*. It specifies web services that can be made available to wireless devices through web-resident proxy applications, but is not restricted to that environment.
Location-based services, LBS, Transportation**INCITS/ISO 19134:2007[R2012] Geographic information - Location-based services - Multimodal routing and navigation**
Link
ISO
2007
End User License Agreement
2011
Yes
ISO 19134:2007 specifies data types and associated operations for implementation of *multimodal location-based services for routing and navigation*. It specifies web services that may be made available to wireless devices through web-resident proxy applications, but is not limited to that environment.
Location-based services, Transportation**INCITS/ISO 19135:2005[R2011] Geographic information - Procedures for item registration**
Link
ISO
2005
End User License Agreement
2011
Yes
ISO 19135:2005 specifies procedures for establishing, maintaining and publishing registers of unique, unambiguous and permanent identifiers and meanings assigned to items of geographic information. It specifies elements of information for identification and meaning of registered items and manage registration of these items.
Registers**INCITS/ISO 19141:2008[R2013] Geographic information - Schema for moving features**
Link
ISO
2008
End User License Agreement
2011
Yes
ISO 19141 defines how to describe the geometry of a feature that moves as a rigid body. The feature moves within any domain composed of spatial objects as specified in ISO 19107. It may move along a planned route or deviate from the planned route. Physical forces, such as orbital, gravitational, or inertial forces, or other features might influence motion of a feature.
Transportation**ISO 19109:2005 Geographic information - Rules for application schema**
Link
ISO
2005
End User License Agreement
2011
Yes
ISO 19109 defines rules for creating and documenting application schemas, including principles for the definition of features.**INCITS/ISO/IEC TS 19127:2005[2015] Geographic information -- Geodetic codes and parameters**
Link
ISO
2005
End User License Agreement
2011
Yes
ISO TS 19127-2005 defines rules for population and maintenance of registers of geodetic codes and parameters and identifies data elements required within these registers, in compliance with ISO 19135 and ISO 19111. Recommendations for the use of registers, legal aspects, applicability to historic data, completeness, and a mechanism for maintenance are specified by the registers themselves.
Geodetic Control, Registers**ISO 19131:2007 Geographic information - Data product specifications**
Link
ISO
2007
End User License Agreement
2011
Yes
ISO 19131:2007 specifies requirements for specification of geographic data products, based on the concepts of other ISO 19100 geographic information standards.
Data product specifications**INCITS/ISO 19131:2007/AM1:2011[2012] Geographic information - Data product specifications - Amendment 1: Requirements relating to the inclusion of an application schema and feature catalogue and the treatment of coverages in an application schema**
Link
ISO
2011
End User License Agreement
2011
Yes

Data product specifications, coverages**INCITS/ISO/IEC 19136:2007 (R2015) Geographic information - Geography Markup Language (GML)**
Link
ISO
2007
End User License Agreement
2011
Yes
GML is an XML encoding for transport and storage of geographic information. It includes both spatial and non-spatial properties of geographic features. Implementers may store geographic application schemas and information in GML or use GML only for schema and data transport.
Encoding, GML, features, XML, Information viewpoint, Information transfer, SDI standards baseline, geospatial application schema**INCITS/ISO 19144-1:2009 [R2015] Geographic information - Classification systems - Part 1: Classification system structure**
Link
ISO
2007
End User License Agreement
2011
Yes
ISO 19144-1 establishes the structure of a geographic information classification system and the mechanism for defining and registering classifiers for such a system. It specifies use of discrete coverages to represent the result of applying the classification system to a particular area and defines the technical structure of a register of classifiers in accordance with ISO 19135.
Land Use - Land Cover, data classification**INCITS/ISO 6709:2008/COR 1:2009 [R2015] Standard representation of geographic point location by coordinates - Technical Corrigendum 1**
Link
ISO
2009
End User License Agreement
2011
Yes

Geodetic Control**INCITS/ISO 6709:2008[R2013] Standard representation of geographic point location by coordinates**
Link
ISO
2008
End User License Agreement
2011
Yes
ISO 6709 specifies representation of horizontal point location and vertical coordinates that may be associated with horizontal coordinates. Representation includes coordinate types, units of measure, and coordinate order. ISO 6709 supports point location representation through XML and allows for use of a single alphanumeric string to describe point locations for backward compatibility with ISO 6709:1983. It does not specify internal procedures, file-organization techniques, storage medium, languages, etc.
Geodetic Control**ISO/IEC 13818-2:2000 MPEG 2 - video**
Link
ISO
2000
End User License Agreement
2011
Yes
The Motion Imagery (Video) standard specifies the structure and data formats for the production, exchange, transmission, or use of digital video data.  INCITS/ISO/IEC 13818-2:2013[2014] revises ISO/IEC 13818-2:2000
Imagery, Motion imagery**ISO/IEC 13818-3:1998 Information technology -- Generic coding of moving pictures and associated audio information -- Part 3: Audio**
Link
ISO
2008
End User License Agreement
2011
Yes
Specifies extension of ISO/IEC 11172-3 to lower sampling frequencies; coded representation of multilingual high quality audio for broadcasting, transmission and storage media; and how to decode multichannel and multilingual high quality audio signals.
Imagery, Motion imagery**INCITS/ISO/IEC 15444-1:2004 [R2015] Information technology - JPEG 2000 image coding system: Core coding system**
Link
ISO
2008
End User License Agreement
2011
Yes
ISO/IEC 15444-1:2004 | ITU-T Rec. T.800 defines bit-preserving (lossless) and lossy compression methods for coding bi-level, continuous-tone grey-scale, palletized color, or continuous-tone color digital still images. It specifies decoding processes for converting compressed image data to reconstructed image data; specifies a code stream syntax containing information for interpreting compressed image data; specifies a file format; provides guidance on encoding processes for converting source image data to compressed image data; and provides guidance on how to implement these processes in practice.
Imagery, Encoding, JPEG**INCITS/ISO/IEC 10918-1:1994[R2013] Information Technology - Digital Compression and Coding of Continuous-Tone Still Images: Requirements and Guidelines (formerly ANSI/ISO/IEC 10918-1-1994)**
Link
ISO
1994
End User License Agreement
2011
Yes
ISO/IEC 10918-1 | ITU-T Recommendation T.81 specifies the core coding technology and incorporates many options for encoding photographic images
Imagery, Encoding, JPEG**ISO/TS 19103:2005 Geographic information - Conceptual schema language**
Link
ISO
1994
End User License Agreement
2011
Yes
ISO 19103:2005 identifies the combination of the Unified Modeling Language (UML) static structure diagram, its associated Object Constraint Language (OCL), and basic type definitions as the conceptual schema language for specification of geographic information. It provides guidelines on how to use UML to create geographic information and service models to enable interoperability. Data types are usually defined by the development environment's data definition language. Each type can be represented in various logically equivalent forms. The ones presented here do not restrict use of other equivalent forms native to the chosen development environment. ISO 19103:2015 revises ISO/TS 19103:2005.**INCITS/ISO TS 19104:2008 [2015] Geographic information - Terminology**
Link
ISO
1994
End User License Agreement
2011
Yes
ISO TS 19104:2008 provides guidelines for collection and maintenance of terminology for geographic information. It establishes criteria for selecting concepts for inclusion in other ISO 191xx standards; specifies the structure of the terminological record; describes principles for definition writing; and lays down guidelines for maintenance of a Terminology Repository.
Terminology**INCITS/ISO TS 19139:2007 [2015] Geographic information - Metadata - XML schema implementation**
Link
ISO
1994
End User License Agreement
2011
Yes
ISO/TS 19139 provides a spatial metadata XML (smXML) encoding and an XML schema implementation derived from ISO 19115. It provides a common XML specification for describing, validating and exchanging geographic metadata. It promotes interoperability through a concrete implementation specification. XML schemas are derived from the harmonized ISO 191XX UML master model. ISO/TS 19139 references scripts for transformation from UML to XML. It provides dataset implementation and extension examples and an abstract conformance test suite. The XML schema allows schemas for datasets, aggregations of datasets, geographic features, feature attributes, feature types, and feature attribute types, etc. Specifics of non-dataset usage of the XML schema are outside the scope of this specification.
Encoding, Metadata, Information transfer, information viewpoint, SDI standards baseline**NetCDF (Network Common Data Form)**
Link
UCAR
2016
copyright
2011
No
NetCDF is a set of software libraries and self-describing, machine-independent data formats that support creation, access, and sharing of array-oriented scientific data.**OpenGIS® Web Feature Service (WFS) Implementation Specification, version 1.1.0 [04-094 ]**
Link
OGC
2005
OGC Policies
2011
No
This document describes WFS operations on geographic features using HTTP. It outlines the protocol for WFS requests:
1. A client application requests a capabilities document from the WFS that describes all operations that the WFS supports and all feature types that it can service. 2. A client application (optionally) makes a request to a WFS for the definition of one or more feature or element types that the WFS can service. 3. Based on the definition of the feature type(s), the client application generates a request, as specified in this document, which is posted to a web server. 4. The WFS is invoked to read and service the request. When it has completed processing the request, it will generate a status report and hand it back to the client. In case of an error, the status report will indicate that fact.
Open web services, Web Feature Services, Features, Computation viewpoint, service invocation, SDI standards baseline**Corrigendum for the OpenGIS® Web Feature Service (WFS) implementation specification 04-095 [OGC 06-027r1]**
Link
OGC
2006
OGC Policies
2011
No
ANNEX A of WFS 1.1.0 references files in the OGC schema repository (http://schemas.opengis.net/wfs/1.1.0) that define XML encoding of operations and documents that describe the API using Web Services Description Language (WSDL). This corrigendum corrects the referenced files that have errors and adds files that are referenced in ANNEX A of WFS 1.1.0
Open web services, Web Feature Services, Features**OpenGIS® Filter Encoding Implementation Specification, version 1.1 [ 04-095 ]**
**Link**
OGC
**2006**
**OGC Policies**
**2011**
**No**
**A filter expression constrains property values of an object type to identify a subset of object instances. OGC web services that require the ability to query objects from a web-accessible repository can use XML filter encoding in a GetFeature operation to define query constraints.**
**FE 1.1 describes an XML encoding of the OGC Common Catalog Query Language (CQL). The XML representation can be easily validated, parsed and then transformed into that target language required to retrieve or modify object instances stored in a persistent object store.**
**Open web services, Web Feature Services, Features, encoding, information viewpoint, information transfer, SDI standards baseline****OpenGIS® Web Map Context (WMC) Documents Implementation Specification, Version 1.1.0 [05-005]**
Link
OGC
2005
OGC Policies
2011
No
WMC is a companion specification to the OGC Web Map Service Interface Implementation Specification version 1.1.1 (WMS 1.1.10. It describes a grouping of one or more maps from one or more map servers in a portable, platform-independent format for storage or transmission between clients. This description is a "Web Map Context Document." A WMC document includes information about the server(s) providing layer(s), the bounding box and map projection shared by all the maps, sufficient operational metadata for client software to reproduce the map, and ancillary metadata to annotate or describe the maps and their provenance. A WMC document is structured using XML. This specification applies to creation and use of documents that unambiguously describe the state, or "Context," of a WMS Client application. Reference is made to normative material from WMS 1.1.1. In some cases, reference is made to the Styled Layer Descriptor specification [SLD]. This specification does not address archival, cataloging, discovery or retrieval of Context XML documents.
Open web services, Web Map Services, Information viewpoint, Information transfer, SDI standards baseline**Corrigendum for OpenGIS Implementation Standard Web Map Context Documents - Corrigendum 1 [08-050]**
Link
OGC
2006
OGC Policies
2011
No
This corrigendum provides change notes for OGC Web Map Context Standard version 1.1 [OGC document 05-005]. Edits and enhancements were made to WMC to correct typographic errors, schema errors, or other deficiencies that prevented proper use of WMC. This corrigendum also documents items that have been deprecated.
Open web services, Web Map Services**OpenGIS® Web Processing Service 1.0.0 [OGC 05-007r7]**
Link
OGC
2005
OGC Policies
2011
No
WPS provides client access to pre-programmed calculations and/or computation models that operate on spatially referenced data. Processes include any algorithm, calculation or model that operates on spatially referenced data. WPS defines an interface that facilitates publishing of geospatial processes and discovery of and binding to those processes by clients. Publishing makes machine-readable binding information and human-readable metadata available for service discovery and use. WPS provides mechanisms to identify spatially referenced data required by the calculation, initiate the calculation, and manage output so that the client can access it. It can be used to process both vector and raster data. It allows a service provider to expose a web accessible process to allow clients to input data and execute the process without specialized knowledge of the underlying physical process interface or API. The WPS interface standardizes how processes and their inputs/outputs are described, how a client can request execution of a process, and how output is handled. Because WPS offers a generic interface, it can be used to wrap other OGC geospatial processing services. To achieve interoperability, each process shall be specified in a separate document called an Application Profile. This document does not specify specific processes that a WPS can implement, nor address archival, cataloguing, discovery, or retrieval of information that a WPS has created.
Open web services, Web Processing Services, Computation viewpoint, Service invocation**Corrigendum for OpenGIS Implementation Standard Web Processing Service (WPS) 1.0.0 [08-091r6]**
Link
OGC
2009
OGC Policies
2011
No
This corrigendum defines change notes for Web Processing Service (WPS) version 1.0.0 Standard. Edits and enhancements correct typographic errors, schema errors, examples, or other deficiency that prevented proper use of WPS. This document provides details of those edits and corrections.
Open web services, Web Processing Services**Symbology Encoding Implementation Specification 1.1.0 [OGC 05-077r4]**
Link
OGC
2006
OGC Policies
2011
No
Symbology Encoding (SE) is an XML language for producing georeferenced maps with user-defined styling. It can be used to portray output of Web Map Servers, Web Feature Servers and Web Coverage Servers. Portrayal tranforms raw information into an explanatory or decision-support tool.
WMS advertises a preset collection of visual portrayals for each available data set. While it provides the user with style options, it can tell the user only the name of each style. It cannot tell the user what portrayal will look like. More importantly, users have no way of defining their own styling rules. The ability for a human or machine client to define these rules requires a styling language that the client and server can both understand.
Open Web Services, Web Map Services, Encoding, Web Feature Services, Web Coverage Services**Styled Layer Descriptor (SLD) profile of the Web Map Service Implementation Specification, version 1.1.0 [OGC 05-078r4]**
Link
OGC
2006
OGC Policies
2011
No
SLD defines an encoding that extends WMS to allow user-defined symbolization and coloring of geographic feature and coverage data. It addresses the need for users and software to control the visual portrayal of the geospatial data. Styling rules require a styling language that both the client and server can understand. SE provides this language, while SLD enables application of SE to WMS layers using extensions of WMS operations. Additionally, SLD defines an operation for standardized access to legend symbols.
Encoding, Open Web Services, Web Map Services**OpenGIS® Web Map Service (WMS) Implementation Specification, Version 1.3.0 [OGC 06-042]**
Link
OGC
2006
OGC Policies
2011
No
WMS provides a simple HTTP interface for requesting geo-registered map images from one or more distributed geospatial databases. GetCapabilities and GetMap operations support creation and display of registered and superimposed map-like views of geospatial information that come simultaneously from multiple sources. An optional third operation (GetFeatureInfo) provides access to information about displayed map features. The response is one or more geo-registered map images (returned as JPEG, PNG, etc) that can be displayed in a browser. The interface also supports the ability to specify whether the returned images should be transparent.
Encoding, Open Web Services, Web Map Services, Computation viewpoint, Service invocation, SDI standards baseline**OpenGIS® Sensor Observation Service (SOS) Interface Standard, version 1.0.0 [OGC 06-009r6]**
Link
OGC
2007
OGC Policies
2011
No
SOS applies to use cases for managing sensor data an interoperable way. It defines a Web service interface that allows querying observations, sensor metadata, and representations of observed features. It defines means to register new sensors and remove existing ones. It defines operations to insert new sensor observations. It specifies KVP and SOAP bindings.
Sensor Web Enablement, Sensor Observation Service**OpenGIS® SensorML Encoding Standard v 1.0 [OGC 07-000] w/Schema Corregendum 1 (1.01)**
Link
OGC
2007
OGC Policies
2011
No
SensorML defines processes and processing components associated with measurement and post-measurement transformation of observations. The SensorML document defines Sensor Web Enablement (SWE) Common data types used throughout SWE encodings and services.
Sensor Web Enablement, Encoding**OpenGIS® Location Services (OpenLS): Tracking Service Interface Standard 1.0.0 [OGC 06-024r4]**
Link
OGC
2008
OGC Policies
2011
No
OpenLS specifies interfaces that enable companies in the LBS value chain to “hook up” and provide their pieces of applications (such as emergency response, personal navigator, traffic information service, proximity service, location recall, mobile field service, travel directions, restaurant finder, corporate asset locator, concierge, routing, vector map portrayal and interaction, friend finder, and geography voice-graphics). Interfaces that implement OpenLS services such as a Directory Service, Gateway Service, Geocoder Service, Presentation (Map Portrayal) Service and others enable these applications.
Location-based services, LBS, Transportation**OpenGIS® Catalogue Service (CAT) Implementation Specification (2.0.2) [OGC 07-006r1]**
Link
OGC
2007
OGC Policies
2011
No
Catalogue services support the discovery of and binding to registered information resources. CAT 2.0.2 specifies interfaces, bindings, and a framework for defining application profiles required to publish and access digital metadata catalogues for geospatial data, services, and related resource information. Catalogue services can return metadata for resource evaluation and invocation or retrieval of the referenced resource.
Open Web Services, Catalog Services, Metadata, Computation viewpoint, Service invocation**Corrigendum [OGC 07-010] for OpenGIS Implementation Specification 07-006: Catalogue Services, Version 2.0.2**
Link
OGC
2007
OGC Policies
2011
No
This corrigendum contains revision notes for CAT 2.0.2. It consists primarily of changes made to the general model and the HTTP Protocol Binding section, with additional edits for consistency. It provides details of edits, deficiency corrections, and enhancements; documents deprecated items; and provides implementations details related to issues of backwards compatibility.
Open Web Services, Catalog Services**OpenGIS® Web Map Tile Service (WMTS) Implementation Standard, version 1.0.0 [OGC 07-057r7]**
Link
OGC
2010
OGC Policies
2011
No
WMTS provides a solution to serve digital maps using predefined image tiles. It advertises the tiles it has available through a declaration in the ServiceMetadata document common to all OGC web services. This declaration defines tiles available for each layer, graphical representation style format, coordinate reference system, scale, and over each geographic fragment of the total covered area. The ServiceMetadata document also declares communication protocols and encodings through which clients can interact with the server. Clients can interpret the ServiceMetadata document to request specific tiles.
Open Web Services, Web Map Services**Web Coverage Service (WCS) Implementation Standard version 1.1.2, Version 1.1 Corrigendum 2 release**
Link
OGC
2008
OGC Policies
2011
No
WCS 1.1.2 is used to provide access to coverage data. It supports only grid coverages. It provides three operations: GetCapabilities, GetCoverage, and DescribeCoverage. It specifies core requirements for a WCS implementation. It does not prescribe support for any particular coverage encoding format. While GML is the canonical format for the definition of WCS, WCS 1.1.2 does not require that a concrete instance of a WCS implement the GML coverage format.
WCS extension standards add functionality to obtain a complete implementation. WCS encoding extensions are designed so that GML coverage information specified in this core is consistent with the contents of an encoded coverage.
Open Web Services, Web Coverage Services, SDI Baseline, Computation viewpoint, service invocation, coverages**OGC 07-074 OpenGIS® Location Services (OpenLS): Core Services, version 1.2**
Link
OGC
2008
OGC Policies
2011
No
OpenLS specifies interfaces that enable companies in the Location Based Services (LBS) value chain to provide their pieces of applications (such as emergency response, personal navigator, traffic information service, proximity service, location recall, mobile field service, travel directions, restaurant finder, corporate asset locator, concierge, routing, vector map portrayal and interaction, friend finder, and geography voice-graphics) and "hook up." Interfaces that implement OpenLS services such as Directory Service, Gateway Service, Geocoder Service, Presentation (Map Portrayal) Service and others enable these applications.
Location-based services, Transportation**OGC KML 2.2 - Abstract Test Suite (1.0.0) [OGC 07-134r2]**
Link
OGC
2008
OGC Policies
2011
No
This abstract test suite (ATS) is a compendium of abstract test cases for verifying the structure and content of OGC KML 2.2 instance documents. It defines three conformance levels; each level builds on the preceding ones.
Encoding, KML, Information viewpoint, information transfer, SDI standards baseline**OpenGIS® KML, version 2.2.0 [OGC 07-147r2]**
Link
OGC
2008
OGC Policies
2011
No
KML is an XML grammar used to encode and transport representations of geographic data for display in an earth browser. It encodes what to show in an earth browser and how to show it. It uses a tag-based structure with nested elements and attributes. Web browsers process a KML instance in much the same way that they process HTML and XML.
Encoding, KML**OpenGIS® Location Services (OpenLS): Part 6-Navigation Service (1.0.0) [OGC 08-028r7]**
Link
OGC
2008
OGC Policies
2011
No
Navigation Service is an extended profile of the Route Service. It is part of the GeoMobility Server (GMS), an open location services platform.
Location-based services, Transportation**OpenGIS® Location Services: Tracking Service Interface Standard [OGC 06-024r4]**
Link
OGC
2008
OGC Policies
2011
No
The OpenGIS Tracking Service Interface Standard supports a very simple functionality that allows tracking of a collection of movable objects as they move and change orientation. It addresses the absolute minimum in functionality for geospatial tracking.
Location-based services, Transportation**Tagged Image File Format (TIFF) Revision**
Link
ISO
2004
End User License Agreement
2011
Yes
TIFF is a tag-based file format for storing and describing raster images. It provides a rich environment that takes advantage of varying capabilities of scanners and other imaging devices for exchanging image data. The number of required fields is small. TIFF can describe bi-level, grayscale, palette-color, and full-color image data in several color spaces. It includes compression schemes that allow developers to choose the best space or time tradeoff for their applications. It does not favor particular operating systems, file systems, compilers, or processors.
Encoding, Imagery, TIFF**INCITS/ISO 19156:2011[2012] Geographic information - Observations and measurements**
Link
ISO
2011
End User License Agreement
2011
Yes
ISO 19156:2011 defines a conceptual schema for observations and features involved in sampling when making observations for exchange of information describing observation acts and their results. The schema includes relationships between sampling features (sub-sampling, derived samples). It concerns only externally visible interfaces and places no restriction on the underlying implementations other than what is needed to satisfy the interface specifications in the actual situation.
Sensor Web Enablement, Observations & Measurements, Abstract standard**[OGC 10-126r3] OGC® WaterML 2.0: Part 1- Time series**
Link
OGC
2012
OGC Policies
2012
No
OGC® WaterML 2.0: Part 1 is an encoding standard for the representation of hydrological observations data, with a specific focus on time series structures. WaterML2.0 is implemented as an application schema of the GML 3.2.1 and makes use of the OGC Observations & Measurements standards. Replaced by Version 2.0.1
Water - Inland, Water - Oceans and Coasts, Encoding, GML**Time-Space-Position Information (TSPI), Version 2.0, (2012-04-05)**
Link
NCGIS
2012
unrestricted
2012
No
TSPI Version 2.0 specifies a core XML schema for encoding spatial, temporal, and accompanying quality assessment characteristics of real-world entities. It is a set of reusable data components for developing GML and non-GML XML based schemas. It specifies a registry-based extension mechanism for development and reuse of additional spatiotemporal XML Schema components. It integrates the XML Schema for the United States Thoroughfare, Landmark, and Postal Address Data Standard, FGDC-STD-016-2011.
TSPI includes a platform-specific encoding using XML Schema, which is available through http://nsgreg.nga.mil/doc/view?i=82043.
Encoding, XML, Address, GML**OpenGIS Web Feature Service (WFS) 2.0 Interface Standard [09-025r1] (also ISO 19142)**
Link
OGC
2010
OGC Policies

No
WFS 2.0 applies to systems that have requirements to access or distribute geospatial feature data. A WFS request consists of a description of query or data transformation operations applied to one or more features. The request is generated on the client side and posted to a web feature server using HTTP. The WFS then reads the request and returns results that conform to GML. WFS offers direct access to geographic information at the feature and feature property level and allow clients to retrieve or modify only the data they seek, rather than an entire file.
Open Web Services, Web Feature Services, features, GML**GeoRSS-Simple and GeoRSS-GML**
Link
de facto

license

No
GeoRSS is a standardized way to encode location in RSS and Atom feeds. It allows users to perform searches on feeds using all sorts of geographic criteria. Its location content consists of geometries and related feature descriptions. Geographic software such as map generators can consume GeoRSS feeds.
GeoRSS-Simple is a very lightweight format that supports basic geometries (point, line, box, and polygon), while GeoRSS GML is a formal GML Application Profile that supports a greater range of features, notably coordinate reference systems other than WGS-84 latitude/longitude.
Encoding, GeoRSS, GML, Information viewpoint, Information transfer, SDI standards baseline**ISO/IEC 15444-1:2004 Technical Corrigendum 1:2007**
Link
ISO
2007
End User License Agreement
2011
Yes
ISO/IEC 15444-1:2004 Technical Corrigenda 1:2007 and 2:2008 JPEG 2000 serve as errata for ISO/IEC 15444-1:2014, Information technology -- JPEG 2000 image coding system: Core coding system. The FGDC has endorsed ISO/IEC 15444-1:2004.
ISO ISO/IEC 15444-1:2016 revises ISO/IEC 15444-1:2004 and its amendments and corrigenda
Imagery, JPEG**ISO/IEC 15444-1:2004 Technical Corrigendum 2:2008 JPEG 2000 image coding system: Core coding system**
Link
ISO
2008
End User License Agreement
2011
Yes
ISO/IEC 15444-1:2004 Technical Corrigenda 1:2007 and 2:2008 JPEG 2000 serve as errata for ISO/IEC 15444-1:2014, which FGDC endorsed.  ISO ISO/IEC 15444-1:2016 revises ISO/IEC 15444-1:2004 and its amendments and corrigenda
Imagery, JPEG**Aeronautical Information Exchange Model (AIXM) 5.1**
Link
FAA, EUROCONTROL

unrestricted

No
AIXM 5.1 is an exchange format that contains hundreds of entities, data types, and relationships used to represent aeronautical data. It enables data exchange applicable to aerodromes (airports), heliports, routes, navigation aids, fixes, instrument approach procedures, instrument departures, standard terminal arrival routes, organizations, units, services, obstacles and airspace. It uses GML to leverage commercial-off-the-shelf (COTS) tools and web services.
AIXM is based on ICAO standards and recommended practices and industry standards requirements for data exchange and GIS capability. Its conceptual model uses the Unified Modeling Language (UML) to define relationships, behavior, and high-level ideas for aeronautical data.
Transportation, Air, Encoding, XML, GML**Real Property Asset Data Standard (RPADS), FGDC-STD-019-2014**
Link
FGDC
2014
unrestricted
2015
No
The Real Property Asset Data Standard (RPADS) defines essential data needed to identify Real Property Assets (RPAs) such as buildings, land parcels, linear structures, and structures. It establishes fundamental definitions for RPAs and provides a minimum set of attributes needed to locate RPAs on a map and identify what the RPA is, with standardized attribute values where appropriate. RPA data will support for federal real property management, homeland security, emergency response, high-performance green buildings management, and other federal government initiatives.
Real Property*Categories are **Reference and Abstract Standards (RAS), Common Encoding Standards (CES), Common Service Standards (CSS), Content/Code Standards (CCS)**
 
StandardMost recent statusDocument DateSponsor**Earth Cover Classification Standard**
Proposal
1999/09/13
Earth Cover Working Group (inactive)**Geologic Data Model**
Proposal
2001/10/10
Geologic Data Subcommittee**Shoreline Data Content Standard**
Public review draft
2007/03/07
National Geodetic Survey**Content Standards for Framework Land Elevation Data**
Final draft
1999/01
Subcommittee for Base Cartographic Data (retired)**Cultural Resources Geospatial Data Content Standard**
Proposal
2008/02/14
Subcommittee on Cultural and Demographic Data**Federal Buildings and Facilities Geospatial Data Content Standard**
Proposal
2010/01
General Services Administration (GSA)**Maintenance and Review of the National Wetland Classification Standard**
Proposal
2010/02
Wetlands Subcommittee

These projects, which did not result in FGDC-endorsed standards, were discontinued at the request of the sponsor.
ProjectStatusDateSponsorReason**Content Standard for Digital Geospatial Metadata: Thematic Supplement for Geospatially Referenced Cultural and Demographic Data Metadata**
Proposal

Subcommittee on Cultural and Demographic Data
This project has been discontinued at the request of its sponsor, the Subcommittee on Cultural and Demographic Data.**Environmental Hazards Geospatial Data Content Standard**
Proposal

Facilities Working Group
This project has been discontinued at the request of its sponsor, the Facilities Working Group (now inactive).**Transportation Data Content Standard**
Proposal

Facilities Working Group
This project has been discontinued at the request of its sponsor, the Facilities Working Group (now inactive).**Address Data Content Standard**
Public Review Draft
2003/04/17
Subcommittee on Cultural and Demographic Data
This project has been replaced by the FGDC standards project United States Thoroughfare, Landmark, And Postal Address Data Standard**NSDI Framework Transportation Identification Standard**
Public Review Draft
2000/12
Ground Transportation Subcommittee
This project has been replaced by INCITS Project 1574-D Information Technology - Geographic Information Framework Data Content Standard**Data Content Standard for Location and Identification of Facilities**
Final draft
1998/12
Facilities Working Group
By recommendation of the U.S. Army Corps of Engineers, which chaired the Facilities Working Group (now inactive).**National Standards for the Floristic Levels of Vegetation Classification in the United States: Associations and Alliances**
Proposal

Vegetation Subcommittee
This project has been discontinued, as the National Vegetation Classification Standard (Version 2.0) encompasses this effort.**Revisions to the National Standards for the Physiognomic Levels of Vegetation Classification in the United States**
Proposal

Vegetation Subcommittee
This project has been discontinued, as the National Vegetation Classification Standard (Version 2.0) encompasses this effort.**Governmental Unit Boundary Data Content Standard**
Proposal
1997/11
Subcommittee on Cultural and Demographic Data
This project has been superseded by FGDC endorsement of the Geographic Information Framework Data Content Standard, Part 5, Government Units, FGDC-STD-014.5-2008**Hydrographic Data Content Standard for Coastal and Inland Waterways**
Public Revieew Draft
2000/01
Subcommittee for Coastal  and Marine Spatial Data
This project has been discontinued at the request of the sponsor.**Biological Nomenclature and Taxonomy Standard**
Proposal
1999/07/22
Biological Data Working Group**Riparian Mapping Standard**
Proposal
2000/11/14
Wetlands Subcommittee
The Chair, FGDC Wetlands Subcommittee, said that the project should be discontinued.  The standard is a U.S. Fish and Wildlife standard, and the subcommittee does not seek FGDC endorsement.**National Hydrography Framework Data Standard**
Proposal
2000/12/12
Subcommittee on Spatial Water Data
This project has been superseded by FGDC endorsement of the Geographic Information Framework Data Content Standard, Part 6, Hydrography, FGDC-STD-014.6-2008**Federal Standards for Delineation of Hydrologic Unit Boundaries**
Working draft
2003/12/23
Spatial Water Data Subcommittee
At request of Water Boundary Dataset team**Encoding Standard for Metadata**
Working draft
2000/02/17
Clearinghouse Working Group
At request of FGDC Metadata WG**FGDC Profile(s) of ISO 19115**
Proposal
2001/06/13
Metadata WG
At request of FGDC Metadata WG Contact Us
                                **Office:**
                                        12201 Sunrise Valley Dr.
                                        MS 590 Reston, VA 20192
                                    **Fax:** (+1) 703
                                    648 5755**Email:**
                                    fgdc@fgdc.gov
                    **Subscribe** to Our Mailing List
                            for Important News & Updates
                            
                            Subscribe
                        **Like
                                    us**
                                **Follow
                                    us**
                                **RSS**
            The Federal Geographic Data Committee.Policies & Notices / USA.gov
                            Download Adobe Reader /
                            Download Office Viewers