{"id":13584,"date":"2024-09-18T09:00:00","date_gmt":"2024-09-18T13:00:00","guid":{"rendered":"https:\/\/www.ogc.org\/?p=13584"},"modified":"2024-09-18T09:00:00","modified_gmt":"2024-09-18T13:00:00","slug":"ogc-membership-approves-ogc-api-features-part-3-filtering-as-an-official-ogc-standard","status":"publish","type":"post","link":"https:\/\/fm-connect1.fortmindz.in\/wp-ogc\/announcement\/ogc-membership-approves-ogc-api-features-part-3-filtering-as-an-official-ogc-standard\/","title":{"rendered":"OGC Membership approves OGC API – Features – Part 3: Filtering as an official OGC Standard"},"content":{"rendered":"\n

The Open Geospatial Consortium (OGC) Membership has approved OGC API – Features – Part 3: Filtering<\/em> as an official OGC Standard. <\/p>\n\n\n\n

OGC API – Features<\/a> defines a web interface for creating, modifying, and querying feature data. Part three of this standard is focused on defining query parameters and the Queryables resource, allowing users to specify filter criteria in API requests. <\/p>\n\n\n\n

OGC API – Features – Part 3<\/em>: <\/em><\/strong>Filtering<\/em> extends the ability to extract data subsets that meet specific criteria beyond bounding boxes or date and time attributes. This enhanced query functionality is specified using the Common Query Language (CQL2) \u2013 a recently approved OGC Standard<\/a>. <\/p>\n\n\n\n

Part 3 is designed to extend and interoperate with other parts of the OGC API – Features Standard. It builds on Part 1, which defines basic server behavior and is compatible with Part 2, which extends support for different Coordinate Reference Systems. <\/p>\n\n\n\n

To help developers quickly implement products that support this standard, example API definitions and schemas are available on the OGC API – Features webpage<\/a>. These resources conform to the OpenAPI Specification v3.0<\/a>, making them easy to integrate into various Web APIs.  <\/p>\n\n\n\n

OGC API – Features – Part 3<\/em>: <\/em><\/strong>Filtering<\/em> is the outcome of the work and dedication of the OGC API – Features Standards Working Group. Development of the standard was led by: <\/p>\n\n\n\n