Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more

GIS standards fall into overlapping categories, not one universally fixed list. Some define what geospatial data means, others specify how it is encoded or accessed, and still others focus on metadata or a particular subject such as water or city models. To classify a standard accurately, first ask whether you mean its purpose, its implementation form, or the subject it covers.

What “category” means for GIS standards

Standards bodies organize geospatial standards in different ways. The Open Geospatial Consortium (OGC) describes functional types, its catalogue groups standards into families, and the Federal Geographic Data Committee (FGDC) lists standards by topics such as metadata, encoding, services, and data content. Those schemes answer different questions rather than competing to define a single official taxonomy.

The categories below are a practical map synthesized from OGC and FGDC descriptions; they are not a combined classification formally adopted by either organization. A single standard may fit more than one category: a domain standard, for instance, can define a data model and an encoding as well as the subject matter. OGC explains its functional types and standards program, while FGDC’s standards list illustrates its broader catalogue.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

What are the main categories of GIS standards?

Conceptual models and data content

These standards define what the data represents: the concepts, feature types, attributes, relationships, constraints, and organization that systems should understand consistently. They address meaning, not merely file format. For example, the FGDC Geographic Information Framework Data Standard describes schemas covering feature and attribute types, domains, relationships, spatial representation, data organization, and metadata. FGDC’s framework standard applies to seven National Spatial Data Infrastructure (NSDI) themes: cadastre, imagery, elevation, geodetic control, government units and administrative or statistical boundaries, inland water, and transportation.

Encoding standards

An encoding standard specifies rules for representing and organizing information so it can be exchanged or processed. It is distinct from a content model: the model says what concepts and properties data should contain; the encoding says how to express them in a representation. FGDC lists ISO 19118 as a geographic-information encoding standard and distinguishes encoding rules from media, transfer services, and protocols. Consult FGDC’s standards list for the listing and verify the current record before implementation.

Interfaces and services

Interface standards define operations through which a requester interacts with a service provider. OGC’s catalogue includes service families such as Web Map Service (WMS), Web Feature Service (WFS), Web Coverage Service (WCS), and Web Processing Service (WPS). These names identify families, not a guarantee that every version or implementation offers the same capabilities. Check the relevant current standard record for version and status in your intended deployment. OGC’s catalogue and standards information provide the appropriate starting point.

Metadata and discovery

Metadata helps people and software understand, assess, and find geospatial resources. It can describe datasets as well as services. FGDC describes ISO 19115-1 as the fundamental standard at the center of the ISO metadata suite; related standards extend the core, document associated information, or provide XML encoding and validation. FGDC also publishes its own Content Standard for Digital Geospatial Metadata (CSDGM). FGDC’s ISO metadata standards page explains the suite, while its CSDGM page describes the U.S. standard.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Content standards specify metadata elements and their properties; encoding standards specify how that metadata is structured and validated in a representation such as XML. OGC’s Catalogue Service Standard addresses the service side of discovery, defining interfaces, bindings, and application profiles for publishing and accessing catalogues of metadata about geospatial data, services, and related resources. See the OGC Catalogue Service Standard.

Domain-specific standards

These standards specialize geospatial conventions for a subject area. OGC’s catalogue includes examples such as CityGML and WaterML, while FGDC’s framework standard addresses selected NSDI themes. A domain standard may also prescribe content models, encodings, or interfaces, so “domain-specific” describes scope rather than a mutually exclusive technical function. OGC’s standards catalogue lists examples.

How the categories fit together in a real exchange

Suppose two organizations need to exchange road-network features. They need to agree on what counts as a road feature and which attributes and relationships matter; choose a representation that both can encode and interpret; and, if exchange occurs through a service, identify the supported interface and operations. Metadata can help users assess and find the dataset or service. The choices are related, but a standard addressing one layer does not automatically settle the others.

Rank #4
Sale
Web Mapping Illustrated: Using Open Source GIS Toolkits
  • Web Mapping Illustrated By Mitchell Tyler

As OGC puts it, “Together, these standards define interoperable approaches to geospatial data organization, access, processing, visualization, and discovery.” This is the standards body’s description of its program, not a measured claim about outcomes. OGC’s standards-program page provides the statement and context.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

How to choose the right GIS standard

Start with the work the standard must support, then check the scope and authority that apply to your project. A useful comparison asks:

Best Value
Mark Twain Forensic Investigations Workbook, Using Science to Solve High Crimes Middle School Books, Critical Thinking for Kids, DNA and Handwriting Analysis Labs, Classroom or Homeschool Curriculum
  • Students build unmatched deductive-reasoning skills as they become crime-solving stars
  • Most scenarios have more than one plausible outcome, allowing individuals or groups to broadly interpret evidence
  • Includes interpretive handwriting, body language, fingerprinting, and many more activities
  • Purpose: Are you defining data content, documenting or discovering resources, encoding information, providing service operations, or addressing portrayal and visualization?
  • Scope: Is the need general geospatial interoperability or a specific theme such as elevation, imagery, water, or transportation?
  • Interoperability boundary: Do you need agreement on a data model, a serialized representation, service operations, or an integrated profile?
  • Governance and adoption: Which standards body or jurisdiction is relevant, and is the standard endorsed, required, or simply available for voluntary use?
  • Implementation fit: Can your systems support the relevant schema, encoding, and service, and does it fit the data and workflow already in use?

For U.S. federal agencies, FGDC explains that agencies are directed toward voluntary consensus standards and that ISO metadata standards are endorsed and encouraged for NSDI stakeholders. This is U.S. federal guidance, not a universal requirement for every GIS project. The applicable choice for a particular organization also depends on its policy, sector, data theme, procurement requirements, and existing systems. See FGDC’s standards guidance and list and its ISO metadata guidance.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Check status before implementation

Standard names and families are useful for orientation, but do not by themselves establish which revision a project should implement. Publication or revision metadata is not proof that a version remains current or is required in a particular jurisdiction. Confirm the current status, version, profile, and adoption requirements with the issuing standards body and the responsible authority for your project. The OGC and FGDC pages linked above provide starting points; they do not determine requirements for every organization.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.