[Geoserver-users] GeoServer Docker Image 2.24.0

[Christian Mayer]

Hi all,

when looking to the OSGeo Nexus it seems the Docker Image for GeoServer 
version 2.24.0 is missing: 
https://docker.osgeo.org/#browse/search/docker=attributes.docker.imageName%3Dgeoserver%20AND%20attributes.docker.imageTag%3D2.24* 



Is that the case or am I looking at the wrong spot? In case it is really 
missing, is there a planned date when the image will be available?


Thanks for any hint / help.

Best regards
Chris





___
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

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] problem with Proxy Base URL as from version 2.19

[Christian Mayer]

Hi Frans, hi all,

I had running a GeoServer >2.19 with a nginx in the past. I remember 
some problems with unwanted redirects and similar when behind the proxy.


Besides setting the "Proxy Base URL" I had to set the ENV VAR 
"GEOSERVER_CSRF_WHITELIST", like 
GEOSERVER_CSRF_WHITELIST=my-geoserver.server.de to get the Web-UI and 
all services fully functional.


Not sure if it was exactly the same problems you had but maybe you want 
to give it a shot and report back here.


Best regards
Chris

On 03.08.22 08:57, Frans Fierens wrote:


Thx Graham.

This is indeed a solution. But not everything is solved: a wfs/wms 
GetCapabilities request will rely on the Global proxy-base url. It 
seems that the "online resource" option in the wfs/wms service section 
is not being used (?)


To illustrate this:

1. GetCapabilities using geoserver v2.18.6: 
https://geo.irceline.be/wfs?request=GetCapabilities&service : the 
xlinks are correctly pointing to the proxy url 
https://geo.irceline.be/wfs. Global proxy-base 
url=https://geo.irceline.be, admin pages are accessible.


2. GetCapabilities using geoserver v2.21.0 with empty Global 
proxy-base url: 
https://geonew.irceline.be/wfs?request=GetCapabilities&service : the 
xlinks are pointing to http://georocky/geoserver/wfs and NOT to the 
correct proxy url https://geonew.irceline.be/wfs. This will only be 
correct when the Global proxy-base url is not empty ... but then the 
admin pages are not accessible anymore.


catch 22 ...

best regards,

Frans


On 03/08/2022 02:22, Humphries, Graham wrote:


Hi Frans,

I lodged the original issue about this. What I have done is set the 
proxy-base url for the workspace and left the Global proxy-base url 
unset. This allows me to access the admin pages.


*From:*Frans Fierens 
*Sent:* Wednesday, 3 August 2022 2:26 AM
*To:* Andrea Aime 
*Cc:* geoserver-users@lists.sourceforge.net
*Subject:* Re: [Geoserver-users] problem with Proxy Base URL as from 
version 2.19


Thanks Andrea,

I already tried to configure the nginx but without success. It would 
be interesting to get more info on the nginx config. There are also 
other issues to deal when using this option: you give internet access 
to the admin pages (which I would prefer not to do).


best regards,

Frans

On 02/08/2022 18:09, Andrea Aime wrote:

Hi Frans,

maybe it just requires a different set up? These two servers are
using nginx proxying, and a proxy base URL,

but the UI works, as you can see:

https://gs-main.geosolutionsgroup.com/geoserver/web/



http://gs-stable.geosolutionsgroup.com/geoserver/web/



One is a 2.20.x, the other is a nightly build from the developer
series.

Unfortunately I don't know exactly how they are set up NGINX
wise, but I can tell you the proxy base URL configured in GeoServer

is simple, e.g. "https://gs-main.geosolutionsgroup.com/geoserver/

"

Cheers

Andrea

On Tue, Aug 2, 2022 at 3:10 PM Frans Fierens
 wrote:

Hello,

I do have the same problem as posted in:
https://sourceforge.net/p/geoserver/mailman/message/37250476/



When geoserver is behind a reverse proxy as n

Re: [Geoserver-users] Problem with WMS Cascade

[Christian Mayer]

Hi Fernando,

