{"id":2469,"date":"2021-12-06T11:38:01","date_gmt":"2021-12-06T11:38:01","guid":{"rendered":"https:\/\/www.ogc.org\/news\/ogc-seeks-public-comment-on-ogc-api-common-part-2-geospatial-data\/"},"modified":"2021-12-06T11:38:01","modified_gmt":"2021-12-06T11:38:01","slug":"ogc-seeks-public-comment-on-ogc-api-common-part-2-geospatial-data-2","status":"publish","type":"post","link":"https:\/\/fm-connect1.fortmindz.in\/wp-ogc\/announcement\/ogc-seeks-public-comment-on-ogc-api-common-part-2-geospatial-data-2\/","title":{"rendered":"OGC Seeks Public Comment on OGC API – Common – Part 2: Geospatial Data"},"content":{"rendered":"

OGC API – Common – Part 2: Geospatial Data provides a common connection between the API landing page (defined by Part 1) and resource-specific details.<\/em><\/p>\n

\"Banner<\/p>\n

The Open Geospatial Consortium (OGC) is seeking public comment on the OGC API – Common – Part 2: Geospatial Data Candidate Standard. The purpose of OGC API – Common – Part 2: Geospatial Data is to provide a common connection between the API landing page and resource-specific details. Comments are due by January 5, 2022.<\/strong><\/p>\n

OGC APIs<\/a> are OGC's Building Blocks for Location, and are ushering in a new age for location information on the web by enabling a much simpler, consistent, and familiar way to share and access location information. Through the OGC APIs, the OGC community is improving how location information can be integrated: by any developer, with any other type of information, and into any type of application.<\/p>\n

OGC API – Common<\/a> serves as a foundation upon which all OGC APIs can be built. OGC API – Common – Part 1: Core defines the resources and access mechanisms which are useful for a client seeking to understand the offerings and capabilities of an API. OGC API – Common – Part 2: Geospatial Data builds on Part 1 by providing a common connection between the API landing page and geospatial data collections.<\/p>\n

Geospatial data is rarely considered as a single entity. Feature Collections, Coverages, Data Sets, etc. are all aggregations of Spatial or Temporal \u2018Things'. It stands to reason that an OGC Web API would also expose its holdings as aggregates of spatial resources. The purpose of the OGC API – Common – Part 2 Standard, then, is to provide a means of organizing these aggregate collections and to define operations for the discovery and selection of individual collections.<\/p>\n

The OGC API – Common – Part 2 Standard does not specify the nature of the geospatial data that make up a collection. Rather, it provides a basic capability that should be applicable to any geospatial resource type. Additional OGC Web API standards extend this foundation to define resource-specific capabilities.<\/p>\n

In parallel to this public review, the OGC Naming Authority is assessing the naming conventions to be used in the Requirements Modules defined in the candidate Standard. These conventions are important in the continued modularization of the OGC APIs, so careful review by experts is welcomed.<\/strong><\/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>.<\/p>\n

OGC Members interested in staying up to date on the progress of this standard, or contributing to its development, are encouraged to join the OGC API – Common SWG via the OGC Portal<\/a>.<\/p>\n

The OGC API – Common – Part 2: Geospatial Data Candidate Standard<\/a> is available for review and comment on the OGC Portal<\/a>. Comments are due by January 5, 2022,<\/strong> and should be submitted via the method outlined on the OGC API – Common – Part 2: Geospatial Data Standard's public comment request page<\/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":"

OGC API – Common – Part 2: Geospatial Data provides a common connection between the API landing page (defined by Part 1) and resource-specific details.The Open Geospatial Consortium (OGC) is seeking public comment on the OGC API – Common – Part 2: Geospatial Data Candidate Standard.The purpose of OGC API – Common – Part 2: Geospatial Data is to provide a common connection between the API landing page and resource-specific details.OGC API – Common – Part 2: Geospatial Data builds on Part 1 by providing a common connection between the API landing page and geospatial data collections.The OGC API – Common – Part 2: Geospatial Data Candidate Standard is available for review and comment on the OGC Portal.<\/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-2469","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\/2469","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=2469"}],"version-history":[{"count":0,"href":"https:\/\/fm-connect1.fortmindz.in\/wp-ogc\/wp-json\/wp\/v2\/posts\/2469\/revisions"}],"wp:attachment":[{"href":"https:\/\/fm-connect1.fortmindz.in\/wp-ogc\/wp-json\/wp\/v2\/media?parent=2469"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fm-connect1.fortmindz.in\/wp-ogc\/wp-json\/wp\/v2\/categories?post=2469"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fm-connect1.fortmindz.in\/wp-ogc\/wp-json\/wp\/v2\/tags?post=2469"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}