Robert,
the standard WFS 1.1 option for this is propertyName, supported for all
GeoServer simple feature types. Append &propertyName=prop1,prop2,... to
your GeoServer GET URL and only the named properties will be returned.
If your geometry is not one of them, it will be encoded as null in the
GeoJSON response. I tested it and it works for outputFormat=json.
Kind regards,
Ben.
On 26/07/11 15: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
>
--
Ben Caradoc-Davies <[email protected]>
Software Engineering Team Leader
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre
------------------------------------------------------------------------------
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