we have a similar setup in a project and we are treating every cascaded
layer as a separate resource and thus we create a separate datastore for
it via GeoServer REST-API. The idea is that every layer, which is
populated by our "GeoServer 02" could (in theory) be from a different
WMS (even tough most of the time it is "GeoServer 01".

Or as Andrea stated drop your datastore and re-create ist. This could
also be automated via GeoServer REST-API.

Cheers
Chris

On 17.12.21 11:24, Andrea Aime wrote:
> On Thu, Dec 16, 2021 at 7:55 PM Fernando Quadro  > wrote:
>
> The question is, is there how this update can be automatic in
> GeoServer 02 (when going to Add new layer), when a new layer is
> created in GeoServer 01?
>
>
> Not that I know of. GeoServer has only one instance of that WMS store,
> which is used alike for OGC requests and configurations.
> Not caching the capabilities document would slow down requests
> tremendously... and from the p.o.v. of GeoSever the cache is really 
> just holding an instance of the store, the caps cache is happening
> inside the store, which also offers no way to clear it, it's grabbed on
> object creation and the functionality of the object depends on having
> it at all times.
> Currently the only way to drop it, would be to drop the store itself
> (so another way is to go and hit the "clear" button in the GeoServer
> status panel)... 
> code changes would be needed to do that. 
>
> Cheers
> Andrea
> ==
>
> GeoServer Professional Services from the experts!
>
> Visit http://bit.ly/gs-services-us for
> more information.==Ing. Andrea Aime @geowolfTechnical Lead
>
> GeoSolutions Groupphone: +39 0584 962313
>
> fax:     +39 0584 1660272
>
> mob:   +39  333 8128928
>
>
> https://www.geosolutionsgroup.com/ 
>
> http://twitter.com/geosolutions_it 
>
> ---
>
>
> Con riferimento alla normativa sul trattamento dei dati personali
> (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati
> “GDPR”), si precisa che ogni circostanza inerente alla presente email
> (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui
> conoscenza è riservata al/i solo/i destinatario/i indicati dallo
> scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a
> cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato
> se potesse darmene notizia.This email is intended only for the person
> or entity to which it is addressed and may contain information that is
> privileged, confidential or otherwise protected from disclosure. We
> remind that - as provided by European Regulation 2016/679 “GDPR” -
> copying, dissemination or use of this e-mail or the information herein
> by anyone other than the intended recipient is prohibited. If you have
> received this email by mistake, please notify us immediately by
> telephone or e-mail
>
>
> ___
> 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
>
> If you want to request a feature or an improvement, also see this: 
> https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
>
>
> Geoserver-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
___
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

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] Missing ImageMosaic plugin/exetension for version 2.20.x

[Christian Mayer]

Hi Andrea,

thanks for your response and the clarification. I got the point. I know
a few projects using (or at least they used) the imagemosaic-jdbc
plugin. I'll get in touch with them and see what we can do on this
topic. But can't promise anything. I'll come back here if there is
anything to report.

Thanks again
Chris

On 02.11.21 19:12, Andrea Aime wrote:
> Hi Christian,
> the imagemosaic-jdbc plugin has been removed from the GeoServer source
> code,
> after years without a dedicated maintainer. 
>
> It can be resurrected from the dead: that will require a new
> maintainer, or someone
> interested in investing in it so that other developers can get
> familiar with the module, and remove 
> all the rust that accumulated on it.
>
> Cheers
> Andrea
>
> On Tue, Nov 2, 2021 at 7:00 PM Christian Mayer  <mailto:ml...@meggsimum.de>> wrote:
>
> Hi all,
>
> I tried to upgrade our GeoServer instances from 2.19.x to 2.20.x
> (wrapped as Docker image, which should not be the point here). For
> version 2.19.x I could download the ImageMosaic extension from
> 
> https://build.geoserver.org/geoserver/2.19.x/community-latest/geoserver-2.19-SNAPSHOT-imagemosaic-jdbc-plugin.zip
> 
> <https://build.geoserver.org/geoserver/2.19.x/community-latest/geoserver-2.19-SNAPSHOT-imagemosaic-jdbc-plugin.zip>.
> The corresponding link/download for version 2.20.x is missing. Does
> anyone know something about this? Or can point me to a valid link?
>
> Thanks for any hint,
> Chris
>
>
>
> ___
> 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#/
> <http://www.ianturton.com/talks/foss4g.html#/>
> - The GeoServer user list posting guidelines:
> http://geoserver.org/comm/userlist-guidelines.html
> <http://geoserver.org/comm/userlist-guidelines.html>
>
> If you want to request a feature or an improvement, also see this:
> 
> https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
> 
> <https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer>
>
>
> Geoserver-users@lists.sourceforge.net
> <mailto:Geoserver-users@lists.sourceforge.net>
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
> <https://lists.sourceforge.net/lists/listinfo/geoserver-users>
>
>
>
> -- 
>
> Regards,
>
> Andrea Aime
>
> ==GeoServer Professional Services from the experts!
>
> Visit http://bit.ly/gs-services-us <http://bit.ly/gs-services-us>for
> more information.==Ing. Andrea Aime @geowolfTechnical Lead
>
> GeoSolutions Groupphone: +39 0584 962313
>
> fax:     +39 0584 1660272
>
> mob:   +39  333 8128928
>
>
> https://www.geosolutionsgroup.com/ <https://www.geosolutionsgroup.com/>
>
> http://twitter.com/geosolutions_it <http://twitter.com/geosolutions_it>
>
> ---
>
>
> Con riferimento alla normativa sul trattamento dei dati personali
> (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati
> “GDPR”), si precisa che ogni circostanza inerente alla presente email
> (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui
> conoscenza è riservata al/i solo/i destinatario/i indicati dallo
> scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a
> cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato
> se potesse darmene notizia.This email is intended only for the person
> or entity to which it is addressed and may contain information that is
> privileged, confidential or otherwise protected from disclosure. We
> remind that - as provided by European Regulation 2016/679 “GDPR” -
> copying, dissemination or use of this e-mail or the information herein
> by anyone other than the intended recipient is prohibited. If you have
> received this email by mistake, please notify us immediately by
> telephone or e-mail
___
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

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

[Geoserver-users] Missing ImageMosaic plugin/exetension for version 2.20.x

[Christian Mayer]

Hi all,

I tried to upgrade our GeoServer instances from 2.19.x to 2.20.x
(wrapped as Docker image, which should not be the point here). For
version 2.19.x I could download the ImageMosaic extension from
https://build.geoserver.org/geoserver/2.19.x/community-latest/geoserver-2.19-SNAPSHOT-imagemosaic-jdbc-plugin.zip.
The corresponding link/download for version 2.20.x is missing. Does
anyone know something about this? Or can point me to a valid link?

Thanks for any hint,
Chris



___
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

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] Publish SLD with InlineContent via REST API

[Christian Mayer]

Hi all,

I created an issue in GeoServer's JIRA for the described exception/bug:
https://osgeo-org.atlassian.net/browse/GEOS-10220

Regards
Chris

On 27.08.21 11:00, Christian Mayer wrote:
>
> Hi all,
>
> thanks for your replies and sorry that I forgot to mention the version
> I am using. The error occurred on v2.19.1 in my setup.
>
> Regards
> Chris
>
> On 27.08.21 10:45, Roar Brænden wrote:
>> Hi,
>>
>> I can confirm that the same exception occurs when running Geoserver main.
>>
>> Regards,
>>
>> Roar
>>
>>
>>> 27. aug. 2021 kl. 09:37 skrev Andrea Aime
>>> >> <mailto:andrea.a...@geosolutionsgroup.com>>:
>>>
>>> Hi all,
>>> before opening a ticket please make sure it's happening also on
>>> 2.19.x, lots of code changes happened
>>> in between.
>>>
>>> Cheers
>>> Andrea
>>>
>>> On Fri, Aug 27, 2021 at 8:31 AM Roar Brænden
>>> mailto:roar.brenden...@gmail.com>> wrote:
>>>
>>> Hi,
>>>
>>> I tried your call on a Geoserver version 2.15.2 and can confirm
>>> there is a bug in that version. Which version are you running?
>>> You should consider to open an issue, to have someone look
>>> further into the case.
>>>
>>> I've got the trace log from the log-files as well. That could be
>>> useful when opening an issue.
>>>
>>> Best regards,
>>> Roar Brænden
>>>
>>> 2021-08-27 06:08:10,705 ERROR [geoserver.rest] - Error writing style
>>> org.geoserver.rest.RestException 500 INTERNAL_SERVER_ERROR:
>>> Error writing style
>>> at
>>> 
>>> org.geoserver.rest.catalog.StyleController.styleSLDPost(StyleController.java:242)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at
>>> 
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>>> at
>>> 
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>> at java.lang.reflect.Method.invoke(Method.java:498)
>>> at
>>> 
>>> org.springframework.web.method.support.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:207)
>>> at
>>> 
>>> org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:137)
>>> at
>>> 
>>> org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:102)
>>> at
>>> 
>>> org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:895)
>>> at
>>> 
>>> org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:800)
>>> at
>>> 
>>> org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:87)
>>> at
>>> 
>>> org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:1038)
>>> at
>>> 
>>> org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:942)
>>> at
>>> 
>>> org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:998)
>>> at
>>> 
>>> org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:901)
>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:660)
>>> at
>>> 
>>> org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:875)
>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:741)
>>> at
>>> 
>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231)
>>> at
>>> 
>>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
>>> at
>>> org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53)
>>> at
>>> 
>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
>>> at
>>> 
>>> org.apache.catalina.core.ApplicationFilterChain.doFilter(Application

Re: [Geoserver-users] Publish SLD with InlineContent via REST API

[Christian Mayer]

rent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>> at
>> 
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>> at
>> 
>> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
>> at java.lang.Thread.run(Thread.java:748)
>> Caused by: java.io.IOException: Error writing style
>> at org.geoserver.catalog.SLDHandler.encode10(SLDHandler.java:263)
>> at org.geoserver.catalog.SLDHandler.encode(SLDHandler.java:250)
>> at
>> org.geoserver.catalog.ResourcePool.writeStyle(ResourcePool.java:2069)
>> at
>> 
>> org.geoserver.rest.catalog.StyleController.writeStyle(StyleController.java:531)
>> at
>> 
>> org.geoserver.rest.catalog.StyleController.styleSLDPost(StyleController.java:240)
>> ... 104 more
>> Caused by: javax.xml.transform.TransformerException: Translator error
>> at
>> 
>> org.geotools.xml.transform.TransformerBase.transform(TransformerBase.java:122)
>> at
>> 
>> org.geotools.xml.transform.TransformerBase.transform(TransformerBase.java:100)
>> at org.geoserver.catalog.SLDHandler.encode10(SLDHandler.java:261)
>> ... 108 more
>> Caused by: java.lang.NullPointerException
>> at
>> org.apache.xml.serializer.ToStream.writeAttrString(ToStream.java:2098)
>> at
>> org.apache.xml.serializer.ToStream.processAttributes(ToStream.java:2078)
>> at org.apache.xml.serializer.ToStream.endElement(ToStream.java:2223)
>> at
>> 
>> org.apache.xalan.transformer.TransformerIdentityImpl.endElement(TransformerIdentityImpl.java:1102)
>> at
>> 
>> org.geotools.xml.transform.TransformerBase$ContentHandlerFilter.endElement(TransformerBase.java:312)
>> at
>> 
>> org.geotools.xml.transform.TransformerBase$TranslatorSupport._end(TransformerBase.java:802)
>> at
>> 
>> org.geotools.xml.transform.TransformerBase$TranslatorSupport.access$400(TransformerBase.java:404)
>> at
>> 
>> org.geotools.xml.transform.TransformerBase$TranslatorSupport$DirectBackend.end(TransformerBase.java:594)
>> at
>> 
>> org.geotools.xml.transform.TransformerBase$TranslatorSupport.end(TransformerBase.java:796)
>> at
>> 
>> org.geotools.xml.transform.TransformerBase$TranslatorSupport.element(TransformerBase.java:762)
>> at
>> 
>> org.geotools.xml.styling.SLDTransformer$SLDTranslator.visit(SLDTransformer.java:809)
>> at
>> 
>> org.geotools.styling.ExternalGraphicImpl.accept(ExternalGraphicImpl.java:135)
>> at
>> 
>> org.geotools.xml.styling.SLDTransformer$SLDTranslator.visit(SLDTransformer.java:952)
>> at org.geotools.styling.GraphicImpl.accept(GraphicImpl.java:333)
>> at
>> 
>> org.geotools.xml.styling.SLDTransformer$SLDTranslator.visit(SLDTransformer.java:925)
>> at
>> 
>> org.geotools.styling.PointSymbolizerImpl.accept(PointSymbolizerImpl.java:86)
>> at
>> 
>> org.geotools.xml.styling.SLDTransformer$SLDTranslator.visit(SLDTransformer.java:888)
>> at org.geotools.styling.RuleImpl.accept(RuleImpl.java:303)
>> at
>> 
>> org.geotools.xml.styling.SLDTransformer$SLDTranslator.visit(SLDTransformer.java:1232)
>> at
>> 
>> org.geotools.xml.styling.SLDTransformer$SLDTranslator.visit(SLDTransformer.java:1195)
>> at
>> 
>> org.geotools.xml.styling.SLDTransformer$SLDTranslator.visit(SLDTransformer.java:1015)
>> at
>> 
>> org.geotools.xml.styling.SLDTransformer$SLDTranslator.visit(SLDTransformer.java:987)
>> at
>> 
>> org.geotools.styling.StyledLayerDescriptorImpl.accept(StyledLayerDescriptorImpl.java:171)
>> at
>> 
>> org.geotools.xml.styling.SLDTransformer$SLDTranslator.encode(SLDTransformer.java:1369)
>> at
>> 
>> org.geotools.xml.styling.SLDTransformer$SLDTranslator.encode(SLDTransformer.java:1378)
>> at
>> 
>> org.geotools.xml.transform.TransformerBase$XMLReaderSupport.parse(TransformerBase.java:995)
>> at
>> 
>> org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentityImpl.java:485)
>> at
>> 
>> org.geotools.xml.transform.TransformerBase$Task.run(TransformerBase.java:283)
>> at
>> 
>> org.geotools.xml.transform.TransformerBase.transf

