Good evening,
I have also stumbled into probably the same issue trying to build a layer
spanning across the dateline seamlessly. If this is not related, please
correct me. I do not possess any Java skills to spot the bug in code neither
fix it and therefore tried to document what I have tried on GeoServer side -
to no success so far.
https://osgeo-org.atlassian.net/browse/GEOS-9059
(https://osgeo-org.atlassian.net/browse/GEOS-9059)
It could be used as a steppingstone for someone later.
Best,
Lubomír Bucek
---------- Původní e-mail ----------
Od: Phil Scadden <[email protected]>
Komu: GeoServer Mailing List List <[email protected]>
Datum: 13. 12. 2018 0:00:41
Předmět: Re: [Geoserver-users] Imagemosaic spanning the dateline
"
Any insight at all into the warning message would help. (Like what was code
trying to do when it generated it).
From: Phil Scadden <[email protected]>
Sent: Tuesday, 11 December 2018 10:06
To: GeoServer Mailing List List <[email protected]>
Subject: Re: [Geoserver-users] Imagemosaic spanning the dateline
After a bit of battle getting disk provisioning, I have now successfully
built an imagemozaic in EPSG:3857 which does cover both sides of the
dateline. If I use “tiled” in getmap requests, it returns imagery for one
side the dateline – if dateline is not in frame, you can get imagery for
either side, but moment you have datetime in frame, then you get one side or
other. I am about to analyse the getmap requests buts when I look in the
logs, I see it is full of WARN message like this:
2018-12-11 09:52:09,214 WARN [lite.gridcoverage2d] - Could not reduce the
grid geometry inside the valid area bounds: ReferencedEnvelope[-
1.7976931348623157E308 : 1.7976931348623157E308, -85.0 : 85.0]
Grid geometry isGridGeometry2D[GridEnvelope2D[0..1063, 0..1063], PARAM_MT[
"Affine",
PARAMETER["num_row", 3],
PARAMETER["num_col", 3],
PARAMETER["elt_0_0", 9.554628534313876],
PARAMETER["elt_0_2", 19841652.786989305],
PARAMETER["elt_1_1", -9.554628534317445],
PARAMETER["elt_1_2", -4118861.8190303175]]]
The messages vary in terms of the elt_ parameters and the GridEnvelope2D
content, but ALWAYS have ReferencedEnvelope[-1.7976931348623157E308 :
1.7976931348623157E308, -85.0 : 85.0]
The lat/long bounding box on the layer is -179.999999 -60.23
179.999999999999 -19.3111
Can anyone tell me what the WARN message is about? (or should I give up now
and create 2 imagemozaics, one for each side of the dateline).
From: Phil Scadden <[email protected](mailto:[email protected])>
Sent: Monday, 29 October 2018 16:21
Cc: GeoServer Mailing List List <[email protected]
(mailto:[email protected])>
Subject: Re: [Geoserver-users] Imagemosaic spanning the dateline
That is encouraging. Trying it if I can figure the REST. While there is no
accounting for some random consumer might request, any sensible query isn’t
going to ask for the raster in anything but 3857 and it would make no sense
outside SW Pacific.
From: Andrea Aime <[email protected]
(mailto:[email protected])>
Sent: Sunday, 28 October 2018 05:59
To: Phil Scadden <[email protected](mailto:[email protected])>
Cc: GeoServer Mailing List List <[email protected]
(mailto:[email protected])>
Subject: Re: [Geoserver-users] Imagemosaic spanning the dateline
Hi Phil,
we have done that in the past, even with granules spanning the dateline,
using a heterogeneous CRS
setup (each image in its own UTM zone, the ones crossing the dateline in UTM
1 or 60).
That said, it's always tricky, so I won't promise it will work in your case.
Having the source CRS in 3857, that will surely be source of troubles if
someone asks the map in output
in 4326, last time I stumbled in that case if the client asked for the
entire globe to be displayed in 4326
the envelope reprojection would fail
Cheers
Andrea
On Fri, Oct 26, 2018 at 2:35 AM Phil Scadden <[email protected]
(mailto:[email protected])> wrote:
"
Before I waste a lot of time on something impossible, I thought I would ask
whether it is okay to have an image mosaic that crosses the dateline. None
of the granules cross the 180 (more accurately, the data is split into tiles
that don’t cross the 180), but the mosaic itself will span a big hunk of the
SW Pacific. CRS is 3857 for each tile. The reason I ask is the LL, UR
coordinates for an envelope2d would violate the common assumption that LL x
is < LR x that flat-earthers are so used to.
Notice: This email and any attachments are confidential and may not be
used, published or redistributed without the prior written consent of the
Institute of Geological and Nuclear Sciences Limited (GNS Science). If
received in error please destroy and immediately notify GNS Science. Do not
copy or disclose the contents.
_______________________________________________
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#/
(http://www.ianturton.com/talks/foss4g.html#/)
- The GeoServer user list posting guidelines: http://geoserver.org/comm/
userlist-guidelines.html(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
(https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer)
[email protected]
(mailto:[email protected])
https://lists.sourceforge.net/lists/listinfo/geoserver-users
(https://lists.sourceforge.net/lists/listinfo/geoserver-users)
"
--
Regards, Andrea Aime == GeoServer Professional Services from the experts!
Visit http://goo.gl/it488V(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://www.geo-solutions.it) http://twitter.com/geosolutions_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.
Notice: This email and any attachments are confidential and may not be
used, published or redistributed without the prior written consent of the
Institute of Geological and Nuclear Sciences Limited (GNS Science). If
received in error please destroy and immediately notify GNS Science. Do not
copy or disclose the contents.
Notice: This email and any attachments are confidential and may not be
used, published or redistributed without the prior written consent of the
Institute of Geological and Nuclear Sciences Limited (GNS Science). If
received in error please destroy and immediately notify GNS Science. Do not
copy or disclose the contents.
Notice: This email and any attachments are confidential and may not be
used, published or redistributed without the prior written consent of the
Institute of Geological and Nuclear Sciences Limited (GNS Science). If
received in error please destroy and immediately notify GNS Science. Do
not copy or disclose the contents.
_______________________________________________
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
"
_______________________________________________
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
