On Fri, Sep 23, 2022 at 6:00 PM Ian Turton <ijtur...@gmail.com> wrote:
> GeoJSON is required to be in 4326 by the specification, we have just come > into conformance with that standard. I don't think there is any way to > force it back to the old way. > Hmm... that aspect of the specification is broken for several applications (the ones in need of centimetric+ accuracy, due to the uncertainty of WGS84 epoch). OGC API Features opted for the prior arrangement <https://docs.ogc.org/is/18-058/18-058.html#_features_and_feature_resources> clause and have set up a working group for GeoJSON extensions that will break it free of such limitations <https://portal.ogc.org/files/95319#_business_value_proposition>. On a practical note, I believe GeoServer should allow for choice, maybe driven by the mime type: - if the "application/geo+json" official mime type is used, maybe be strict and generate RFC compliant GeoJSON - if "application/json" is used instead, generate pre-RFC GeoJSON with native CRS and the CRS attribute Cheers Andrea == GeoServer Professional Services from the experts! Visit http://bit.ly/gs-services-us for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions Group phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 https://www.geosolutionsgroup.com/ http://twitter.com/geosolutions_it ------------------------------------------------------- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail
_______________________________________________ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