[Geoserver-users] Publish SLD with InlineContent via REST API

[Christian Mayer]

Hi all,

I am trying to publish a SLD with InlineContent (a base64 png image) by
using the REST-API. The request fails with the message an HTTP 500
"Error writing style". The REST call works quite well with a "normal"
SLD, such as the simple "point" example. So the problem seems to be
related to the InlineContent element. When I publish the SLD with the
InlineContent element via GeoServer web GUI it works without any issues
and even the validator says "No validation errors.". Did anyone
experience this as well and has maybe a workaround for that? Any hint
very much appreciated. Here is my REST API call

curl -X POST \
 
'http://localhost:8080/geoserver/rest/workspaces/test-cm/styles?name=foo' \
  -H 'Authorization: Basic YWRtaW46Z2Vvc2VydmVy' \
  -H 'Content-Type: application/vnd.ogc.sld+xml' \
  -H 'cache-control: no-cache' \
  -d '
http://www.w3.org/2001/XMLSchema-instance'\''
    xmlns="http://www.opengis.net/sld";
    xmlns:sld="http://www.opengis.net/sld";
    xmlns:se="http://www.opengis.net/se";
    xsi:schemaLocation="http://www.opengis.net/sld
http://schemas.opengis.net/sld/1.1.0/StyledLayerDescriptor.xsd
    http://www.opengis.net/se
