[Geoserver-users] MBStyle Extension - broken?

[Johannes Weskamm]

Hi,

I am struggling with the MBStyle extension. I only want to use it to 
filter the data from the database to reduce the size of the delivered 
vector tiles.


Therefore i copy the style from the client to geoserver and apply it to 
the data source layers, so that no unnecessary data is transferred.


The idea works fine, if i only have a single layer in the style document.

But when i use multiple layers, strange things happen.

It may happen that data ist not filtered, even if there is a filter 
applied to a layer. But the most important thing is that data is not 
delivered at all, if it is not listed at the top of the layers array 
(which should, as the spec says, be the bottom layer of my map).



The attached example has the behaviour that the roads layer is not 
served (buildings work). If i remove the buildings layer, roads layer 
starts to work.


If i move the roads layer on top of the buildings layer, the roads layer 
works. If i set the "visible" property of the buildings layer to 
"hidden", the roads layer work.



To conclude, it seems the the extension can only handle a single layer 
properly, or am i doing something terribly wrong?



Thanks for ideas and answers,

Johannes



{
  "version": 8,
  "name": "Empty Style",
  "metadata": {"maputnik:renderer": "mbgljs"},
  "center": [50.73926, 7.11514],
  "zoom": 14,
  "sources": {
    ...
  },
  "sprite": "",
  "glyphs": 
"https://orangemug.github.io/font-glyphs/glyphs/{fontstack}/{range}.pbf";,

  "layers": [
    {
  "id": "buildings",
  "type": "fill",
  "source": "buildings",
  "source-layer": "vector_osm_buildings",
  "minzoom": 22,
  "maxzoom": 24,
  "layout": {"visibility": "visible"},
  "paint": {
    "fill-color": {
  "stops": [
    [11, "rgba(210, 208, 208, 0)"],
    [19, "rgba(203, 203, 203, 1)"]
  ]
    },
    "fill-outline-color": {
  "stops": [
    [10, "rgba(189, 189, 189, 0)"],
    [19, "rgba(189, 189, 189, 1)"]
  ]
    },
    "fill-opacity": 0.5
  }
    },
    {
  "id": "roads outline",
  "type": "line",
  "source": "roads",
  "source-layer": "vector_osm_roads",
  "minzoom": 11,
  "maxzoom": 24,
  "filter": [
    "any",
    [
      "in",
  "type",
  "primary",
  "secondary",
  "tertiary",
  "residential",
  "unclassified"
    ]
  ],
  "layout": {
    "visibility": "visible",
    "line-cap": "round",
    "line-join": "miter"
  },
  "paint": {
    "line-color": "rgba(61, 61, 61, 1)",
    "line-blur": 1,
    "line-width": 3,
    "line-opacity": {"stops": [[11, 0], [19, 1]]}
  }
    },

  ],
  "id": "7v910ggmu"
}

--
Dipl.-Geogr. Johannes Weskamm
  — Anwendungsentwickler —

  terrestris GmbH & Co. KG
  Kölnstraße 99
  53111 Bonn

  Tel: +49 (0)228 / 96 28 99 -51
  Fax: +49 (0)228 / 96 28 99 -57

  Email: wesk...@terrestris.de
  Web: https://www.terrestris.de

  Amtsgericht Bonn, HRA 6835
  Komplementärin: terrestris Verwaltungsgesellschaft mbH
  vertreten durch: Torsten Brassat, Marc Jansen
  
  Informationen über Ihre gespeicherten Daten finden Sie auf

  unserer Homepage unter folgendem Link:
  https://www.terrestris.de/datenschutzerklaerung/



___
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] Geoserver CSS extension 404

[Johannes Weskamm]

Hi,


"Master" changed to "main", so the URL now is

https://build.geoserver.org/geoserver/main/ext-latest/geoserver-2.20-SNAPSHOT-css-plugin.zip


Greetings,

Johannes


