Hi, We try and publish a dataset in accordance to the European Inspire Directive with geoserver, and have a rather though time to have it properly set up (euphemism, I love them!).
Namely, we try to solve this 'error', as it seems to be reported as such by the european validator: https://gis.urban.brussels/geoserverinspire/ows?service=wfs&version=2.0.0&request=DescribeFeatureType&typename=ps:ProtectedSite This request 'should' send an xsd explaining the structure of the feature ps:ProtectedSite, but instead gives a minimal xsd containing only an include tag pointing to the schemalocation: <?xml version="1.0" encoding="UTF-8"?><xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:base="http://inspire.ec.europa.eu/schemas/base/3.3"; xmlns:gco="http://www.isotc211.org/2005/gco"; xmlns:gmd="http://www.isotc211.org/2005/gmd"; xmlns:gml="http://www.opengis.net/gml/3.2"; xmlns:gn="http://inspire.ec.europa.eu/schemas/gn/4.0"; xmlns:gsr="http://www.isotc211.org/2005/gsr"; xmlns:gss="http://www.isotc211.org/2005/gss"; xmlns:gts="http://www.isotc211.org/2005/gts"; xmlns:ps="http://inspire.ec.europa.eu/schemas/ps/4.0"; xmlns:xlink="http://www.w3.org/1999/xlink"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; elementFormDefault="qualified" targetNamespace="http://inspire.ec.europa.eu/schemas/ps/4.0"; xmlns:xml="http://www.w3.org/XML/1998/namespace";> <xsd:include schemaLocation="http://inspire.ec.europa.eu/schemas/ps/4.0/ProtectedSites.xsd"/> </xsd:schema> Is it standard and normal behaviour, and it is the european validator that should be able to handle xsd responses containing include tags towards external xsd, or is there something to be set differently in our appschema mapping file in order to have the xsd stuffed with the content of the distant xsd? I must say the ps namespace contains itself a reference towards gn:Geonames namespace, and the structure is of the complexfeature type (to make things a bit easier, one never has enough fun with this...). Such secondary gn namespace has been created also, according to the docs of geoserver, at least I hope we did it properly. We do not hit this new geoserverinspire dedicated only to this Inspire layer though virtual service /ps/ to avoid any problem with appschema and multiple namespaces. Any idea? Surely someone is having as much fun as we have with all this wonderful Joseph II kind of stuff? All the best, Greg for BruGIS
_______________________________________________ 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