http://schemas.opengis.net/se/1.1.0/FeatureStyle.xsd";
    version="1.1.0"
    >
    
  sauber_stations
    
    
    
  sauber_stations_rule_1
    
  
  
  iVBORw0KGgoNSUhEUgAAACQkCAYAAADhAJiYBGdBTUEAALGPC/xhBQAAACBjSFJNAAB6JgAAgIQAAPoAAACA6AAAdTAAAOpgAAA6mAAAF3CculE8BmJLR0QAAAD5Q7t/CXBIWXMAAABgYADwa0LPAAABhklEQVRYw+3XMUscURAH8J854QJ2EUzSpZWENCcqGNATvC9gII3kI5jS9iy1EPEz2PgVDCQpDBgSGxtBC0vBMiGaI4ak2HfccZ7Hure7d4H9w8C8eftm/m/mveEtBQr0h5GM/E6igokwvsQRTvLcXBnvcIa/d8gZVsO3mWZoGnt4hl/4gI+4CPNPUcUiHuIcb/A1i8zM4Bq/saVVJigFaeIxtsO3V2Ft6ihhB/Nh/ASbOMVNkFNsBEKwENaU7hMoCV7jh+i8fMchvgS9aVvu5eBByoSei8q3gnHMisoyjrdo4EXWWenEo4Rzw4msGiO8wlzQP+Ng0JutazXEetxFaR/qvlEQ+u8IjfaYq+Gl5O19rkNfC/ofHGP/Ps523f2ESEt245Kp5UCmKUudwbudoUrCEiXBVBxC5RiO0sKtWHFv2UibNFFts30KtvU223oShkN37YeOUDfU5XfL6nEy1Mhx87didSP0LUdCsWMNrFP3ejEuiR7pYyln5afob+R9yn4LFAD/AABxpFl+H1QlJXRFWHRkYXRlOmNyZWF0ZQAyMDIxLTA4LTI2VDA4OjMzOjMwKzAwOjAwM+HvGCV0RVh0ZGF0ZTptb2RpZnkAMjAyMS0wOC0yNlQwODozMzozMCswMDowMEK8V6QASUVORK5CYII=
  image/png
  
  
    
    
    
    
    
'

Thanks and best regards
Christian



___
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

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] WFS and Time dimension

[Christian Mayer]

Hi Luciano,

yes, you can use the "filter" URL parameter in your WFS request for
that. By providing an OGC Filter Encoding compliant XML you can filter
your dataset by a date/time column. The slide at [1] will give you a XML
snippet as a kind of starting point (the slides are in German but you
will get the point).

Best regards
Chris

[1] https://meggsimum.github.io/fossgis2021/zeitbasierte-geodaten/#/17

On 27.07.21 17:47, Luciano Castro wrote:
> Hello!
> I'm trying to filter a GetFeature request by the layer's time
> dimension. I know WFS doesn't have a time filter (as WMS does), but is
> there any workaround to do this? Can I query the property configured
> as time dimension, so I can filter the GetFeature request?
>
> -- 
>
>   
>
> Luciano Castro
>
> Software Tester
>
>
> +54 (11) 4342-2976/84
>
> www.spacesur.com 
>
>
>
>
> ___
> 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
>
> If you want to request a feature or an improvement, also see this: 
> https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
>
>
> Geoserver-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
___
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

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

[Geoserver-users] Geopackage Natural Earth Vector Data causes map distortion / disruption

[Christian Mayer]

Hi list,

When I publish a WMS layer based on a vector data set
(ne_10m_admin_0_countries) in a GeoPackage by Natural Earth (download
here [1])  The resulting layer seems to be distorted / disrupted. I
validated the GeoPackage and rendered the same data in QGIS, where
everything looks fine.