Am 14.04.21 um 11:08 schrieb Michael Seiwald-McCarty:
>
> Hi,
>
>  
>
> It seems that the download URL for the CSS extension
> (https://build.geoserver.org/geoserver/master/ext-latest/geoserver-2.19-SNAPSHOT-css-plugin.zip
> )
> returns 404.
>
>  
>
> Can anyone help with that? Is there an alternate URL?
>
>  
>
> Kind regards,
>
> Michael
>
> *Michael Seiwald-McCarty*
> Smartify IT Solutions GmbH | Büro München | Leopoldstraße 18 | 80802
> München | Deutschland
> Telefon +49 89 5880098-25 | Fax +49 (0)89 588 00 98-9
> Mobil +49 (0)151 29 25 75 13 | E-Mail
> michael.seiwald-mcca...@smartify-it.de
> 
>
> Smartify IT Solutions GmbH | Leopoldstraße 18 | 80802 München |
> Deutschland
> Geschäftsführer: Dr. Tobias Möhlmann, Nicolai Foerster, Niklas Hofferbert
> Sitz München | Amtsgericht München HRB 244315
>
>
>
> ___
> 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] Vector Tile very slow rendering

[Johannes Weskamm]

Yes, you need to use your SLD connected to the layer in order to filter
out features, using Min- and MaxScaleDenominators or filters.

Styling in SLD obviously does not matter in this case.


Greetings,

Johannes


> this is definitely what I wanna do, but how can I do it? I could not find
> much in GWC documentation. Do you mean using SLD perhaps?
>
>
>
> --
> Sent from: http://osgeo-org.1560.x6.nabble.com/GeoServer-User-f3786390.html
>
>
> ___
> 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] Request for mvt vectortiles leads to "Problem communicating with GeoServer"

[Johannes Weskamm]

This is not a solution, as the client rendering the tiles does not know
what scaledenominators are set in the sld.

The behaviour should be to not serve any features in the tiles for that
specific layer, but not responding with an code 400.

As i am using a grouplayer, there is in fact a demand to render features
in that scalerange that are coming from other layers, that have a valid
salerange for that request.


Greetings,

Johannes

Am 22.05.19 um 15:53 schrieb Ian Turton:
> The solution is to not request tiles outside the specified range.
>
> Ian
>
> On Wed, 22 May 2019 at 14:06, Johannes Weskamm  <mailto:wesk...@terrestris.de>> wrote:
>
> Hi,
>
>
> Thanks, but the problem is, i do not generate that query by
> myself, its
> seems to be the code (GeoServer / GeoWebCache / MVT Vectortiles
> Extension).
>
> The layer is published as simple table from the database (also checked
> if using an sql view differs, but its the same problem).
>
> So the question is, where does this query come from?
>
> It seems to be related to not matching any scaledenominators in
> the SLD
> somehow...
>
>
>
> Am 22.05.19 um 14:40 schrieb DEGRÈVE Benoît:
> > Johannes,
> >
> > There's indeed a syntax problem in your SQL just between the 1st
> SELECT  and the 1st FROM : SQL expect a list of fields , or a " *
> "You must select something...
> >
> > SELECT FROM (SELECT * FROM osm_waterareas
> >     ) as "vtable" WHERE 0 = 1
> >
> > Benoît DEGRÈVE
>     > Risques sous-sols et cartographie
> > Bachelier en gestion de données et cartographie
> >
> >
> > -Message d'origine-
> > De : Johannes Weskamm [mailto:wesk...@terrestris.de
> <mailto:wesk...@terrestris.de>]
> > Envoyé : mercredi 22 mai 2019 10:29
> > À : GeoServer Users
> > Objet : [Geoserver-users] Request for mvt vectortiles leads to
> "Problem communicating with GeoServer"
> >
> > Hi all,
> >
> >
> > I have troubles getting Mapbox vectortiles from GeoServer in some
> > circumstances:
> >
> > I am using a grouplayer with several layers from a PostGIS DB
> (Postgres
> > 9.3 and PostGIS 2.1.2) in it.
> >
> > The layer themselves are working fine when previewed / used as WMS.
> >
> > But when i request the layer as vectortile, GeoWebCache answers
> > sometimes with "400: Problem communicating with GeoServer".
> >
> > I found out that the problem only occurs, when i use an SLD with
> Min and
> > MaxScaledenominator and when i request tiles outside that range.
> >
> > All tiles in that scalerange are delviered fine.
> >
> > The problem exists in three different GeoServer versions i have
> tested
> > (2.12.1, 2.14.3, 2.15.1).
> >
> >
> > The error that happens from GeoServer Log is at the end of this
> mail.
> >
> > The interesting part is, it think, "PSQLException: ERROR: syntax
> error
> > at or near "FROM"
> >
> > I had a look at the postgres log which gives a better idea:
> >
> >
> > 2019-05-22 10:26:48 CEST ERROR:  syntax error at or near "FROM" at
> > character 8
> > 2019-05-22 10:26:48 CEST STATEMENT:  SELECT FROM (SELECT * FROM
> > osm_waterareas
> >     ) as "vtable" WHERE 0 = 1
> >
> >
> > This is indeed an invalid statement. Any ideas where this may
> come from?
> >
> > Thanks!
> >
> >
> >
> >
> 
> http://136.243.46.241/geoserver/gwc/service/tms/1.0.0/osm:osm_vector@EPSG:3857@pbf/9/268/342.pbf
> > 2019-05-22 10:14:56,280 ERROR [geowebcache.GeoWebCacheDispatcher] -
> > Request failed
> > org.geowebcache.GeoWebCacheException: Problem communicating with
> GeoServer
> >     at
> >
> 
> org.geoserver.gwc.layer.GeoServerTileLayer.getMetatilingReponse(GeoServerTileLayer.java:644)
> >     at
> >
> 
> org.geoserver.gwc.layer.GeoServerTileLayer.getTile(GeoServerTileLayer.java:579)
> >     at
> org.geowebcache.util.ResponseUtils.writeTile(ResponseUtils.java:102)
> >     at
> >
> 
> org.geowebcache.GeoWebCacheDispatcher.handleServiceRequest(GeoWebCacheDispatcher.java:422)
> >     at
> >

