{"id":17158,"date":"2021-10-07T10:28:39","date_gmt":"2021-10-07T10:28:39","guid":{"rendered":"https:\/\/www.ogc.org\/news\/compliance-testing-now-available-for-\u2018ogc-api-features-part-2\u2019-standard\/"},"modified":"2025-11-18T11:06:40","modified_gmt":"2025-11-18T11:06:40","slug":"compliance-testing-now-available-for-ogc-api-features-part-2-standard","status":"publish","type":"post","link":"https:\/\/fm-connect1.fortmindz.in\/wp-ogc\/announcement\/compliance-testing-now-available-for-ogc-api-features-part-2-standard\/","title":{"rendered":"Compliance testing now available for \u2018OGC API – Features – Part 2\u2019 standard"},"content":{"rendered":"

OGC compliance provides confidence that a product will seamlessly integrate with other compliant solutions regardless of the vendor that created them. <\/em><\/p>\n

\"Banner<\/p>\n

The Open Geospatial Consortium (OGC) is excited to announce that the OGC Membership has approved an enhancement to the OGC Validator tool<\/a> to offer compliance tests for version 1.0 of the OGC API – Features – Part 2: Coordinate Reference Systems by Reference<\/a> Standard. Products that implement the standard and pass the compliance tests can now be certified as OGC Compliant.<\/p>\n

Implementers are invited to validate their products using the OGC API – Features executable test suite, which is available on the OGC Validator tool<\/a>. The executable test suite can now assess compliance to both Parts 1 and 2 of OGC API – Features<\/a>. These tests typically take only 5-10 minutes to complete. Once a product has passed the test, implementers can submit an application to OGC for permission to use the OGC Compliant trademark on their product.<\/p>\n

The OGC API – Features Standard offers the capability to create, modify, and query spatial data on the Web. The Standard specifies requirements and recommendations for APIs that want to follow a standardized, simple, accessible way of sharing feature data. OGC API – Features is a multi-part standard, with Part 1, the \u201cCore,\u201d describing the capabilities that every implementing service has to support. Implementations built using only Part 1 can provide read-only access to spatial data that is referenced to the WGS 84 Coordinate Reference System (CRS). Part 2 enables the use of different CRSs, in addition to WGS 84 ('write' capabilities – specifically Create, Replace, Update, and Delete operations – will come in Part 4).<\/p>\n

The OGC API – Features standard is part of the OGC API<\/a> family of Standards, the Building Blocks For Location. OGC API Standards define modular APIs that spatially enable Web APIs in a consistent way. OGC API Standards make use of the popular OpenAPI specification, so are easy to implement and access. To help developers get started, OGC provides a variety of resources relevant to OGC API – Features<\/a> and other OGC APIs on the OGC API website<\/a>. Further, ldproxy<\/a> by interactive instruments GmbH<\/a> and deegree<\/a> by lat\/lon GmbH<\/a> have been designated as Reference Implementations. <\/p>\n

The OGC Compliance Program<\/a> is a certification process that ensures organizations' solutions are compliant with OGC Standards. It is a universal credential that allows agencies, industry, and academia to better integrate their solutions. OGC compliance provides confidence that a product will seamlessly integrate with other compliant solutions regardless of the vendor that created them. <\/p>\n

More information about the OGC compliance process is available at ogc.org\/compliance<\/a>. Implementers of the OGC API – Features – Part 2: Coordinate Reference Systems by Reference Standard – or other OGC Standards – are invited to validate their products using the OGC validator tool<\/a>.<\/em><\/p>\n

To learn more about how the family of OGC API Standards work together to provide modular \u201cbuilding blocks for location\u201d that address both simple and the most complex use-cases, visit ogcapi.org<\/a>.<\/em><\/p>\n

About OGC<\/strong>
The Open Geospatial Consortium (OGC) is a collective problem-solving community of experts from more than 500 businesses, government agencies, research organizations, and universities driven to make geospatial (location) information and services FAIR – Findable, Accessible, Interoperable, and Reusable.
The global OGC Community engages in a mix of activities related to location-based technologies: developing consensus-based open standards and best-practice; collaborating on agile innovation initiatives; engaging in community meetings, events, and workshops; and more.
OGC's unique standards development process moves at the pace of innovation, with constant input from technology forecasting, practical prototyping, real-world testing, and community engagement.
OGC bridges disparate sectors, domains, and technology trends, and encourages the cross-pollination of ideas between different communities of practice to improve decision-making at all levels. OGC is committed to creating an inclusive and sustainable future.
Visit ogc.org<\/a> for more info on our work.<\/p>\n

“<\/p>\n","protected":false},"excerpt":{"rendered":"

Implementers are invited to validate their products using the OGC API – Features executable test suite, which is available on the OGC Validator tool.The OGC API – Features Standard offers the capability to create, modify, and query spatial data on the Web.The OGC API – Features standard is part of the OGC API family of Standards, the Building Blocks For Location.To help developers get started, OGC provides a variety of resources relevant to OGC API – Features and other OGC APIs on the OGC API website.Implementers of the OGC API – Features – Part 2: Coordinate Reference Systems by Reference Standard – or other OGC Standards – are invited to validate their products using the OGC validator tool.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_eb_attr":"","footnotes":""},"categories":[169],"tags":[],"class_list":["post-17158","post","type-post","status-publish","format-standard","hentry","category-announcement"],"acf":[],"_links":{"self":[{"href":"https:\/\/fm-connect1.fortmindz.in\/wp-ogc\/wp-json\/wp\/v2\/posts\/17158","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/fm-connect1.fortmindz.in\/wp-ogc\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/fm-connect1.fortmindz.in\/wp-ogc\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/fm-connect1.fortmindz.in\/wp-ogc\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/fm-connect1.fortmindz.in\/wp-ogc\/wp-json\/wp\/v2\/comments?post=17158"}],"version-history":[{"count":1,"href":"https:\/\/fm-connect1.fortmindz.in\/wp-ogc\/wp-json\/wp\/v2\/posts\/17158\/revisions"}],"predecessor-version":[{"id":23665,"href":"https:\/\/fm-connect1.fortmindz.in\/wp-ogc\/wp-json\/wp\/v2\/posts\/17158\/revisions\/23665"}],"wp:attachment":[{"href":"https:\/\/fm-connect1.fortmindz.in\/wp-ogc\/wp-json\/wp\/v2\/media?parent=17158"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fm-connect1.fortmindz.in\/wp-ogc\/wp-json\/wp\/v2\/categories?post=17158"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fm-connect1.fortmindz.in\/wp-ogc\/wp-json\/wp\/v2\/tags?post=17158"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}