On 30 July 2017 at 15:56, dracic 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
Just to add one thing. The problem is not related only to html responses.
The same issue is present with text, GML and GeoJSON responses. So my logic
tells me that this has nothing to do with freemarker templates. It has to
do with limiting attribute access through Geofence.
Best regards
Davor
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?
So my logic tells me that if this is the case, this would be the case with
the default Geoserver
But in freemarker a feature's attributes are stored in a map so there is no
expected order to them. If you require an order then you should define it.
Ian
On 28 Jul 2017 18:44, "dracic" wrote:
> Ok. I think I'm not clear enough. I do not want any specific order. I
>
Ok. I think I'm not clear enough. I do not want any specific order. I would
like generic behavior - which is the one when Geofence rules don't apply
and that is that the attributes are ordered in the way they are listed in
database tables or in attribute list in geoserver layer properties. So that
So with the previous template with no Geofence rule limiting attribute
access, GetFeatureinfo request orders columns as they are listed in tabel or
layer property. With Geofence rule, they have no particular order, and
subsequent request can have even different order from previous requests.
--
Sorry, those were default templates. This is my custom setup:
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/Geoserver-2-10-external-Geofence-3-2-GetFeatureInfo-problem-tp5329591p5329630.html
Sent from the GeoServer - User mailing list archive at Nabble.com.
I have tried with default templates and custom templates with the same
result. When I say "order" I mean column order as in PostGIS table DDL or in
Feature Type Details in Layer Properties. When you say "If you have not
specified a freemarker template for the request then I do not expect there
to
I have tried with default templates and custom templates with the same
result. When I say "order" I mean column order as in PostGIS table DDL or in
Feature Type Details in Layer Properties. When you say "If you have not
specified a freemarker template for the request then I do not expect there
to
If you have not specified a freemarker template for the request then I do
not expect there to be any specific attribute order implied in the
getfeatureinfo specification. If you have to have a fixed order of some of
the attributes then a freemarker template is probably the best way to go.
Ian
On
Hi everyone
I'm having strange problems with GetFeatureinfo requests when restricting
access to some of layer attributes. After that column order in getfeaturinfo
request results is messed up - reordered. I could see that following
requests change that order again.
This kind of rule order
11 matches
Mail list logo