Re: [Geoserver-users] Request for mvt vectortiles leads to "Problem communicating with GeoServer"

[Johannes Weskamm]

Hi,


Thanks, but the problem is, i do not generate that query by myself, its
seems to be the code (GeoServer / GeoWebCache / MVT Vectortiles Extension).

The layer is published as simple table from the database (also checked
if using an sql view differs, but its the same problem).

So the question is, where does this query come from?

It seems to be related to not matching any scaledenominators in the SLD
somehow...



Am 22.05.19 um 14:40 schrieb DEGRÈVE Benoît:
> Johannes,
>
> There's indeed a syntax problem in your SQL just between the 1st SELECT  and 
> the 1st FROM : SQL expect a list of fields , or a " * "You must select 
> something...
>
> SELECT FROM (SELECT * FROM osm_waterareas
> ) as "vtable" WHERE 0 = 1
>
> Benoît DEGRÈVE
> Risques sous-sols et cartographie
> Bachelier en gestion de données et cartographie
>
>
> -Message d'origine-
> De : Johannes Weskamm [mailto:wesk...@terrestris.de] 
> Envoyé : mercredi 22 mai 2019 10:29
> À : GeoServer Users
> Objet : [Geoserver-users] Request for mvt vectortiles leads to "Problem 
> communicating with GeoServer"
>
> Hi all,
>
>
> I have troubles getting Mapbox vectortiles from GeoServer in some
> circumstances:
>
> I am using a grouplayer with several layers from a PostGIS DB (Postgres
> 9.3 and PostGIS 2.1.2) in it.
>
> The layer themselves are working fine when previewed / used as WMS.
>
> But when i request the layer as vectortile, GeoWebCache answers
> sometimes with "400: Problem communicating with GeoServer".
>
> I found out that the problem only occurs, when i use an SLD with Min and
> MaxScaledenominator and when i request tiles outside that range.
>
> All tiles in that scalerange are delviered fine.
>
> The problem exists in three different GeoServer versions i have tested
> (2.12.1, 2.14.3, 2.15.1).
>
>
> The error that happens from GeoServer Log is at the end of this mail.
>
> The interesting part is, it think, "PSQLException: ERROR: syntax error
> at or near "FROM"
>
> I had a look at the postgres log which gives a better idea:
>
>
> 2019-05-22 10:26:48 CEST ERROR:  syntax error at or near "FROM" at
> character 8
> 2019-05-22 10:26:48 CEST STATEMENT:  SELECT FROM (SELECT * FROM
> osm_waterareas
>     ) as "vtable" WHERE 0 = 1
>
>
> This is indeed an invalid statement. Any ideas where this may come from?
>
> Thanks!
>
>
>
> http://136.243.46.241/geoserver/gwc/service/tms/1.0.0/osm:osm_vector@EPSG:3857@pbf/9/268/342.pbf
> 2019-05-22 10:14:56,280 ERROR [geowebcache.GeoWebCacheDispatcher] -
> Request failed
> org.geowebcache.GeoWebCacheException: Problem communicating with GeoServer
>     at
> org.geoserver.gwc.layer.GeoServerTileLayer.getMetatilingReponse(GeoServerTileLayer.java:644)
>     at
> org.geoserver.gwc.layer.GeoServerTileLayer.getTile(GeoServerTileLayer.java:579)
>     at org.geowebcache.util.ResponseUtils.writeTile(ResponseUtils.java:102)
>     at
> org.geowebcache.GeoWebCacheDispatcher.handleServiceRequest(GeoWebCacheDispatcher.java:422)
>     at
> org.geowebcache.GeoWebCacheDispatcher.handleRequestInternal(GeoWebCacheDispatcher.java:275)
>     at
> org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:177)
>     at
> org.geoserver.gwc.dispatch.GwcServiceProxy.dispatch(GwcServiceProxy.java:82)
>     at sun.reflect.GeneratedMethodAccessor247.invoke(Unknown Source)
>     at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>     at java.lang.reflect.Method.invoke(Method.java:498)
>     at org.geoserver.ows.Dispatcher.execute(Dispatcher.java:877)
>     at
> org.geoserver.ows.Dispatcher.handleRequestInternal(Dispatcher.java:264)
>     at
> org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:177)
>     at
> org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:52)
>     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.doGet(FrameworkServlet.java:890)
>     at javax.servlet.http.HttpServlet.service(HttpServlet.java:620)
>     at
> org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:875)
>     at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
>     at
> org.apache.ca

