Hi,I have a doubt regarding the way GML complex features encoder handles a sub collection of features, i.e. chained features.
The example use case is the representation of some meteorological stations measurements in GML. The complex feature represents a station were the measurements are represented as a sub collection of features. The XML expected representation
would be something like this:
<?xml version="1.0" encoding="UTF-8"?>
<wfs:FeatureCollection ...>
<st:featureMember>
<st:StationFeature gml:id="1">
<st:name>station 1</st:name>
<st:contact>
<st:mail>stati...@mail.com</st:mail>
</st:contact>
<st:measurement>
<st:name>temp</st:name>
<st:unit>c</st:unit>
<st:value>35.5</st:value>
</st:measurement>
<st:measurement>
<st:name>wind</st:name>
<st:unit>km/h</st:unit>
<st:value>110.5</st:value>
</st:measurement>
<st:geometry>
<gml:Point
srsName="http://www.opengis.net/gml/srs/epsg.xml#4326";>
<gml:coordinates>50.0,60.0</gml:coordinates>
</gml:Point>
</st:geometry>
</st:StationFeature>
</gml:featureMember>
</wfs:FeatureCollection>
The first GML based schema I wrote for this didn't work, i.e. the
measurements sub collection was not encoded by
the encoder, please find that schema attached with name stations1.xsd.
After some investigation I found that my
problem was in this piece of code: https://github.com/geotools/geotools/blob/master/modules/extension/xsd/xsd-gml3/src/main/java/org/geotools/gml3/bindings/ComplexSupportXSAnyTypeBinding.java#L176-L177Basically no child elements were extracted, and in this case the child elements were the station measurements. After checking the app-schema examples I came up with this second schema that worked, please find that schema attached with name stations2.xsd.
The main difference is that I wrapped the measurement element with the MeasurmentPropertyType:
<xs:complexType name="MeasurementPropertyType">
<xs:sequence minOccurs="0">
<xs:element ref="st:Measurement"/>
</xs:sequence>
<xs:attributeGroup ref="gml:AssociationAttributeGroup"/>
</xs:complexType>
This stations use case is just an example, I have a much more complex
use case with the same problem were I cannot change the schema.
So I'm wondering, did anyone had a similar use case ? did I made
something wrong in the app-schema mappings-file ? is this something is
just not supported by the encoder ? and did my first schema actually
makes sense (in my point of view it looks sane) ?
Any help with this will be very very welcomed :) Regards, Nuno Oliveira -- == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Nuno Miguel Carvalho Oliveira @nmcoliveira Software Engineer GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 333 8128928 http://www.geo-solutions.it http://twitter.com/geosolutions_it ------------------------------------------------------- AVVERTENZE AI SENSI DEL D.Lgs. 196/2003 Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e -mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.The information in this message and/or attachments, is intended solely for the attention and use of
the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.
stations1.xsd
Description: XML document
stations2.xsd
Description: XML document
<?xml version="1.0" encoding="UTF-8"?> <as:AppSchemaDataAccess xmlns:as="http://www.geotools.org/app-schema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://www.geotools.org/app-schema AppSchemaDataAccess.xsd"> <namespaces> <Namespace> <prefix>st</prefix> <uri>http://www.stations.org/1.0</uri> </Namespace> <Namespace> <prefix>gml</prefix> <uri>http://www.opengis.net/gml</uri> </Namespace> </namespaces> <sourceDataStores> <DataStore> <id>data_source</id> <parameters> <Parameter> <name>data_store</name> <value>mongodb://localhost/stations</value> </Parameter> <Parameter> <name>namespace</name> <value>http://www.stations.org/1.0</value> </Parameter> <Parameter> <name>schema_store</name> <value>file:///tmp/9093</value> </Parameter> <Parameter> <name>data_store_type</name> <value>complex</value> </Parameter> </parameters> </DataStore> </sourceDataStores> <targetTypes> <FeatureType> <schemaUri>http://localhost/data/schemas/stations.xsd</schemaUri> </FeatureType> </targetTypes> <typeMappings> <FeatureTypeMapping> <sourceDataStore>data_source</sourceDataStore> <sourceType>stations</sourceType> <targetElement>st:StationFeature</targetElement> <attributeMappings> <AttributeMapping> <targetAttribute> st:StationFeature </targetAttribute> <idExpression> <OCQL>jsonSelect("id")</OCQL> </idExpression> </AttributeMapping> <AttributeMapping> <targetAttribute>st:name</targetAttribute> <sourceExpression> <OCQL>jsonSelect("name")</OCQL> </sourceExpression> </AttributeMapping> <AttributeMapping> <targetAttribute>st:geometry</targetAttribute> <sourceExpression> <OCQL>jsonSelect("geometry")</OCQL> </sourceExpression> </AttributeMapping> <AttributeMapping> <targetAttribute>st:contact/st:mail</targetAttribute> <sourceExpression> <OCQL>jsonSelect("contact.mail")</OCQL> </sourceExpression> <isMultiple>true</isMultiple> </AttributeMapping> <AttributeMapping> <targetAttribute>st:measurement</targetAttribute> <sourceExpression> <OCQL>jsonSelect("id")</OCQL> <linkElement>st:Measurement</linkElement> <linkField>FEATURE_LINK[1]</linkField> </sourceExpression> <isMultiple>true</isMultiple> </AttributeMapping> </attributeMappings> </FeatureTypeMapping> <FeatureTypeMapping> <sourceDataStore>data_source</sourceDataStore> <sourceType>stations</sourceType> <targetElement>st:Measurement</targetElement> <attributeMappings> <AttributeMapping> <targetAttribute> st:Measurement </targetAttribute> <idExpression> <OCQL>jsonSelect("id")</OCQL> </idExpression> </AttributeMapping> <AttributeMapping> <targetAttribute>st:name</targetAttribute> <sourceExpression> <OCQL>jsonSelect("name")</OCQL> </sourceExpression> </AttributeMapping> <AttributeMapping> <targetAttribute>st:unit</targetAttribute> <sourceExpression> <OCQL>jsonSelect("unit")</OCQL> </sourceExpression> </AttributeMapping> <AttributeMapping> <targetAttribute>st:value</targetAttribute> <sourceExpression> <OCQL>jsonSelect("value")</OCQL> </sourceExpression> </AttributeMapping> <AttributeMapping> <targetAttribute>FEATURE_LINK[1]</targetAttribute> <sourceExpression> <OCQL>jsonSelect("id")</OCQL> </sourceExpression> </AttributeMapping> </attributeMappings> </FeatureTypeMapping> </typeMappings> </as:AppSchemaDataAccess>
------------------------------------------------------------------------------ Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today. http://sdm.link/xeonphi
_______________________________________________ GeoTools-Devel mailing list GeoTools-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
