"I'm saying that GeoServer and the WMS specification make no promises as to
the attribute order in a GetFeatureInfo request. "
Ian, please... Not all reasonable things have to be specified by some
specification. Constant attribute order change in GetfeatureInfo responses
is not something that is present in default Geoserver setup, so it is
should not be there when using Geofence plugin.
Best regards
Davor
ned, 30. srp 2017. u 17:19 Ian Turton [via OSGeo.org] <
[email protected]> napisao je:
> On 30 July 2017 at 15:56, dracic <[hidden email]
> <http:///user/SendEmail.jtp?type=node&node=5329801&i=0>> wrote:
>
>> So when no ordering is present in freemarker template the normal behavior
>> is that Geoserver orders attributes randomly for each Getfeatureinfo
>> request? Is that what you are trying to tell me?
>>
>
> I'm saying that GeoServer and the WMS specification make no promises as to
> the attribute order in a GetFeatureInfo request.
>
>
>> So my logic tells me that if this is the case, this would be the case
>> with the default Geoserver template. But that is not the case. There is an
>> order if there is not an explicit order in the template, and that is the
>> order in which attributes are listed in the table definition. If that isn't
>> the case every Getfeatureinfo would have different attribute order. I
>> haven't seen this behavior in any Geoserver setup.
>>
>>
> That some undefined behaviour occurs in a certain way in some cases in no
> way implies that it will be that way for all cases.
>
>
>
>> This behavior only exists when I apply attribute filter in Geofence -
>> whether I have my own template or use the default one.
>>
>>
> So if you need a fixed order set up a template that defines that order,
> otherwise ask for the info in another format and sort it your self to match
> your requirements.
>
> Ian
>
>
> ------------------------------------------------------------------------------
>
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Geoserver-users mailing list
>
> Please make sure you read the following two resources before posting to
> this list:
> - Earning your support instead of buying it, but Ian Turton:
> http://www.ianturton.com/talks/foss4g.html#/
> - The GeoServer user list posting guidelines:
> http://geoserver.org/comm/userlist-guidelines.html
>
> [hidden email] <http:///user/SendEmail.jtp?type=node&node=5329801&i=1>
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://osgeo-org.1560.x6.nabble.com/Geoserver-2-10-external-Geofence-3-2-GetFeatureInfo-problem-tp5329591p5329801.html
> To unsubscribe from Geoserver 2.10 & external Geofence 3.2 -
> GetFeatureInfo problem, click here
> <http://osgeo-org.1560.x6.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5329591&code=ZGF2b3IucmFjaWNAZ21haWwuY29tfDUzMjk1OTF8NjgxMTE0NzM1>
> .
> NAML
> <http://osgeo-org.1560.x6.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/Geoserver-2-10-external-Geofence-3-2-GetFeatureInfo-problem-tp5329591p5330161.html
Sent from the GeoServer - User mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Geoserver-users mailing list
Please make sure you read the following two resources before posting to this
list:
- Earning your support instead of buying it, but Ian Turton:
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines:
http://geoserver.org/comm/userlist-guidelines.html
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