[Geoserver-users] Request for mvt vectortiles leads to "Problem communicating with GeoServer"

[Johannes Weskamm]

Hi all,


I have troubles getting Mapbox vectortiles from GeoServer in some
circumstances:

I am using a grouplayer with several layers from a PostGIS DB (Postgres
9.3 and PostGIS 2.1.2) in it.

The layer themselves are working fine when previewed / used as WMS.

But when i request the layer as vectortile, GeoWebCache answers
sometimes with "400: Problem communicating with GeoServer".

I found out that the problem only occurs, when i use an SLD with Min and
MaxScaledenominator and when i request tiles outside that range.

All tiles in that scalerange are delviered fine.

The problem exists in three different GeoServer versions i have tested
(2.12.1, 2.14.3, 2.15.1).


The error that happens from GeoServer Log is at the end of this mail.

The interesting part is, it think, "PSQLException: ERROR: syntax error
at or near "FROM"

I had a look at the postgres log which gives a better idea:


2019-05-22 10:26:48 CEST ERROR:  syntax error at or near "FROM" at
character 8
2019-05-22 10:26:48 CEST STATEMENT:  SELECT FROM (SELECT * FROM
osm_waterareas
    ) as "vtable" WHERE 0 = 1


This is indeed an invalid statement. Any ideas where this may come from?

Thanks!



http://136.243.46.241/geoserver/gwc/service/tms/1.0.0/osm:osm_vector@EPSG:3857@pbf/9/268/342.pbf
2019-05-22 10:14:56,280 ERROR [geowebcache.GeoWebCacheDispatcher] -
Request failed
org.geowebcache.GeoWebCacheException: Problem communicating with GeoServer
    at
org.geoserver.gwc.layer.GeoServerTileLayer.getMetatilingReponse(GeoServerTileLayer.java:644)
    at
org.geoserver.gwc.layer.GeoServerTileLayer.getTile(GeoServerTileLayer.java:579)
    at org.geowebcache.util.ResponseUtils.writeTile(ResponseUtils.java:102)
    at
org.geowebcache.GeoWebCacheDispatcher.handleServiceRequest(GeoWebCacheDispatcher.java:422)
    at
org.geowebcache.GeoWebCacheDispatcher.handleRequestInternal(GeoWebCacheDispatcher.java:275)
    at
org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:177)
    at
org.geoserver.gwc.dispatch.GwcServiceProxy.dispatch(GwcServiceProxy.java:82)
    at sun.reflect.GeneratedMethodAccessor247.invoke(Unknown Source)
    at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    at org.geoserver.ows.Dispatcher.execute(Dispatcher.java:877)
    at
