hi Nuno.
your schema DID HELP, the output is correct now!
I don't remember why I deactivated the import of gml Schema months ago.
Anyway its working now.
Thanks a lot, I really had come to an end with searching for the error.
Happy greetings and do stay healthy!
Christine
Am 23.03.2020 um 19:45 schrieb Nuno Oliveira:
Hi,
if GeoServer is capable of producing the correct GeoJSON output and
use WMS it means that it's the XML encoding that's failing, probably
because some GML type binding is not being recognized.
I did a few changes on your schema, could you give a try using:
<!--Generated by Enterprise Architect 13.5.1351 ( Build: 1351 )-->
<xs:schema elementFormDefault="qualified"
targetNamespace="http://geoserver.org/xe" version = "2.03"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:xe="http://geoserver.org/xe"
xmlns:gml="http://www.opengis.net/gml/3.2">
<http://www.opengis.net/gml/3.2>;
<xs:import namespace="http://www.opengis.net/gml/3.2"
schemaLocation="http://schemas.opengis.net/gml/3.2.1/gml.xsd" />
<xs:element name="XE_OrtVonInteresse"
type="xe:XE_OrtVonInteresseType"
substitutionGroup="gml:AbstractFeature" />
<xs:complexType name="XE_OrtVonInteresseType" abstract="true">
<xs:complexContent>
<xs:extension base="gml:AbstractFeatureType">
<xs:sequence>
<xs:element name="ovi_id" type="xs:integer"/>
<xs:element name="objektUUID" type="xs:string"/>
<xs:element name="objektName" type="xs:string"/>
<xs:element name="lageanfasspunkt"
type="gml:GeometryPropertyType" minOccurs="1" maxOccurs="1"/>
<xs:element name="objektFunktion" type="xs:string"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:element name="XE_Aussichtspunkt"
type="xe:XE_AussichtspunktType"
substitutionGroup="xe:XE_OrtVonInteresse"/>
<xs:complexType name="XE_AussichtspunktType">
<xs:complexContent>
<xs:extension base="xe:XE_OrtVonInteresseType">
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:schema>
If the schema changes above don't make it work, can you give it a try
whit this mapping for the geometry (instead of the one you are using)?
<AttributeMapping>
<targetAttribute>xe:lageanfasspunkt</targetAttribute>
<sourceExpression>
<OCQL>lageanfasspunkt</OCQL>
</sourceExpression>
</AttributeMapping>
If none of the above work, then I'm afraid this will need to be debugged.
Hope it helps,
Nuno Oliveira
On Sun, 2020-03-22 at 18:53 +0100, Christine Andrae wrote:
Hello,
I have problems trying to serve a complex feature schema via Application
Schema Extension with geoserver.
All feature attributes are built correctly with exception of the
geometry column. This results in an empty tag in the GML 3.x-Output.
However, geoserver is able to produce a correct wms output or to serve
the geometric data as GeoJSON.
After spending days trying all sorts of changes I finally made a
stackoverflow-request.
https://gis.stackexchange.com/questions/354759/geoserver-application-schema-gml-output-without-geometry
Is anybody able to help?
Thank you
Christine
_______________________________________________
Geoserver-users mailing list
Please make sure you read the following two resources before posting to this
list:
- Earning your support instead of buying it, but Ian
Turton:http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting
guidelines:http://geoserver.org/comm/userlist-guidelines.html
If you want to request a feature or an improvement, also see
this:https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
[email protected]
<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/geoserver-users
--
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
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
-------------------------------------------------------
Con riferimento alla normativa sul trattamento dei dati
personali (Reg. UE 2016/679 - Regolamento generale sulla
protezione dei dati “GDPR”), si precisa che ogni
circostanza inerente alla presente email (il suo contenuto,
gli eventuali allegati, etc.) è un dato la cui conoscenza
è riservata al/i solo/i destinatario/i indicati dallo
scrivente. Se il messaggio Le è giunto per errore, è
tenuta/o a cancellarlo, ogni altra operazione è illecita.
Le sarei comunque grato se potesse darmene notizia.
This email is intended only for the person or entity to
which it is addressed and may contain information that
is privileged, confidential or otherwise protected from
disclosure. We remind that - as provided by European
Regulation 2016/679 “GDPR” - copying, dissemination or
use of this e-mail or the information herein by anyone
other than the intended recipient is prohibited. If you
have received this email by mistake, please notify
us immediately by telephone or e-mail.
_______________________________________________
Geoserver-users mailing list
Please make sure you read the following two resources before posting to this
list:
- Earning your support instead of buying it, but Ian Turton:
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines:
http://geoserver.org/comm/userlist-guidelines.html
If you want to request a feature or an improvement, also see this:
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users