Has anyone an idea what could be the reason?

I am using GeoServer 2.18.2

Thanks for any hint.

[1] http://naciscdn.org/naturalearth/packages/natural_earth_vector.gpkg.zip



___
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

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] Rest API - Ingest not supported for mosaics - Add files to an ImageMosaic

[Christian Mayer]

Hi,

not sure if this is exactly what you are looking for but I am doing the
following to add a granule to an existing image mosaic:

Send a HTTP POST request to
http://mygeoserver/workspaces/myworkspace/coveragestores/myCoverageStore/external.imagemosaic
whereas the URL (local files can be referenced with file://) to the new
granule is send in the POST body, e.g. file:///opt/raster_data/myGeotiff.tif

Hope this helps
Chris

On 14.02.21 18:23, Simon Crown wrote:
> The REST endpoint I am using is POST to
> http://localhost:8080/geoserver/rest/imports
>
> To create the ImageMosaic the JSON sent is 
>
> {
> "import" : {
> "targetWorkspace" : {
> "workspace" : {
> "name" : "TEST"
> }
> },
> "data" : {
> "type" : "mosaic",
> "location" : "D:\\PART1"
> }
>    }
> }
> Now in order to add files from a different directory I send the following
> {
> "import" : {
> "targetStore" : {
> "store" : "PART1"
> },
> "targetWorkspace" : {
> "workspace" : {
> "name" : "TEST"
> }
> },
> "data" : {
> "type" : "mosaic",
> "location" : "D:\\PART2"
> }
> }
> }
> The above was copied from a computer that is not connected to the
> internet so I apologize if there are any obvious errors in the JSON,
> Looking at the GeoServer source code I see that the error I am getting
> is thrown in importer.java at initForMosaic.
> On a related note. Is there any way to get GeoServer to log the
> requests it gets from the supplied Web UI. Perhaps I could do this at
> the level of the Jetty web server. This would be a really useful to
> the API documentation.
> Regards,
> Simon Crown
>
> On Sun, Feb 14, 2021 at 10:17 AM Andrea Aime
> mailto:andrea.a...@geo-solutions.it>>
> wrote:
>
> Hi Simon,
> can you please show which requests you've used?
>
> Cheers
> Andrea
>
> On Sun, Feb 14, 2021 at 9:14 AM Simon Crown
> mailto:simonleoncr...@gmail.com>> wrote:
>
> GeoServer 2.18.0 Java 1.8 on Windows
>
> I have succeeded in creating an ImageMosaic store using the
> REST API. This store is located as a single directory in the
> file system. The data are GeoTIFF.
>
> I would like to add new tiles to this store. To do this l add
> a targetStore JSON object to the REST import object. GeoServer
> returns an INIT_ERROR with a message " ingest not supported
> for mosaics"
>
> This seems to indicate that it is not possible to extend a
> mosaic once it has been created. Is this the case or perhaps I
> am calling the REST API incorrectly? 
>
> Note. I previously posted this question to GIS StackExchange
> but it was not answered so I am trying my luck here.
>
>
>
>
> ___
> 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
>
> If you want to request a feature or an improvement, also see
> this:
> 
> https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
>
>
> Geoserver-users@lists.sourceforge.net
> 
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>
>
>
> -- 
>
> Regards, Andrea Aime
>
> == GeoServer Professional Services from the experts! Visit
> http://goo.gl/it488V for more information. == Ing. Andrea Aime
> @geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A
> 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272
> mob: +39 339 8844549 http://www.geo-solutions.it
> http://twitter.com/geosolutions_it
> --- /Con
> riferimento alla normativa sul trattamento dei dati personali
> (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati
> “GDPR”), si precisa che ogni circostanza inerente alla presente
> email (il suo contenuto, gli eventuali allegati, etc.) è un dato
> la cui conoscenza è riservata al/i solo/i destinatario/i indicati
> dallo scrivente. Se il messaggio Le è giunto per errore, è
> tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei
> comunque grato se potesse darmene notizia. This email is intended
> only for the person or entity to which it is addressed and may
> contain information that is privileged, confidential or otherwise
> protected from disclosure. We remin

Re: [Geoserver-users] WFS on the fly transformation to EPSG:3857

[Christian Mayer]

Hi Mark, hi list

I think I found a solution, which works for me, which I want to share.
I checked that GeoServer per default does not use the wanted SRS
definition for the EPSG code of my source SRS (EPSG:31468). This is OK,
since there are several definitions for this SRS. Overwriting the SRS
with the wanted parameters (as described here [1]) did not bring any
effect. The overwritten SRS definition was shown in GeoServer UI, but
the transformation returned still the old (unwanted) values. I verified
the transformation with the reprojection console of GeoServer [2], which
is very useful.
After a while I discovered that the "coordinate operations" in the
transformation process (can be shown in the reprojection console as
well) still use the old parameters. So I decided to overwrite the
"coordinate operations" as documented here [3].

So in m special case I had to change the TOWGS84 parameters for
EPSG:31468. As stated above it was necessary to set these TOWGS84
parameters within a custom "coordinate operations". To do this I added a
file epsg_operations.properties to geoserver_data/user_projections with
the following content (maybe useful as example):

31468,3857=CONCAT_MT[INVERSE_MT[PARAM_MT["Transverse_Mercator",\
  PARAMETER["semi_major", 6377397.155],\
  PARAMETER["semi_minor", 6356078.962818189],\
  PARAMETER["central_meridian", 12.0],\
  PARAMETER["latitude_of_origin", 0.0],\
  PARAMETER["scale_factor", 1.0],\
  PARAMETER["false_easting", 450.0],\
  PARAMETER["false_northing", 0.0]]],\
  PARAM_MT["Ellipsoid_To_Geocentric",\
    PARAMETER["dim", 2],\
    PARAMETER["semi_major", 6377397.155],\
    PARAMETER["semi_minor", 6356078.962818189]],\
  PARAM_MT["Position Vector transformation (geog2D domain)",\
    PARAMETER["dx", 598.1],\
    PARAMETER["dy", 73.7],\
    PARAMETER["dz", 418.2],\
    PARAMETER["ex", 0.202],\
    PARAMETER["ey", 0.045],\
    PARAMETER["ez", -2.455],\
    PARAMETER["ppm", 6.7]],\
  PARAM_MT["Geocentric_To_Ellipsoid",\
    PARAMETER["dim", 2],\
    PARAMETER["semi_major", 6378137.0],\
    PARAMETER["semi_minor", 6356752.314245179]],\
  PARAM_MT["Popular Visualisation Pseudo Mercator",\
    PARAMETER["semi_major", 6378137.0],\
    PARAMETER["semi_minor", 6378137.0],\
    PARAMETER["latitude_of_origin", 0.0],\
    PARAMETER["central_meridian", 0.0],\
    PARAMETER["scale_factor", 1.0],\
    PARAMETER["false_easting", 0.0],\
    PARAMETER["false_northing", 0.0]]]

[1]
https://docs.geoserver.org/stable/en/user/configuration/crshandling/customcrs.html#override-an-official-epsg-code
[2]
https://docs.geoserver.org/stable/en/user/configuration/demos/index.html#demos-reprojectionconsole
[3]
https://docs.geoserver.org/stable/en/user/configuration/crshandling/coordtransforms.html#coordinate-operations

Cheers
Chris

On 01.02.21 08:38, Christian Mayer wrote:
> Hi Mark,
>
> thanks for your answer and the hints with the NTv2. I'll give it a try
> and report back here.
>
> Thanks again
> Chris
>
> On 29.01.21 17:19, Mark Prins wrote:
>> On 29-01-2021 15:03, Christian Mayer wrote:
>>> Hi list,
>>>
>>> I have the following setup: A geometry table in a PostGIS DB with points
>>> having the projection EPSG:31468 [1]. I am publishing the points as WFS
>>> FeatureType and query them in EPSG:3857 [2] by setting srsName=EPSG:3857
>>> in the WFS GetFeature request. The returned WFS points have a coordinate
>>> shift (1-2 meters) compared to the points transformed directly in
>>> PostGIS or with GDAL.
>>>
>>> Here is an example:
>>>
>>> Native point in EPSG:31468 --> 4355155.403, 5512583.018
>>>
>>> Transformed point with GDAL or ST_Transform of PostGIS    -->
>>> 1112006.22028666, 6400063.79411048
>>>
>>> Transformed point as output of the GeoServer WFS request -->
>>> 1112005.8998, 6400065.9514
>>>
>>> Has anyone an idea what is going wrong here? 
>> There appear to be several well known transformation methods available
>> listed at http://epsg.io/31468, GeoServer may be using a less accurate
>> version than other products by default.
>>
>>> Do the SRS definitions in
>>> GeoServer differ from those in PostGIS or GDAL? 
>> debug logging may show which transformation method is used, it's not
>> my expertise but it looks like NTv2 should be used to get results
>> within 1m accuracy, so you may need to add a Grid Shift file to get
>>

Re: [Geoserver-users] WFS on the fly transformation to EPSG:3857

[Christian Mayer]

Hi Mark,

thanks for your answer and the hints with the NTv2. I'll give it a try
and report back here.

Thanks again
Chris

On 29.01.21 17:19, Mark Prins wrote:
> On 29-01-2021 15:03, Christian Mayer wrote:
>> Hi list,
>>
>> I have the following setup: A geometry table in a PostGIS DB with points
>> having the projection EPSG:31468 [1]. I am publishing the points as WFS
>> FeatureType and query them in EPSG:3857 [2] by setting srsName=EPSG:3857
>> in the WFS GetFeature request. The returned WFS points have a coordinate
>> shift (1-2 meters) compared to the points transformed directly in
>> PostGIS or with GDAL.
>>
>> Here is an example:
>>
>> Native point in EPSG:31468 --> 4355155.403, 5512583.018
>>
>> Transformed point with GDAL or ST_Transform of PostGIS    -->
>> 1112006.22028666, 6400063.79411048
>>
>> Transformed point as output of the GeoServer WFS request -->
>> 1112005.8998, 6400065.9514
>>
>> Has anyone an idea what is going wrong here? 
>
> There appear to be several well known transformation methods available
> listed at http://epsg.io/31468, GeoServer may be using a less accurate
> version than other products by default.
>
>> Do the SRS definitions in
>> GeoServer differ from those in PostGIS or GDAL? 
>
> debug logging may show which transformation method is used, it's not
> my expertise but it looks like NTv2 should be used to get results
> within 1m accuracy, so you may need to add a Grid Shift file to get
> better results
>
> see also:
> https://docs.geoserver.org/stable/en/user/configuration/crshandling/coordtransforms.html
>
> -M
>
>
> ___
> 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
>
> If you want to request a feature or an improvement, also see this:
> https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
>
>
>
> Geoserver-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-users


___
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

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

[Geoserver-users] WFS on the fly transformation to EPSG:3857

[Christian Mayer]

Hi list,

I have the following setup: A geometry table in a PostGIS DB with points
having the projection EPSG:31468 [1]. I am publishing the points as WFS
FeatureType and query them in EPSG:3857 [2] by setting srsName=EPSG:3857
in the WFS GetFeature request. The returned WFS points have a coordinate
shift (1-2 meters) compared to the points transformed directly in
PostGIS or with GDAL.

Here is an example:

Native point in EPSG:31468 --> 4355155.403, 5512583.018

Transformed point with GDAL or ST_Transform of PostGIS    -->
1112006.22028666, 6400063.79411048

Transformed point as output of the GeoServer WFS request -->
1112005.8998, 6400065.9514

Has anyone an idea what is going wrong here? Do the SRS definitions in
GeoServer differ from those in PostGIS or GDAL? Or is this a known issue
in GeoServer? I searched around but could not find any hint. Any
hint/help is very much appreciated.

GeoServer version used is 2.17.4.

Thanks in advance
Chris

[1] http://epsg.io/31468
[2] http://epsg.io/3857



___
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

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

[Geoserver-users] REST-API creation of FeatureType based on remote WFS

[Christian Mayer]

Hi all,

I am doing the following via the GeoServer REST-API: I create a
datastore based on a remote WFS [1]. This works fine. Then I try to
publish a FeatureType of the remote WFS in my GeoServer by POSTing
against /rest/workspaces//datastores//featuretypes.
This gives me the error "Trying to create new feature type inside the
store, but no attributes were specified".
Due to some research I came to the point that the "nativeName" I
provided in my POST body did not match with the one GeoServer expects.
The original one of the remote WFS is "osm: osm-fuel" and GeoServer
expects "osm_osm-fuel". So the ":" has been replaced with a "_". Is that
a reliable pattern?

GeoServer version used is 2.17.1.

Thanks in advance for any response.

Cheers
Chris

[1] https://ows-demo.terrestris.de/geoserver/osm/wfs



___
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

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] Image mosaic extension for v2.18.0

