|
From: Andrea A. <and...@ge...> - 2010-11-10 10:33:36
|
On Wed, Nov 10, 2010 at 9:42 AM, Frank Gasdorf <fg...@us...> wrote: > Hello geoserver developers! > > I started implementing a simple wfs client based on the OWS infrastructure > to get features from a getFeatures Request with a BBOX Filter and mixed > types for the typeName attribute. See the following request: > > http://localhost:8080/geoserver/wfs?request=GetFeature&version=1.1.0&typeName=ne-50m-admin-0-countries,ne-10m-populated-places&BBOX=-75.102613,40.212597,-72.361859,41.512517,EPSG:4326&OUTPUTFORMAT=GML2 > > The two types are taken from http://www.naturalearthdata.com/ and added as > shapefile datastores/layers to a geoserver 2.0.2 > > The schemlocation of the response gml file is wrong, the DescribeFeatureType > has the two requested typenames, one with the namespace and the other one > without. > > <wfs:FeatureCollection xsi:schemaLocation="http://www.naturalearthdata.com/ > http://mapserv1:80/geoserver/wfs?service=WFS&version=1.0.0&request=DescribeFeatureType&typeName=naturalEarth%3Ane-50m-admin-0-countries,ne-10m-populated-places > http://www.opengis.net/wfs > http://mapserv1:80/geoserver/schemas/wfs/1.0.0/WFS-basic.xsd"> > > A ServerException occures requesting the DescribeFeatureType > > <ServiceExceptionReport version="1.2.0" > xsi:schemaLocation="http://www.opengis.net/ogc > http://schemas.opengis.net/wfs/1.0.0/OGC-exception.xsd"> > - > <ServiceException> > > Could not find type: ne-10m-populated-places > </ServiceException> > </ServiceExceptionReport> > > I tried an older geoserver version (1.7.5) and the response looks good, the > typename is always append after namespace. > > I added the namespace for the typenames in the GetFeature Request for both > types but that end up into the same resulting response. > > http://localhost:8080/geoserver/wfs?request=GetFeature&version=1.1.0&typeName=naturalEarth%3Ane-50m-admin-0-countries,naturalEarth%3Ane-10m-populated-places&BBOX=-75.102613,40.212597,-72.361859,41.512517,EPSG:4326&outputFormat=GML2 > > Do you have any suggestions? Maybe it has to deal with changes of > GML2OutputFormat.java A few suggestions: - don't hijack an old thread to ask new questions. The subject line has nothing to do with the question you're posing today. Always start a new thread with a consistent subject - if you're using WFS 1.1 and making a standard client you should be using GML3, GML2 is not guaranteed to be there - when reporting issues use a recent nightly build of the 2.0.x series, the release is very old In any case, it seems what you're seeing is still valid, this one has issues the same way: http://demo.opengeo.org/geoserver/wfs?request=GetFeature&typeName=og:archsites,og:bugsites&version=1.1.0&outputFormat=GML2 and this one as well: http://demo.opengeo.org/geoserver/wfs?request=GetFeature&typeName=og:archsites,og:bugsites&version=1.0.0&outputFormat=GML2 So yeah, open a bug report. A test and a patch attached to it to solve the issue would also go a long way in making the problem fixed soon ;-) Cheers Andrea ----------------------------------------------------- Ing. Andrea Aime Senior Software Engineer GeoSolutions S.A.S. Via Poggio alle Viti 1187 55054 Massarosa (LU) Italy phone: +39 0584962313 fax: +39 0584962313 http://www.geo-solutions.it http://geo-solutions.blogspot.com/ http://www.linkedin.com/in/andreaaime http://twitter.com/geowolf ----------------------------------------------------- |