It's hard to define an envelope for a circular projection, and an oblique one
is even more difficult, because either the top or bottom point is not the
max/min lat depending on what lat_0 is for the projection.
The (projection specific) right answer here is to inverse project the following
points:
(xmin,0)(xmax,0) -> lonmin, lonmax.
(0,ymin)(0ymax) -> latmin, latmax.
Then correct:
if lat_0 > 0
latmax = 90
elsif lat_0 < 0
latmin = -90
# implied else lat_0 == 0 don't do anything
This is about as good a description as you may get. However, in any oblique
situation it actual has a lon range of (-180,180) near the pole. Whether that
matters or not... I don't know. I'd need to know more of what decisions are
made based on the envelope.
... and then I never really thought much about what happens when the coverage
layer isn't full disk. I guess you'd have to make determine if it contains the
pole or not... which would be complicated.
I like the idea of prompting the user for manual entry when a try/catch fails.
I have no idea how to do that, though. I'll look into it.
Thanks,
Judd
Judd Taylor | Orbital Systems LLC | CPI Antenna Systems Division
3807 Carbon Road · Irving, TX · 75038 · USA
P: 972-915-3669 ext 127 · E:
[email protected]<mailto:[email protected]> · W
<http://www.orbitalsystems.com>
www.orbitalsystems.com<mailto:[email protected]>
[http://www.orbitalsystems.com/logo/CPI_ASD.png][http://www.orbitalsystems.com/logo/Orbital.png]
________________________________
From: Andrea Aime [[email protected]]
Sent: Thursday, November 01, 2018 5:02 AM
To: Judd Taylor
Cc: GeoServer Mailing List List
Subject: Re: [Geoserver-users] Orthographic Coverage Layer
On Mon, Oct 22, 2018 at 4:03 PM Judd Taylor
<[email protected]<mailto:[email protected]>> wrote:
But if the fix is going to be something projection specific, I feel like I need
to know better about what the purpose of this Envelope is to begin with.
Looking at your report at https://osgeo-org.atlassian.net/browse/GEOS-8979
(thanks for filling it), you have a stack trace and are already looking at
the code and making suggestions about it, so you coud backtrace a few methods
in the trace, see where it's being called and figure out why.
Doing it shows that the call in question is happening to fill the "lat/lon
bounding box", which is mandatory in most OGC protocols and
has always to be filled when configuring a layer.
Given the use case, I believe you could guard that section in the catalog
builder with a try/catch, log a warning, and have the user fill that information
by hand instead. This would be an acceptable patch (reminder, the patch must
come with a test).
However, you might still stumble in reprojection issues later down the road,
the method I've indicated in the previous mails is still the place
where on can make a "general fix"
Cheers
Andrea
==
GeoServer Professional Services from the experts! Visit http://goo.gl/it488V
for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions
S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) phone: +39 0584 962313 fax:
+39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
![http://www.orbitalsystems.com/logo/CPI_ASD.png][http://www.orbitalsystems.com/logo/Orbital.png](http://www.orbitalsystems.com/logo/CPI_ASD.png][http://www.orbitalsystems.com/logo/Orbital.png){kind=link}