un 21, 2017 at 9:46 AM, Christopher DeMars
wrote:
> After an update of geoserver, the logging no longer works and openlayers'
> getGetFeatureInfoUrl base feature query also no longer works. WMS layers
> (including parameterized SQL layers) work.
>
> Example of the feature query
After an update of geoserver, the logging no longer works and openlayers'
getGetFeatureInfoUrl base feature query also no longer works. WMS layers
(including parameterized SQL layers) work.
Example of the feature query:
localhost/geoserver/wms?SERVICE=WMS&VERSION=1.3.0&REQUEST=GetFeatureInfo&FORM
rything works. Joy!
On to the next bug!
Thanks again,
--Christopher
On Fri, Feb 17, 2017 at 11:20 AM, Christopher DeMars
wrote:
> I rewrote the sql view to not need any special characters:
>
>
>
> with pur as (select pur.comtrs,
> sum(pur.lbs_prd_us
owing parameter string works fine on geoserver.
sumvar:100;startdate:20140101;enddate:20141231;numcolors:6
;classification:quantile;colormap:Reds;prodnos: and ( pur.prodno = 30369 )
I'm at a loss of what could be different between the two on geoserver's end.
Thanks for any insight you can shar
Dear all,
Another issue: when I replace the summation parameter from a simple column
name "sum(pur.lbs_prd_used)" to an equation "sum(pur.lbs_prd_used *
pc.prodchem_pct / 100)", I get the following error:
2017-02-17 18:24:29,758 DEBUG [org.geotools.util] - CRSConverter:
Converting object of class
Jukka & Andrea,
Thank you!
I was able to get the query from the geotools log and with a bit of
tinkering using explain was able to speed things up enough to be useful. I
also upped the timeout window at least for testing purposes.
But of course, solve one bug get another.
Let me step back and e
Is there a way to get the actual query that geoserver is sending to the SQL
server?
I have a moderately complex parameterized SQL view. When I run it via
geoserver, it pegs all my cores at 100% then fails after minute or so with
the following error posted to the log:
org.geoserver.platform.Servic
