org.geoserver.wcs.DefaultWebCoverageService100.computeIntersectionEnvelop(GeneralEnvelope requestedEnvelope, GeneralEnvelope nativeEnvelope) returns correctly computed intersection for below case:
 |
 |
|---|
However, org.geoserver.wcs.DefaultWebCoverageService100.computeIntersectionEnvelop(GeneralEnvelope requestedEnvelope, GeneralEnvelope nativeEnvelope) returns NULL for below envelopes.
 |
 |
|---|
The first envelope was created from WPS post request with below envelope information:
<ns1:Envelope srsName=“EPSG:4326”>
<gml:pos xmlns:gml=“http://www.opengis.net/gml”>-168.075 12.925</gml:pos>
<gml:pos xmlns:gml=“http://www.opengis.net/gml”>-149.925 31.075</gml:pos>
</ns1:Envelope>
The second envelope was created from WPS post request with below envelope information:
<ns1:Envelope srsName=“EPSG:4326”>
<gml:pos xmlns:gml=“http://www.opengis.net/gml”>191.925 12.925</gml:pos>
<gml:pos xmlns:gml=“http://www.opengis.net/gml”>210.075 31.075</gml:pos>
</ns1:Envelope>
For both cases, the requestedEnvelope references the same area. The only difference is that one is in [-180:180] format and the other is in [0:360] format for longitudes.
Is this known issue? Or is the requestedEnvelope in second case incorrectly created and should be using some other CRS?
–
Joseph Shin
We are what we repeatedly do. Excellence then is not an act but a habit.