org.geoserver.ows.Dispatcher.handleRequestInternal(Dispatcher.java:264)
    at
org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:177)
    at
org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:52)
    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.doGet(FrameworkServlet.java:890)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:620)
    at
org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:875)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
    at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
    at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
    at
org.geoserver.filters.ThreadLocalsCleanupFilter.doFilter(ThreadLocalsCleanupFilter.java:26)
    at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
    at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
    at
org.geoserver.filters.SpringDelegatingFilter$Chain.doFilter(SpringDelegatingFilter.java:69)
    at
org.geoserver.wms.animate.AnimatorFilter.doFilter(AnimatorFilter.java:73)
    at
org.geoserver.filters.SpringDelegatingFilter$Chain.doFilter(SpringDelegatingFilter.java:66)
    at
org.geoserver.filters.SpringDelegatingFilter.doFilter(SpringDelegatingFilter.java:41)
    at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
    at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
    at
org.geoserver.platform.AdvancedDispatchFilter.doFilter(AdvancedDispatchFilter.java:37)
    at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
    at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
    at
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:320)
    at
org.geoserver.security.filter.GeoServerCompositeFilter$NestedFilterChain.doFilter(GeoServerCompositeFilter.java:70)
    at
org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.ja

Re: [Geoserver-users] SLD styling in production environment

[Johannes Weskamm]

Hi,

As far as i know, QGIS Style and Mapbox Style parsing is going to be
implemented next.

CSS and YSLD are missing, but pull request are welcome! :-)


Greetings,

Johannes



Am 09.11.2018 um 09:05 schrieb Arnaud L.:
> Le 08/11/2018 à 17:34, Johannes Weskamm a écrit :
>> Just want to add another option for a simple, what you see is what you
>> get SLD-editor:
>>
>> Demo: https://terrestris.github.io/geostyler/
>>
>> Code and documentation: https://github.com/terrestris/geostyler
>>
>> Introduction:
>> https://www.terrestris.de/en/2018/08/06/das-projekt-geostyler/
>>
>> News: https://www.terrestris.de/en/2018/09/12/neues-vom-geostyler/
>>
>>
>> This project is still a work in progress, but it think its already
>> usable!
>
> Very nice project !
> Are there by chance any plans for YSLD/CSS formats ?
>
>
> Cheers
>
> -- 
> Arnaud



___
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] SLD styling in production environment

[Johannes Weskamm]

Hi,


Just want to add another option for a simple, what you see is what you
get SLD-editor:

Demo: https://terrestris.github.io/geostyler/

Code and documentation: https://github.com/terrestris/geostyler

Introduction: https://www.terrestris.de/en/2018/08/06/das-projekt-geostyler/

News: https://www.terrestris.de/en/2018/09/12/neues-vom-geostyler/


This project is still a work in progress, but it think its already usable!

Regards,

Johannes Weskamm




___
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] Configuring WMS-Time range for capabilities document

[Johannes Weskamm]

Hi,

You are right, the queries itself could be fast. I identified my
SQL-View of the layer to be the problem.

When requesting the layer via WMS, the resulting SQL query made by
geoserver will always contain an AND filter for the timestamp, which
makes the service working fast.

But when requesting capabilities, the SQL View seems not not be filtered
(for obvious reasons) which then takes a lot of time.

So i will discuss this with my colleagues, way may have some capacity
left to develop such a feature (manual configuration) for geoserver.

Maybe you could give me a hint where (files / classes) development for
this should start off.

Thanks,

Johannes


