Hi Sebastian, I have worked with app-schema for the INSPIRE directive, serving complex features via WFS usually from PostgreSQL datastore. The experience should be relevant to other AppSchema uses though. The complex feature mapping file I usually start it with HALE Studio and then manually fine tweaking the app-schema mapping file (in Notepad++), to get the fastest/best results from the DB schema.
Once the mapping file gets published to Geoserver you can then request the configured complex features from the server, and Geoserver + AppSchema will generate a file response based on the incoming KVP/POST requests encoded as either GML 3.2 or, but with some issues, GML 3.0 The incoming request may either be a „get entire dataset” (where you get all the features in a complex type), or a „subset” of the dataset (using stored queries filtering or using the GML:ID property). These requests are handled by the WFS getFeature request parameter, and you expect to receive a GML3.2 response containing the configured complex features. Alternatively the incoming request might use a getProperty value, in order to just get a sub-element from the complex features served through the WFS (ex: just the geometry, without all the other nested elements). Geoserver & AppSchema cannot flatten data requested since it can’t solve the complex feature -> simple feature conversion, which implies you are limited in the output formats from the WFS request to either: text/xml or the „cannonical” application/xml+gml32 (no shapefile unfortunately), or json A working example (two protected sites - polygons) of this is available at: http://gmlid.eu/RO/ENV/PADS/WFS/ps/ows?service=WFS&version=2.0.0&request=GetFeature&typeNames=ps:ProtectedSite&outputFormat=json&count=2 I could provide more info if you could provide a clearer picture of what you are trying to achieve. Sorin R. Trimis din Mail pentru Windows 10 De la: worldexplorer Trimis: marți, 11 septembrie 2018 11:27 Către: geoserver-users@lists.sourceforge.net Subiect: [Geoserver-users] Using the app schema with complex features assource Dear list, in the past, I've worked with the app schema tutorial data. Simple features stored in a java properties file which has been converted into complex features for delivery via WFS. Now, my data source has changed. I'm working with complex GML features stored in a GML file which I want to request though a WFS. The documentation of the GeoServer points out that the mapping „works both ways, so queries against properties of complex features are supported“. ( Application Schema Documentation <http://docs.geoserver.org/latest/en/user/data/app-schema/index.html> ) I am struggling right now with the meaning of the mapping file in this case. Is it just the same way back? One mapping file per complex type which “flattens” the data to simple features? Or is the app schema not able to do that and works only as an adapter between my complex features and the valid complex features XML output when I do a WFS request? I appreciate any help here. Best, Sebastian -- Sent from: http://osgeo-org.1560.x6.nabble.com/GeoServer-User-f3786390.html _______________________________________________ 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 Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
_______________________________________________ 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 Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