[Christian Mayer]

Hi Ian and Daniele,

thank you very much for your help! Taking the community module of
"imagemosaic-jdbc" solved this for me.

All the best
Chris

On 07.10.20 09:29, Daniele Romagnoli wrote:
> Morning Christian,
> the imagemosaic-jdbc plugin has been moved back to "community" modules.
> You will find it in the nightly snapshots download area:
> https://build.geoserver.org/geoserver/2.18.x/community-latest/
>
> The direct link:
> https://build.geoserver.org/geoserver/2.18.x/community-latest/geoserver-2.18-SNAPSHOT-imagemosaic-jdbc-plugin.zip
>
> Hope this helps.
> Best Regards,
> Daniele
>
>
>
>
> On Wed, Oct 7, 2020 at 7:47 AM Christian Mayer  <mailto:ml...@meggsimum.de>> wrote:
>
> Hi everybody,
>
> I am currently updating my GeoServer instances to version 2.18.0
> (thanks
> to everybody contributing and making this real!). I am missing the
> "imagemosaic-jdbc" extension at
> 
> https://sourceforge.net/projects/geoserver/files/GeoServer/2.18.0/extensions/.
> Did I oversee anything or has the location changed for this?
>
> Thanks for any hint.
>
> Cheers
> Chris
>
>
>
> ___
> 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
>
> If you want to request a feature or an improvement, also see this:
> 
> https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
>
>
> Geoserver-users@lists.sourceforge.net
> <mailto:Geoserver-users@lists.sourceforge.net>
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>
>
>
> -- 
> Regards,
> Daniele Romagnoli
> ==
> GeoServer Professional Services from the experts! Visit
> http://goo.gl/it488V for more information.
> ==
>
> Ing. Daniele Romagnoli
> Senior Software Engineer
>
> GeoSolutions S.A.S.
> Via di Montramito 3/A
> 55054  Massarosa (LU)
> Italy
> phone: +39 0584 962313
> fax:      +39 0584 1660272
>
> http://www.geo-solutions.it
> http://twitter.com/geosolutions_it
>
> ---
>
> Con riferimento alla normativa sul trattamento dei dati personali
> (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati
> “GDPR”), si precisa che ogni circostanza inerente alla presente email
> (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui
> conoscenza è riservata al/i solo/i destinatario/i indicati dallo
> scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a
> cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato
> se potesse darmene notizia.
>
> This email is intended only for the person or entity to which it is
> addressed and may contain information that is privileged, confidential
> or otherwise protected from disclosure. We remind that - as provided
> by European Regulation 2016/679 “GDPR” - copying, dissemination or use
> of this e-mail or the information herein by anyone other than the
> intended recipient is prohibited. If you have received this email by
> mistake, please notify us immediately by telephone or e-mail.
___
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

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

[Geoserver-users] Image mosaic extension for v2.18.0

[Christian Mayer]

Hi everybody,

I am currently updating my GeoServer instances to version 2.18.0 (thanks
to everybody contributing and making this real!). I am missing the
"imagemosaic-jdbc" extension at
https://sourceforge.net/projects/geoserver/files/GeoServer/2.18.0/extensions/.
Did I oversee anything or has the location changed for this?

Thanks for any hint.

Cheers
Chris



___
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

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] Delete user with REST api?

