Hi guys, i have a question about "reload band definition" in edit layer page on WEB UI.
What does it do? Because basically i have a layer associated to a custom store that retrive data from my BE.
Now, initially the store is empty (no image on it), then i upload it .... The point is, when i do "compute from data" (for the bounding box) it actually download the image from the store and read the image to get the BBOX.... But when i click on "reload band definition" it's too fast, there is no download, and put "empty" as band.
Differently if i create the layer when the store has image on it, the band are loaded right....
Why? What does "reload band definition" should do? Thanks
P.S. in order to create the layer without having an image on the store, my plugin if the store is empty create a 100 x 100 black image so geoserver doesn't go in nullPointer...
Filter used to lookup userrunning as stated in the official tutorial.
@aaime I see you got the http://geoserver.org/announcements/2021/06/23/geoserver-2-18-4-released.html page out, and in markdown.
How was the writing experience? Were you able to cut and paste markdown from jira?
Looking at the code, maybe you need to customize a different header template?
that template also includes common-header.ftl
@pvgenuchten I have an answer for you ... the documentation does not match the code. Not sure which is right.
Please try the
templates/getfeature-header.ftl directory and report back.
templates/getfeature-header.ftlworks (see modified breadcrumbs below)
If I understand correctly the
<#global pagecrumbs="<li class='breadcrumb-item'><a href='"+serviceLink("")+"'>Home</a></li><li class='breadcrumb-item'><a href='"+serviceLink("collections")+"'>Collections</a></li><li class='breadcrumb-item active'>Feature</li>"> <#include "common-header.ftl"> TEST Test test
Does not know about our search order, and just looks in the same location as
aside: I have been having fun testing postgis/geoserver performance (eventually found the problem was old version of postgis pre TWKB).
During testing I was surprised that using "prepared statements" was a small bit slower than using text. I understood that using prepared statements (and simplify
fast ) would engage TWKB and I expected more of an effect.