[Geoserver-devel] GSIP 219: Multiple CRS authority support, planetary CRS

Andrea_Aime4 · May 3, 2023, 10:13am

Hi all,
the following proposal aims to add support for authorities other than EPSG
in selected parts of GeoServer, and provide a working example based on the
IAU authority (planetary CRSs).

https://github.com/geoserver/geoserver/wiki/GSIP-219

Key points:

It’s not trying to address all places where EPSG authority assumptions are made, but provides a specific list instead. Other cases can be handled later as bug fixes, as funding comes to fix those as well.
Discusses a couple of way to plug in other authorities (can you suggest more/better ones?).
Feedbacks/votes welcomed!

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

ianturton · May 3, 2023, 11:19am

I assume that some/much of this work will be in the GeoTools tree?

As for how to package this on the one hand I like the simplicity of a new extension, it’s easy for users to understand and provides a good way to keep track of versions, on the other hand it’s easy to forget to add it on upgrade and break all your layers. Just thinking aloud here, how much effort would it be to get the existing authority discovery code (or are they hard coded) to “discover” new authorities by looking in a “well known” location?

Anyway +1 for the general plan, looking forward to seeing the details

Ian

···

Ian Turton

Andrea_Aime4 · May 3, 2023, 12:07pm

I assume that some/much of this work will be in the GeoTools tree?

It’s evenly split between GeoTools and GeoServer.

As for how to package this on the one hand I like the simplicity of a new extension, it’s easy for users to understand and provides a good way to keep track of versions, on the other hand it’s easy to forget to add it on upgrade and break all your layers. Just thinking aloud here, how much effort would it be to get the existing authority discovery code (or are they hard coded) to “discover” new authorities by looking in a “well known” location?

SPIs tend to be hard-coded, you can have only one instance of each class registered, which tends to favour
an approach based on modules, each one having its WKT authority factory subclass.
What I may be able to do get away with, in order to support files discovered in the data directory, is to use
bytecode engineering to create the new subclasses on the fly.

Anyway +1 for the general plan, looking forward to seeing the details

90% of it is really going to be specific bug fixes in the places making the EPSG assumptions,
I have a laundry list of things and will likely discover more as I work on it (hence the strict scope control,
I have a contract backing this, not a charity).

The only truly new bit will be the support for the IAU authority.
That said, as a “thing” it’s big enough that I thought I would write a proposal anyways.

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

Nuno_Oliveira1 · May 3, 2023, 9:26pm

+0

···

Regards,

Nuno Oliveira

==
GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information.

Nuno Miguel Carvalho Oliveira
@nmcoliveira
Technical Lead / Project Manager

GeoSolutions Group
phone: +39 0584 962313
fax: +39 0584 1660272

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.

jive · May 4, 2023, 2:01am

+1

The proposal has EPSG as the defacto spatial reference system authority, we also have CRS and AUTO somewhere in the mix …

The proposal identifies a number of areas that will be included in scope; one I was interested in was not covered. The ability to limit the srs published by WMS is a common configuration - although not in scope I assume it could be covered by allowing: IAU2000:49900,IAU2000:49901

I honestly do not know how it works for the top-level srs list if there are a mix of earth layers and planetary layers in a WMS - perhaps it should be empty?

Thanks for the proposed improvement,
Jody

···

–
Jody Garnett

Andrea_Aime4 · May 4, 2023, 7:00am

+1

The proposal has EPSG as the defacto spatial reference system authority, we also have CRS and AUTO somewhere in the mix …

Correct, although they only work in specific use cases.

The proposal identifies a number of areas that will be included in scope; one I was interested in was not covered. The ability to limit the srs published by WMS is a common configuration - although not in scope I assume it could be covered by allowing: IAU2000:49900,IAU2000:49901

It’s not in scope, but I will try to sneak it in, if I manage to work below the allocated timebox. No promises though.

I honestly do not know how it works for the top-level srs list if there are a mix of earth layers and planetary layers in a WMS - perhaps it should be empty?

Not really… we already have plenty of incompatible combinations by mixing local and global SRSs, that will fail if tried. Testing what’s compatible
would make the time for generating the caps balloon, but also, the area of definition of SRSs is going to be missing from WKT based systems,
and when available is useful only from a bureaucratic point of view, it’s often way too tight for cross-border projects.

Long story short, behavior will be just like now, GeoServer is going to list what it has, and will eventually fail if an incompatible mix is chosen.

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

jive · May 4, 2023, 4:46pm

The proposal identifies a number of areas that will be included in scope; one I was interested in was not covered. The ability to limit the srs published by WMS is a common configuration - although not in scope I assume it could be covered by allowing: IAU2000:49900,IAU2000:49901

It’s not in scope, but I will try to sneak it in, if I manage to work below the allocated timebox. No promises though.

Clarification: I am not trying to put it in scope; just understand if we have a decent plan in mind if capacity shows up in the future

I honestly do not know how it works for the top-level srs list if there are a mix of earth layers and planetary layers in a WMS - perhaps it should be empty?

Not really… we already have plenty of incompatible combinations by mixing local and global SRSs, that will fail if tried. Testing what’s compatible
would make the time for generating the caps balloon, but also, the area of definition of SRSs is going to be missing from WKT based systems,
and when available is useful only from a bureaucratic point of view, it’s often way too tight for cross-border projects.

Cool; as above - just trying to understand how it fits together. It could be that these layers would be best handled as a virtual web service (if we really need accurately restricted capabilities).

Cheers,
Jody

Andrea_Aime4 · May 5, 2023, 10:12am

Ok. I’ll try to sneak it anyways, if I can

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