Jody Garnett (
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Ae422bb7f-4808-47e3-837f-13db0e6681e3
) *created* an issue
GeoServer (
https://osgeo-org.atlassian.net/browse/GEOS?atlOrigin=eyJpIjoiNGI3MjE4N2M2MTE2NDE5NmJmN2Y5NjA1ZjJkMTJkOTgiLCJwIjoiaiJ9
) / Bug (
https://osgeo-org.atlassian.net/browse/GEOS-11033?atlOrigin=eyJpIjoiNGI3MjE4N2M2MTE2NDE5NmJmN2Y5NjA1ZjJkMTJkOTgiLCJwIjoiaiJ9
) GEOS-11033 (
https://osgeo-org.atlassian.net/browse/GEOS-11033?atlOrigin=eyJpIjoiNGI3MjE4N2M2MTE2NDE5NmJmN2Y5NjA1ZjJkMTJkOTgiLCJwIjoiaiJ9
) REST API coverage.xml regression on handling of invalid ReferencedEnvelope (
https://osgeo-org.atlassian.net/browse/GEOS-11033?atlOrigin=eyJpIjoiNGI3MjE4N2M2MTE2NDE5NmJmN2Y5NjA1ZjJkMTJkOTgiLCJwIjoiaiJ9
)
Issue Type: Bug Affects Versions: 2.22.2 Assignee: Unassigned Components: REST
Created: 16/Jun/23 11:32 AM Priority: Medium Reporter: Jody Garnett (
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Ae422bb7f-4808-47e3-837f-13db0e6681e3
)
Using a REST API script using a weakly typed language the difference between a
string and an int resulted in a coverage.xml POST with following invalid
ReferencedEnvelope crs:
<crs>0</crs>
In GeoServer 2.21.4 this was preserved:
<coverage>
<name>ijssel_2017_dsm_5</name>
<title>ijssel_2017_dsm_5</title>
...
<nativeCRS class="projected">...</nativeCRS>
<srs>EPSG:28992</srs>
<projectionPolicy>FORCE_DECLARED</projectionPolicy>
<nativeBoundingBox>
<minx>180000</minx>
<miny>437500</miny>
<maxx>215000</maxx>
<maxy>512500</maxy>
<crs>0</crs>
</nativeBoundingBox>
<latLonBoundingBox>
<minx>5.7511379908659</minx>
<miny>51.9236999711892</miny>
<maxx>6.27331655234198</maxx>
<maxy>52.6005228787716</maxy>
<crs>0</crs>
</latLonBoundingBox>
In newer releases (GeoServer 2.24.x and 2.23.0, … GeoServer 2.22.2?) the
ReferencedEnvelopes having no crs:
<nativeCRS class="projected">...</nativeCRS>
<srs>EPSG:28992</srs>
<nativeBoundingBox>
<minx>180000</minx>
<miny>437500</miny>
<maxx>215000</maxx>
<maxy>512500</maxy>
</nativeBoundingBox>
<latLonBoundingBox>
<minx>5.7511379908659</minx>
<miny>51.9236999711892</miny>
<maxx>6.27331655234198</maxx>
<maxy>52.6005228787716</maxy>
</latLonBoundingBox>
While this does not look like a significant change … select WCS operations have
trouble:
* WCS 1.0.x DescribeCoverage is fine
* WCS 1.1.x DescribeCoverage has a translate error
* WCS 2.0.x DescribeCoverage has a translate error
java.lang.NullPointerException: Cannot invoke
"org.opengis.referencing.crs.CoordinateReferenceSystem.getCoordinateSystem()"
because "crs" is null
javax.xml.transform.TransformerException: Translator error
Translator error
Unexpected error occurred during describe coverage xml encoding
java.lang.NullPointerException: Cannot invoke
"org.opengis.referencing.crs.CoordinateReferenceSystem.getCoordinateSystem()"
because "crs" is null
Cannot invoke
"org.opengis.referencing.crs.CoordinateReferenceSystem.getCoordinateSystem()"
because "crs" is null
I can only assume that some WCS code paths are ignoring the coverage.xml
<srs>EPSG:28992</srs> setting and trusting the native information to be correct
and available.
(
https://osgeo-org.atlassian.net/browse/GEOS-11033#add-comment?atlOrigin=eyJpIjoiNGI3MjE4N2M2MTE2NDE5NmJmN2Y5NjA1ZjJkMTJkOTgiLCJwIjoiaiJ9
) Add Comment (
https://osgeo-org.atlassian.net/browse/GEOS-11033#add-comment?atlOrigin=eyJpIjoiNGI3MjE4N2M2MTE2NDE5NmJmN2Y5NjA1ZjJkMTJkOTgiLCJwIjoiaiJ9
)
Get Jira notifications on your phone! Download the Jira Cloud app for Android (
https://play.google.com/store/apps/details?id=com.atlassian.android.jira.core&referrer=utm_source%3DNotificationLink%26utm_medium%3DEmail
) or iOS (
https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailNotificationLink&mt=8
) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100227-
sha1:5147d46 )
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
