Hey Robert,

i think that something like this is what ur looking for; a GeoExt grouping grid workaround. Am i right?
i've done this for my project try:

var GroupingFeatureStore = Ext.extend(Ext.data.GroupingStore,GeoExt.data.FeatureStoreMixin());

var storeGroup= new GroupingFeatureStore({
         scopte     : this,
         fields     :  [
                        {name : 'field_xx',  type  : 'string'},
                        {name : 'field_xxx', type  : 'string'},
                        {name : 'field_yyy',  type  : 'float'},
                        {name : 'yyyy',   type  : 'string'},
                        {name : 'yyyy',  type  : 'int'}
                      ],
         layer      : wfs_layer,
         groupField : 'field_xx'
});

var grid = new Ext.grid.EditorGridPanel({
        id          : 'gridTeilId',
        store       : storeGroup, ...})

regards,
Simon


Am 26.07.2011 10:52, schrieb Robert Buckley:
ah..are you saying if I use the geoext feature store, I could bind to any ext component I wish?

(sorry for using the geoserver forum for this)

thanks,

Rob

------------------------------------------------------------------------
*Von:* Bart van den Eijnden (OSGIS) <[email protected]>
*An:* Robert Buckley <[email protected]>
*CC:* [email protected]
*Gesendet:* Dienstag, den 26. Juli 2011, 10:41:21 Uhr
*Betreff:* Re: [Geoserver-users] How to remove the Geo from json?

Hi Robert,

why are you not simply using a GeoExt FeatureStore for your Ext grid?

Best regards,
Bart

> Thanks for the answers.
>
> I was able to get the wfs reponse for the properties I needed, but I still
> needed to edit the json format in order for it to be read as json by an
> Ext.js
> grid....
>
> e.g
>
> is was only possible to bind to a grid if I delete the following from the
> start
> of the wfs response...
>
> {"type":"FeatureCollection","features":[
>
> and then for each dataset delete this from the beginning
>
> {"type":"Feature","id":"EnMap_SG_WEA_f.1","geometry":null,"properties":
>
> and of course the extra " } " from the end of the line.
>
> It will still mean that every data record needs to be edited doesn´t it?
>
> I´m probably missing some basic understanding here!?!?!
>
> yours,
>
> Rob
>
>
>
>
>
>
>
> ________________________________
> Von: Andreas Hocevar <[email protected] <mailto:[email protected]>> > An: Robert Buckley <[email protected] <mailto:[email protected]>> > CC: [email protected] <mailto:[email protected]>
> Gesendet: Dienstag, den 26. Juli 2011, 9:29:49 Uhr
> Betreff: Re: [Geoserver-users] How to remove the Geo from json?
>
> Hi,
>
> use the PropertyName param (for GET requests) or configure your HTTP
> protocol
> with a propertyName. This is a comma separated list of the attributes you
> want
> to include, e.g.
>
> http://localhost:8080/geoserver/wfs?service=wfs&version=1.1.0&request=getfeature&typename=topp:states&outputformat=json&propertyname=STATE_NAME <http://localhost:8080/geoserver/wfs?service=wfs&version=1.1.0&request=getfeature&typename=topp:states&outputformat=json&propertyname=STATE_NAME>
>
>
> Andreas.
>
> On Jul 26, 2011, at 09:01 , Robert Buckley wrote:
>
>> Hi,
>>
>> I have to present the output of a geoserver json file in an ext grid.
>> The
>>problem is that due to the fact that the geodata comes from a polygon I
>> am
>>getting way to much data from the geoserver json output file. I really
>> need to
>>remove the Geometry data so that I can get only the attribute data.
>>
>> Has anyone done this before? Is there a script or method apart from
>> opening the
>>file in a text editor and editing out all the data I don´t need?
>>
>> e.g
>>
>>{"type":"Feature","id":"EnMap_SG_WEA_f.1","geometry":{"type":"MultiPolygon","coordinates":[[[[3594275.44,5850104.87],[3594549.
>>. etc etc etc etc etc
>>
>> needs to be deleted from this row...
>>
>>
>> I need to do this for about 3000 rows.
>>
>>
>> thanks for any help,
>>
>> Rob
>> ------------------------------------------------------------------------------
>> Magic Quadrant for Content-Aware Data Loss Prevention
>> Research study explores the data loss prevention market. Includes
>> in-depth
>> analysis on the changes within the DLP market, and the criteria used to
>> evaluate the strengths and weaknesses of these DLP solutions.
>>http://www.accelacomm.com/jaw/sfnl/114/51385063/_______________________________________________
>>_
>> Geoserver-users mailing list
>> [email protected] <mailto:[email protected]>
>> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>
>
>
> --
> Andreas Hocevar
> OpenGeo - http://opengeo.org/
> Expert service straight from the
> developers.------------------------------------------------------------------------------
> Magic Quadrant for Content-Aware Data Loss Prevention
> Research study explores the data loss prevention market. Includes in-depth
> analysis on the changes within the DLP market, and the criteria used to
> evaluate the strengths and weaknesses of these DLP solutions.
> http://www.accelacomm.com/jaw/sfnl/114/51385063/_______________________________________________
> Geoserver-users mailing list
> [email protected] <mailto:[email protected]>
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>




------------------------------------------------------------------------------
Magic Quadrant for Content-Aware Data Loss Prevention
Research study explores the data loss prevention market. Includes in-depth
analysis on the changes within the DLP market, and the criteria used to
evaluate the strengths and weaknesses of these DLP solutions.
http://www.accelacomm.com/jaw/sfnl/114/51385063/


_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users


--
Visit me at
 - Blog   : http://www.maptags.de
 - Twitter: http://twitter.com/maptagsde
 - youtube: http://www.youtube.com/maptagsde

------------------------------------------------------------------------------
Magic Quadrant for Content-Aware Data Loss Prevention
Research study explores the data loss prevention market. Includes in-depth
analysis on the changes within the DLP market, and the criteria used to
evaluate the strengths and weaknesses of these DLP solutions.
http://www.accelacomm.com/jaw/sfnl/114/51385063/
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Reply via email to