[Christian Mayer]

Hi Gus,

I checked and I also could not delete a user by the REST API (tested
with GeoServer v2.17.1). I could load the users by doing a HTTP GET request

http://localhost:8080/geoserver/rest/security/usergroup/users

If I try to remove a user (user is existing) by HTTP DELETE against
http://localhost:8080/geoserver/rest/security/usergroup/users/testDeleteMe
I get

"The origin server did not find a current representation for the target
resource or is not willing to disclose that one exists".

The APIs here [1] do not work at all.

Maybe we both are missing something or this is a bug? Any help / hint
welcome.

Regards
Chris

[1] https://docs.geoserver.org/stable/en/api/#1.0.0/usergroup.yaml

Am 29.06.20 um 13:39 schrieb Thuser - Services:
> Hi List,
>
> I've been able to create users with the REST api, now I want to be
> able to delete them.  Have tried to follow docs
> from https://docs.geoserver.org/stable/en/user/rest/api/userrole.html and 
> https://docs.geoserver.org/latest/en/api/#1.0.0/usergroup.yaml 
> but so far no success - have tried with 2.16 and 2.17.  Does anyone
> have a working example?
>
> Thanks,
> Gus
>
>
>
>
> ___
> 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
>
> If you want to request a feature or an improvement, also see this: 
> https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
>
>
> Geoserver-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
___
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

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] Heatmap rendering with fixed BBOX