Am 31.10.2018 um 11:45 schrieb Andrea Aime:
> Hi,
> there is indeed no way to configure GeoServer with static time domain
> values (could be done, needs coding, preventive discussion on the
> devel list and then implementation according to the published
> contribution rules).
> However, finding min and max should be fast if you have an index on
> the time column (unless the database in question is
> Oracle, in that case there are fixes to speed that up on the
> development branch only)
>
> Cheers
> Andrea
>
>
> On Wed, Oct 31, 2018 at 11:41 AM Johannes Weskamm
> mailto:wesk...@terrestris.de>> wrote:
>
> I have already checked that, and tried the different options, sadly it
> does not change the time it takes to generate the capabilities
> document.
>
> I tried dynamic values and also hardcoded timestamps, the result
> is the
> same (timeouts).
>
> I think geoserver is still asking the database for the min and max
> values.
>
>
>
> Am 31.10.2018 um 11:28 schrieb br...@frogmouth.net
> <mailto:br...@frogmouth.net>:
> > How are you specifying the Default value strategy?
> >
> > If you change that to Reference Value, you can use a form like
> > fromValue/toValue. It's also possible to use relative times like
> > P1M/PRESENT, but note that the reference value is copied
> verbatim into the
> > capabilities document, which might not be what you want.
> (Adapted from
> >
> 
> https://docs.geoserver.org/stable/en/user/data/webadmin/layers.html#data-web
> > admin-layers-edit-dimensions)
> >
> > Brad
> >
> >
>
> -- 
>   Dipl.-Geogr. Johannes Weskamm
>   — Anwendungsentwickler —
>
>   terrestris GmbH & Co. KG
>   Kölnstraße 99
>   53111 Bonn
>
>   Tel: +49 (0)228 / 96 28 99 -555
>   Fax: +49 (0)228 / 96 28 99 -57
>
>   Email: wesk...@terrestris.de <mailto:wesk...@terrestris.de>
>   Web: https://www.terrestris.de
>
>   Amtsgericht Bonn, HRA 6835
>   Komplementärin: terrestris Verwaltungsgesellschaft mbH
>   vertreten durch: Torsten Brassat, Marc Jansen,
>   Hinrich Paulsen, Till Adams
>
>   Informationen über Ihre gespeicherten Daten finden Sie auf
>   unserer Homepage unter folgendem Link:
>   https://www.terrestris.de/datenschutzerklaerung/
>
>
>
> ___
> 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, 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 

Re: [Geoserver-users] Configuring WMS-Time range for capabilities document

[Johannes Weskamm]

I have already checked that, and tried the different options, sadly it
does not change the time it takes to generate the capabilities document.

I tried dynamic values and also hardcoded timestamps, the result is the
same (timeouts).

I think geoserver is still asking the database for the min and max values.



Am 31.10.2018 um 11:28 schrieb br...@frogmouth.net:
> How are you specifying the Default value strategy?
>
> If you change that to Reference Value, you can use a form like
> fromValue/toValue. It's also possible to use relative times like
> P1M/PRESENT, but note that the reference value is copied verbatim into the
> capabilities document, which might not be what you want. (Adapted from
> https://docs.geoserver.org/stable/en/user/data/webadmin/layers.html#data-web
> admin-layers-edit-dimensions)
>
> Brad
>
>

-- 
  Dipl.-Geogr. Johannes Weskamm
  — Anwendungsentwickler —

  terrestris GmbH & Co. KG
  Kölnstraße 99
  53111 Bonn

  Tel: +49 (0)228 / 96 28 99 -555
  Fax: +49 (0)228 / 96 28 99 -57

  Email: wesk...@terrestris.de
  Web: https://www.terrestris.de

  Amtsgericht Bonn, HRA 6835
  Komplementärin: terrestris Verwaltungsgesellschaft mbH
  vertreten durch: Torsten Brassat, Marc Jansen, 
  Hinrich Paulsen, Till Adams
  
  Informationen über Ihre gespeicherten Daten finden Sie auf
  unserer Homepage unter folgendem Link: 
  https://www.terrestris.de/datenschutzerklaerung/ 



___
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] Configuring WMS-Time range for capabilities document

[Johannes Weskamm]

Hi list,


I am trying to configure the range of time my WMS-Time enabled Layer can
be used for.

The problem i have is, that requesting the capabilities document slows
down the machine for several minutes and i receive a timeout.

Diving deeper into the issue i realized that geoserver asks my database
for the min and max values of the configured attribute, which is of type
timestamp.

As my database contains a lot of data, these queries take some minutes
to complete, for every single layer.

This leads to timeouts when requesting the capabilities.

So my questions is:

Can i manually configure a valid range for my layer, which will appear
in the capabilities document?

This way geoserver would not need to ask the database, which currently
is unusable slow.

Something like

Startvalue: "2013-11-11T12:30:00:000Z"

Endvalue: "NOW() + 7 days" or "2018-11-07T12:30:00:000Z"

Do i miss something or is this something that is not configurable at the
moment?


Thanks for feedback,

Johannes




___
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