On Thu, May 20, 2010 at 4:07 PM, Jody Garnett <jody.garn...@gmail.com> wrote:
> I am not sure I get it what are we trying to do with this change?
Well at the moment, when you parse getCapabilities responses and have
layers with dimensions and dimension extents, for example:
<wms:Layer>
<wms:Name>hydro.runoffmaxaverage</wms:Name>
<wms:Title>Average maximum runoff</wms:Title>
<wms:CRS>EPSG:2393</wms:CRS>
<wms:EX_GeographicBoundingBox>
<wms:westBoundLongitude>19.872</wms:westBoundLongitude>
<wms:eastBoundLongitude>33.030</wms:eastBoundLongitude>
<wms:southBoundLatitude>59.769</wms:southBoundLatitude>
<wms:northBoundLatitude>69.995</wms:northBoundLatitude>
</wms:EX_GeographicBoundingBox>
<wms:Dimension name="time" units="ISO8601">
2025-01-01/2055-01-01/2085-01-01
</wms:Dimension>
<wms:Dimension name="emissionscenario" units="WHAT">
SRES_A1FI,SRES_A2,SRES_B1,SRES_B2
</wms:Dimension>
</wms:Layer>
There isn't a way to get the data ( extent ) from the dimension.
That happens because when we parse getCapabilitiesResponse and parser
calls DimensionType's getValue, it passes handling extents to
Extent.java AND includes extent to the dimension only if extent is not
empty.
As current implementation of isEmpty is not compatible with the
definition of empty, Dimension's extents are not put into the object
graph -- even though they are in the xml and are otherwise parsed
correctly.
> Also which extent class are you wanting this change done to?
> The reason I ask is no modules really depend on the wms module so they are
> not going to take kindly to extending org.geotools.data.wms.xml.Extent.
org.geotools.data.wms.xml.Extent is the class where the problem is. We
just extended geotools' Extent class in our project to fix this bug
untill it is fixed in the upstream.
-huima
------------------------------------------------------------------------------
_______________________________________________
Geotools-devel mailing list
Geotools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