[Christian Mayer]

Hi Emilio,

thanks for your response. If I got you right I just want to do it the
other way round. I will publish a heatmap based on data for a region
(let's say a whole country) and in case the user queries the WMS layer
with a BBOX for a sub-region (let's say a city in this country) the
heatmap should NOT be re-created / re-rendered based on the city's data.
It should still be the one created based on country data.

Regards
Christian

Am 20.05.20 um 21:21 schrieb Emilio Lahr-Vivaz:
> If you want to return the full WMS view-port, but only render the
> points inside a specific bbox, you might be able to accomplish that by
> setting a default filter (containing your bbox) on the layer
> configuration in geoserver.
>
> Thanks,
>
> Emilio
>
> On 5/20/20 10:27 AM, Christian Mayer wrote:
>> Hi Ian, Olivier and Jim,
>>
>> thank you very much for your help by sharing your thoughts on this.
>>
>> So it seems it needs some external (pre-)processing or adaption of
>> code. For me it seems that preprocessing by an external tool is the
>> more suitable way. I'll dig a bit into this and report back here once
>> I have a running solution.
>>
>> Thanks again
>> Chris
>>
>> Am 19.05.20 um 19:10 schrieb Jim Hughes:
>>> Hi Chris,
>>>
>>> One approach is to render the heatmap at a suitable resolution and
>>> then save the result as a format that GeoServer can render (such as
>>> GeoTiff).  That GeoTiff can be registered as a new layer, and you can
>>> serve up that layer.  Users/clients would be able to zoom around that
>>> layer and set a consistent picture (e.g., without local scaling).
>>>
>>> I was involved in a project where we let users make such a query in an
>>> ad hoc manner and then we saved the GeoTiff using a custom WPS (that
>>> did some of the underlying wiring).
>>>
>>> Alternatively, you could re-write the DensityProcess slightly to work
>>> slightly differently.
>>>
>>> I believe your use case would require some external tools or some code
>>> changes.  (That said, maybe I'm missing something clever!)
>>>
>>> Cheers,
>>>
>>> Jim
>>>
>>> On 5/19/2020 8:53 AM, Christian Mayer wrote:
>>>> Hi list,
>>>>
>>>> does anyone know if there is a possibility to render a heatmap for a
>>>> fixed BBOX of the underlying dataset?
>>>> To be more concrete: I have a set of point geometries for which I want
>>>> to have heatmap and expose this as WMS. I want to ensure that the
>>>> heatmap is rendered based on the points within a fixed BBOX and not
>>>> the
>>>> BBOX of the WMS request. At least it looked to me like GeoServer
>>>> heatmap
>>>> rendering transformation is taking the WMS Request BBOX as a
>>>> calculation
>>>> base.
>>>>
>>>> Thanks in advance for any hint / help
>>>> Chris
>>>>
>>>>
>>>>
>>>> ___
>>>> 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
>>>>
>>>> If you want to request a feature or an improvement, also see this:
>>>> https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
>>>>
>>>>
>>>>
>>>> Geoserver-users@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>>>
>>> ___
>>> 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
>>>
>>> If you want to request a feature or an improvement, also see this:
>>> https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
>>>
>>>
&

Re: [Geoserver-users] Heatmap rendering with fixed BBOX

[Christian Mayer]

Hi Ian, Olivier and Jim,

thank you very much for your help by sharing your thoughts on this.

So it seems it needs some external (pre-)processing or adaption of code. For me 
it seems that preprocessing by an external tool is the more suitable way. I'll 
dig a bit into this and report back here once I have a running solution.

Thanks again
Chris

Am 19.05.20 um 19:10 schrieb Jim Hughes:
> Hi Chris,
>
> One approach is to render the heatmap at a suitable resolution and
> then save the result as a format that GeoServer can render (such as
> GeoTiff).  That GeoTiff can be registered as a new layer, and you can
> serve up that layer.  Users/clients would be able to zoom around that
> layer and set a consistent picture (e.g., without local scaling).
>
> I was involved in a project where we let users make such a query in an
> ad hoc manner and then we saved the GeoTiff using a custom WPS (that
> did some of the underlying wiring).
>
> Alternatively, you could re-write the DensityProcess slightly to work
> slightly differently.
>
> I believe your use case would require some external tools or some code
> changes.  (That said, maybe I'm missing something clever!)
>
> Cheers,
>
> Jim
>
> On 5/19/2020 8:53 AM, Christian Mayer wrote:
>> Hi list,
>>
>> does anyone know if there is a possibility to render a heatmap for a
>> fixed BBOX of the underlying dataset?
>> To be more concrete: I have a set of point geometries for which I want
>> to have heatmap and expose this as WMS. I want to ensure that the
>> heatmap is rendered based on the points within a fixed BBOX and not the
>> BBOX of the WMS request. At least it looked to me like GeoServer heatmap
>> rendering transformation is taking the WMS Request BBOX as a calculation
>> base.
>>
>> Thanks in advance for any hint / help
>> Chris
>>
>>
>>
>> ___
>> 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
>>
>> If you want to request a feature or an improvement, also see this:
>> https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
>>
>>
>> Geoserver-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>
>
> ___
> 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
>
> If you want to request a feature or an improvement, also see this:
> https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
>
>
>
> Geoserver-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-users


___
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

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

[Geoserver-users] Heatmap rendering with fixed BBOX

[Christian Mayer]

Hi list,

does anyone know if there is a possibility to render a heatmap for a
fixed BBOX of the underlying dataset?
To be more concrete: I have a set of point geometries for which I want
to have heatmap and expose this as WMS. I want to ensure that the
heatmap is rendered based on the points within a fixed BBOX and not the
BBOX of the WMS request. At least it looked to me like GeoServer heatmap
rendering transformation is taking the WMS Request BBOX as a calculation
base.

Thanks in advance for any hint / help
Chris



___
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

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users