{"id":17207,"date":"2022-11-02T12:41:36","date_gmt":"2022-11-02T12:41:36","guid":{"rendered":"https:\/\/www.ogc.org\/news\/ogc-seeks-to-retire-ogc-moving-features-encoding-extension-json-best-practice-public-comment-sought\/"},"modified":"2022-11-02T12:41:36","modified_gmt":"2022-11-02T12:41:36","slug":"ogc-seeks-to-retire-ogc-moving-features-encoding-extension-json-best-practice-public-comment-sought","status":"publish","type":"post","link":"https:\/\/fm-connect1.fortmindz.in\/wp-ogc\/announcement\/ogc-seeks-to-retire-ogc-moving-features-encoding-extension-json-best-practice-public-comment-sought\/","title":{"rendered":"OGC Seeks to Retire OGC Moving Features Encoding Extension – JSON Best Practice; Public Comment Sought"},"content":{"rendered":"

Superseded Best Practice Document will be retired to ensure consistency in implementation.<\/em><\/p>\n

The Open Geospatial Consortium (OGC) Moving Features Standards Working Group (SWG) has recommended that the OGC Best Practice OGC Moving Features Encoding Extension – JSON<\/a> (16-140r1) document be retired. The document has been superseded by the OGC Moving Features Encoding Extension – JSON Standard (19-045r3). Public Comment on the retirement is sought. Comments are due by January 2, 2023.<\/strong><\/p>\n

The OGC Moving Features SWG has been actively developing Standards and practices for representing the movement of geographically-tied features. These Standards have built upon the ISO 19141:2008 – Schema for moving features<\/a> Standard to provide practical implementation guidance for managing moving feature data.<\/p>\n

The initial Moving Features encoding was standardized in XML. Further work resulted in a Standardized encoding in comma-separated values (CSV). In keeping with sound methodology, the community developing these Standards worked with real and proven implementations before finalizing the Standards. As such, the SWG published a Best Practice document detailing how moving feature data can be encoded in JSON. This Best Practice formed the basis for further work to standardize a JSON encoding: the OGC Moving Features Encoding Extension – JSON Standard<\/a>.<\/p>\n

Now that the JSON encoding is realized as a formal Standard, OGC wishes to retire the out-of-date Best Practice document to ensure that the community is encoding this JSON information in a consistent fashion.<\/p>\n

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

OGC requests that anyone implementing the JSON encoding for moving feature data confirm that they are using the Standard and provide any comments that support or raise concern with retirement of the Best Practice encoding.<\/strong><\/em><\/p>\n

Comments are due by January 2, 2023, and should be submitted via the method outlined on the OGC Moving Features Encoding Extension – JSON Best Practice retirement public comment request page<\/a>.<\/em><\/p>\n

About OGC<\/strong>
\nThe Open Geospatial Consortium (OGC) is a collective problem-solving community of more than 550 experts representing industry, government, research and academia, collaborating to make geospatial (location) information and services FAIR – Findable, Accessible, Interoperable, and Reusable.
\nThe global OGC Community engages in a mix of activities related to location-based technologies: developing consensus-based open standards and best-practices; collaborating on problem solving in agile innovation initiatives; participating in member meetings, events, and workshops; and more.
\nOGC’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.
\nOGC 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.
\nVisit ogc.org<\/a> for more info on our work.<\/p>\n

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

Superseded Best Practice Document will be retired to ensure consistency in implementation.<\/p>\n","protected":false},"author":1,"featured_media":18003,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_eb_attr":"","footnotes":""},"categories":[169],"tags":[263,244,264,174],"class_list":["post-17207","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-announcement","tag-best-practice","tag-json","tag-moving-features","tag-ogc-apis"],"acf":[],"_links":{"self":[{"href":"https:\/\/fm-connect1.fortmindz.in\/wp-ogc\/wp-json\/wp\/v2\/posts\/17207","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=17207"}],"version-history":[{"count":0,"href":"https:\/\/fm-connect1.fortmindz.in\/wp-ogc\/wp-json\/wp\/v2\/posts\/17207\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/fm-connect1.fortmindz.in\/wp-ogc\/wp-json\/wp\/v2\/media\/18003"}],"wp:attachment":[{"href":"https:\/\/fm-connect1.fortmindz.in\/wp-ogc\/wp-json\/wp\/v2\/media?parent=17207"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fm-connect1.fortmindz.in\/wp-ogc\/wp-json\/wp\/v2\/categories?post=17207"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fm-connect1.fortmindz.in\/wp-ogc\/wp-json\/wp\/v2\/tags?post=17207"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}