Thanks Andrea,

I will provide bug report on my workflow with topp:states.

Thanks,
Ravi.





________________________________
From: Andrea Aime <[email protected]>
To: Ravi Pavuluri <[email protected]>
Cc: [email protected]
Sent: Mon, February 28, 2011 3:35:54 PM
Subject: Re: [Geoserver-users] GetFeature schema customization outputformat 
comparison


On Mon, Feb 28, 2011 at 7:14 PM, Ravi Pavuluri <[email protected]> wrote:

Hi,
>
>I am using a basic WFS on Geoserver(2.0.2)and wanted to limit the attributes 
>through "schema customization" to be shown in getfeature. I was following the 
>2.0.2 documentation and was not completely able to do that.
>
>As per 
>http://docs.geoserver.org/2.0.2/user/services/wfs/schemamapping.html#schema-customization
>
>"copy schema.xsd $GEOSERVER_DATA_DIR/featureTypes/<ds>_myDataset/"
>
>There is no featureTypes folder in geoserver data directory which contains 
>coverages,data,demo,gwc etc folders . Looks like the documentation was 
>outdated 
>for this page.
>
>I looked at 2.1.x user manual 
>http://docs.geoserver.org/stable/en/user/services/wfs/schemamapping.html#schema-customization
>
>"copy schema.xsd  
>$GEOSERVER_DATA_DIR/workspaces/<workspace>/<datastore>/myDataset/"
>
>The above directory structure exists in 2.0.2 and I was succesfully able to 
>limit the attributes in the describefeaturetype call.
>
>But when I tried to use GetFeature for a given typeName with 
>
>1) WFS 1.1.0 and GML2/GML3 outputformat
>Customized list of attributes is populated..
>Logs:No Errors
>
>2) WFS 1.1.0 and shape-zip outputformat
>The entire list of  attributes is populated..
>Logs:No Errors
>
>Is this an expected behavior with different output formats? Any suggestions?
>
>

The system to limit the attributes was really just designed to work for the GML 
based output formats.
That said, the mechanism should actually be working for shapefiles too, so 
there 
might be a bug
at work.

Please report a but report on jira.codehaus.org, if possible providing a ready 
made customization
of the topp:states layer and the request to make it fail so that we can quickly 
reproduce it
when trying to fix it (various developers have time to fix community reported 
issues only in 
their spare time, so having an easy to reproduce issue is key to get a bug 
fixed)

Cheers
Andrea
-- 
-------------------------------------------------------
Ing. Andrea Aime
GeoSolutions S.A.S.
Tech lead

Via Poggio alle Viti 1187
55054  Massarosa (LU)
Italy

phone: +39 0584 962313
fax:      +39 0584 962313
mob:    +39 333 8128928

http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.youtube.com/user/GeoSolutionsIT
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf

-------------------------------------------------------



      
------------------------------------------------------------------------------
Free Software Download: Index, Search & Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Reply via email to