{"id":17199,"date":"2022-03-30T10:28:55","date_gmt":"2022-03-30T10:28:55","guid":{"rendered":"https:\/\/www.ogc.org\/news\/ogc-seeks-public-comment-on-candidate-ogc-api-tiles-part-1-core-standard\/"},"modified":"2022-03-30T10:28:55","modified_gmt":"2022-03-30T10:28:55","slug":"ogc-seeks-public-comment-on-candidate-ogc-api-tiles-part-1-core-standard-2","status":"publish","type":"post","link":"https:\/\/fm-connect1.fortmindz.in\/wp-ogc\/announcement\/ogc-seeks-public-comment-on-candidate-ogc-api-tiles-part-1-core-standard-2\/","title":{"rendered":"OGC seeks public comment on candidate OGC API – Tiles – Part 1: Core Standard"},"content":{"rendered":"

The OGC API – Tiles specification enables Web APIs to quickly and efficiently serve tiles of spatially referenced data or of maps with predefined content, extent, and resolution.<\/em> <\/p>\n

\"OGC<\/p>\n

The Open Geospatial Consortium (OGC) seeks public comment on the candidate OGC API – Tiles – Part 1: Core Standard<\/a>. Comments are due by April 29, 2022.<\/strong><\/p>\n

OGC API – Tiles<\/a> uses the latest technologies and spatial data on the web best practices<\/a> to enable Web APIs to serve tiles of spatially referenced data or of maps. The candidate standard offers additional functionality beyond that offered by the Web Map Tile Service (WMTS)<\/a> – a well-established and commonly implemented OGC standard first issued in 2007.<\/p>\n

OGC API Standards are developed in a modular way, meaning that their functionality can be added to existing web APIs as desired. This is why we call the family of OGC API Standards the “Building Blocks For Location.”<\/em><\/p>\n

The candidate OGC API – Tiles specification, therefore, describes the API building blocks that can enable existing OGC API implementations (as well as other Web APIs) to efficiently serve tiles of spatially referenced data or of maps with predefined content, extent, and resolution. <\/p>\n

As with other OGC API Standards<\/a>, OGC API – Tiles is delivered in \u2018Parts' that allow developers to pick and choose the functionality they want in the API they are building. This minimizes complexity and development time, and allows future use-cases and technology changes to be added to the Standard as new parts without breaking existing implementations. Part 1: Core provides the minimum functionality required for a Web API to successfully serve spatially-referenced tiles to a client for the most common use-cases.<\/p>\n

The candidate OGC API – Tiles – Part 1: Core Standard defines how to: discover which resources offered by a Web API can be retrieved as tiles; get metadata about the available tile sets; and request a tile. Tiles can represent a single collection or multiple collections, as defined in the Web API.<\/p>\n

Additionally, the core conformance class describes how to retrieve a tile of an arbitrary resource using tile indices. It is defined in a way that could be easily included in a web API that does not conform to the foundational OGC API – Common<\/a> standard. A web API can combine some requirements classes of this candidate OGC API standard with other OGC API standards (including OGC API – Common) to add functionality to said web API.<\/p>\n

The candidate OGC API – Tiles Standard leverages the concepts of tile matrix sets and tile sets defined in the candidate OGC Two Dimensional Tile Matrix Set and Tile Set Metadata Standard<\/a>, also implicitly used in WMTS and GeoPackage. The candidate OGC API – Tiles Standard can, therefore, be used to publish tiled maps (e.g., PNG, JPEG), tiled feature data (e.g., GeoJSON Vector Tiles, Mapbox Vector Tiles), or tiled coverages (e.g., netCDF, GeoTIFF).<\/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 – Tiles SWG via the OGC Portal<\/a>.<\/p>\n

The candidate OGC API Tiles – Part 1: Core Standard<\/a> is now open for public review and comment. Comments are due by April 29, 2022<\/strong>, and should be submitted via the OGC API Tiles – Part 1: Core Standard's public GitHub Repository<\/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":"

The Open Geospatial Consortium (OGC) seeks public comment on the candidate OGC API – Tiles – Part 1: Core Standard.As with other OGC API Standards, OGC API – Tiles is delivered in \u2018Parts\u2019 that allow developers to pick and choose the functionality they want in the API they are building.A web API can combine some requirements classes of this candidate OGC API standard with other OGC API standards (including OGC API – Common) to add functionality to said web API.The candidate OGC API – Tiles Standard can, therefore, be used to publish tiled maps (e.g., PNG, JPEG), tiled feature data (e.g., GeoJSON Vector Tiles, Mapbox Vector Tiles), or tiled coverages (e.g., netCDF, GeoTIFF).The candidate OGC API Tiles – Part 1: Core Standard is now open for public review and comment.<\/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-17199","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\/17199","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=17199"}],"version-history":[{"count":0,"href":"https:\/\/fm-connect1.fortmindz.in\/wp-ogc\/wp-json\/wp\/v2\/posts\/17199\/revisions"}],"wp:attachment":[{"href":"https:\/\/fm-connect1.fortmindz.in\/wp-ogc\/wp-json\/wp\/v2\/media?parent=17199"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fm-connect1.fortmindz.in\/wp-ogc\/wp-json\/wp\/v2\/categories?post=17199"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fm-connect1.fortmindz.in\/wp-ogc\/wp-json\/wp\/v2\/tags?post=17199"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}