I solved my own problem. It was due to the fact that my workspace URI wasn't
set to match the URI specified in my data store and mapping file.
Thanks,
Danny
From: Danny Cheng
Sent: Monday, September 22, 2014 12:00 PM
To: [email protected]
Subject: Complex Feature; Feature Type
Hi Everyone:
I have 2 simple features setup inside my PostgreSQL database and I am trying to
follow the app schema tutorial
(http://docs.geoserver.org/stable/en/user/data/app-schema/tutorial.html) to
convert them into a complex feature. I modified datastore.xml and added a
mapping file, but when I try to get the feature through WFS request, it tells
me that <namespace>:<feature> is unknown.
Does my new complex feature have to use the same name as the simple feature?
Right now I have simple feature A and B, and I'm trying to make a complex
feature C from A and B. The unknown feature type error occurs when I try to
send a WFS get request for <namespace>:C.
I defined my complex feature C in the mapping file as follows.
<targetTypes>
<FeatureType>
<schemaUri>http://www.geosciml.org/geosciml/2.0/xsd/geosciml.xsd</schemaUri<http://www.geosciml.org/geosciml/2.0/xsd/geosciml.xsd%3c/schemaUri>>
</FeatureType>
</targetTypes>
<typeMappings>
<FeatureTypeMapping>
<sourceDataStore>datastore</sourceDataStore>
<sourceType>A</sourceType>
<targetElement>namespace:C</targetElement>
<attributeMappings>
<AttributeMapping>
<targetAttribute>namespace:C</targetAttribute>
<idExpression>
<OCQL>fid</OCQL>
</idExpression>
</AttributeMapping>
<AttributeMapping>
<targetAttribute>gml:name[1]</targetAttribute>
<sourceExpression>
<OCQL>filename</OCQL>
</sourceExpression>
</AttributeMapping>
<AttributeMapping>
<targetAttribute>gml:name[2]</targetAttribute>
<sourceExpression>
<OCQL>description</OCQL>
</sourceExpression>
</AttributeMapping>
</attributeMappings>
</FeatureTypeMapping>
</typeMappings>
Thanks,
Danny
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
