Hi,
Can you repeat this behaviour for example with the "states" feature type? I
could not. I tested with the OpenGEO demo server with unknown version and with
my own v. 2.3.3 and I seem to get the expected result from both with the
following request which I modified from yours.
http://demo.opengeo.org/geoserver/wfs?service=wfs&version=1.1.0&request=getfeature&typename=topp:states&outputformat=JSON&propertyname=STATE_NAME,FAMILIES,HOUSHOLD,MALE&BBOX=-91.516129,36.9867715,-87.507889,42.5093610001,EPSG:4326
-Jukka Rahkonen-
Christian Maul wrote:
>
> Hello,
>
> with the update from 2.1.3 to 2.3.3 the WFS behaviour has changed suddenly
>
> The following request
>
> http://sii-
> wms1.nre.vic.gov.au:8180/geoserver/ows/wfs?request=GetFeature&version=1.
> 1.0&typeName=sii:SURVEY_MARKS_POINT&BBOX=145.296473,-
> 37.876557,145.301065,-
> 37.875032,EPSG:4326&outputFormat=json&propertyName=DISPLAY_NAME,MA
> RK_ID,SYMBOL_TYPE_MGA,SHAPE
>
> which displays the attributes of one survey mark in 2.1.3 correctly, responds
> now with quadrupling the information and displays in 2.3.3 the attributes to
> the
> survey mark four times and does so consistently.
> I've verified this behaviour with the old version. Is there anything I need
> to
> change in the request? Checking the database there is one record for this mark
> and only one point.
>
> I, then played around with the attributes I want to display
> (propertyName=DISPLAY_NAME,MARK_ID,SYMBOL_TYPE_MGA,SHAPE) and for
> two attributes I get the whole lot twice, for three attributes thrice, for
> four
> attributes four time etc.
>
> Is that intended behaviour?
>
> Slightly puzzled
>
> Christian
>
>
>
> -
>
>
> Dr Christian Maul
> Project Manager
>
> Information Services Branch
> Department of Sustainability and Environment Level13, Marland House, 570
> Bourke Street Melbourne 3000
>
> PO Box 500, East Melbourne Vic 3002
>
>
> Telephone:+61-3-8636 2325
> Telefax: +61-3-8636 2813
> --
> View this message in context: http://osgeo-org.1560.x6.nabble.com/WFS-
> behaviour-changed-tp5070752.html
> Sent from the GeoServer - User mailing list archive at Nabble.com.
>
> --
> Get your SQL database under version control now!
> Version control is standard for application code, but databases havent caught
> up. So what steps can you take to put your SQL databases under version
> control?
> Why should you start doing it? Read more to find out.
> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
> ___
> Geoserver-users mailing list
> Geoserver-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
--
Get your SQL database under version control now!
Version control is standard for application code, but databases havent
caught up. So what steps can you take to put your SQL databases under
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users