|
|
Davor Racic created an issue |
|
Issue Type: |
|
|---|---|
|
Affects Versions: |
2.10.4 |
|
Assignee: |
Unassigned |
|
Attachments: |
info1.png, info2.png, rule.png |
|
Components: |
GeoFence |
|
Created: |
02/Aug/17 10:06 AM |
|
Environment: |
CentOS 7, Java™ SE Runtime Environment (build 1.8.0_141-b15), |
|
Priority: |
|
|
Reporter: |
|
When applying Geofence attribute limit on layers, default behavior of WMS GetfeatureInfo responses changes - order of attributes as they are in table or layer properties changes, also attribute order is not consistent and subsequent GetFeatureInfo requests can change attribute order. This happens with HTML default or custom freemarker template, and even txt, GML, JSON responses - so has nothing to do with freemarker templates. I suppose that has to be something with geofence probe evalutaing attributes. Example: http://gis.hrsume.hr/hrsume/wms - layer: odj (visible at all scales) This kind of rule order works: Instance: default-gs / Service: WMS / Workspace: hrsume / Layer: All Deny at the end If I select Details and put some of the attributes on “Deny” - and with |
|
|
|
Get JIRA notifications on your phone! Download the JIRA Cloud app for Android or iOS |
|
|
This message was sent by Atlassian JIRA (v1000.1154.0#100057-sha1:fec937e) |
|
|
|