Changes between Version 3 and Version 4 of NERCGeoServer


Ignore:
Timestamp:
16/04/08 17:38:19 (11 years ago)
Author:
ashaon
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • NERCGeoServer

    v3 v4  
    77== Serving up CSML PointSeriesFeature through GeoServer == 
    88 
    9 CSML PointSeriesFeature uses the XML List element to represent a series of point measurements.  The current version of “Complex DataStore” Geoserver (available on GeoServer subversion code base at [https://svn.codehaus.org/geoserver/branches/1.6.x]) does not support mapping data to XML List element.  Therefore, in order to accurately generate CSML through GeoServer, it was crucial to implement a mechanism for mapping to XML List elements in GeoServer. The approach used for this is essentially a variant of the one used for mapping to "Multiple Occurrence" elements in the current version of “Complex DataStore” Geoserver.  The only difference is that the values to be mapped are concatenated together (delimited with a space character) and treated as a single value. So, when it comes to mapping to the element in question, there is only one value to be mapped, which essentially yields a single occurrence of the element in the final XML output. Implementations of both of these features are mainly done in the ''GroupingFeatureIterator3'' class of ''org.geotools.data.complex'' package.  Listing 1 illustrates the difference between these implementations. 
     9CSML PointSeriesFeature uses the XML List element to represent a series of point measurements.  However, the current version of “Complex DataStore” Geoserver (available on GeoServer subversion code base at [https://svn.codehaus.org/geoserver/branches/1.6.x]) does not support mapping data to XML List element.  Therefore, in order to accurately generate CSML through GeoServer, it was crucial to implement a mechanism for mapping to XML List elements in GeoServer. The approach used for this is essentially a variant of the one used for mapping to "Multiple Occurrence" elements in the current version of “Complex DataStore” Geoserver.  The only difference is that the values to be mapped are concatenated together (delimited with a space character) and treated as a single value. So, when it comes to mapping to the element in question, there is only one value to be mapped, which essentially yields a single occurrence of the element in the final XML output. Implementations of both of these features are mainly done in the ''GroupingFeatureIterator3'' class of ''org.geotools.data.complex'' package.  Listing 1 illustrates the difference between these implementations. 
    1010 
    1111