[OpenLayers-Dev] Patch for WFS Protocol to allow for different outputFormat

Roald de Wit roald.dewit at lisasoft.com
Mon May 25 02:50:00 EDT 2009


Hi,

I got inspired by Eric who managed to create a ticket despite trac's
unwillingness to make life easy, so after 15 minutes of reloading and
one duplicate ticket, here it is:

http://trac.openlayers.org/ticket/2107

Cheers, Roald

Roald de Wit wrote:
> Hi,
>
> I wanted to do something relatively simple that is not possible with the
> current WFS protocol: request a different outputFormat (JSON in my case).
>
> The following patch makes this possible. I'd like to get feedback on
> whether is is the right path to follow to get this done. If it looks
> good, I'll create appropriate tests.
>
> Example use:
>
>                 protocol: new OpenLayers.Protocol.WFS({
>                         readFormat: new OpenLayers.Format.GeoJSON(),
>                         formatOptions: {
>                             outputFormat: "JSON"
>                         }, .....
>
> Regards, Roald
>
> P.S. I sent this to the dev list since trac is unusable atm.
>
> --
> Roald de Wit
> Software Engineer
> roald.dewit at lisasoft.com
>
> Commercial Support for Open Source GIS Software
> http://lisasoft.com/LISAsoft/SupportedProducts/
>
>
>
> The contents of this email are confidential and may be subject to legal or professional privilege and copyright. No representation is made that this email is free of viruses or other defects. If you have received this communication in error, you may not copy or distribute any part of it or otherwise disclose its contents to anyone. Please advise the sender of your incorrect receipt of this correspondence.
>


--
Roald de Wit
Software Engineer
roald.dewit at lisasoft.com

Commercial Support for Open Source GIS Software
http://lisasoft.com/LISAsoft/SupportedProducts/



The contents of this email are confidential and may be subject to legal or professional privilege and copyright. No representation is made that this email is free of viruses or other defects. If you have received this communication in error, you may not copy or distribute any part of it or otherwise disclose its contents to anyone. Please advise the sender of your incorrect receipt of this correspondence.



More information about the Dev mailing list