GeoPackage took years to get there :-D
Before anything goes into extension, we want 3 separate sites/projects using it (like, users, customers)
Before anything goes into core, it has to be battle tested with heavy use cases, and something that at large set of of people would be interested into (and that the PSC is comfortable with, meaning, they are using it already)
Now, I am trying to push for FlatGeoBuf every time an occasion presents, but things have to be done in order
@groldan : agreed I have had that precise thought but the QGIS WFS client code is.. not easy to adapt to alternative formats.
Hi, I am trying to implement SSO using OpenID connect plugin. I followed the instruction below.
https://docs.geoserver.org/latest/en/user/community/oauth2/index.html#openid-connect-authentication
However, after adding username and password I redirect back to the top page and I see the following error in geoserver log.
2021-03-31 14:28:15,417 ERROR [geoserver.security] - Could not Authorize OAuth2 Resource due to the following exception: error="invalid_request", error_description="Possible CSRF detected - state parameter was present but no state could be found" at org.springframework.security.oauth2.client.token.grant.code.AuthorizationCodeAccessTokenProvider.getParametersForAuthorizeRequest(AuthorizationCodeAccessTokenProvider.java:313) at org.springframework.security.oauth2.client.token.grant.code.AuthorizationCodeAccessTokenProvider.obtainAuthorizationCode(AuthorizationCodeAccessTokenProvider.java:139) at org.springframework.security.oauth2.client.token.grant.code.AuthorizationCodeAccessTokenProvider.obtainAccessToken(AuthorizationCodeAccessTokenProvider.java:207) at org.springframework.security.oauth2.client.token.AccessTokenProviderChain.obtainNewAccessTokenInternal(AccessTokenProviderChain.java:148) at org.springframework.security.oauth2.client.token.AccessTokenProviderChain.obtainAccessToken(AccessTokenProviderChain.java:121) at org.springframework.security.oauth2.client.OAuth2RestTemplate.acquireAccessToken(OAuth2RestTemplate.java:221) at org.springframework.security.oauth2.client.OAuth2RestTemplate.getAccessToken(OAuth2RestTemplate.java:173) at org.springframework.security.oauth2.client.OAuth2RestTemplate$$FastClassBySpringCGLIB$$ca6dc720.invoke(<generated>) at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:218) at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:752) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163) at org.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:136) at org.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:124) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186) at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:691) at org.springframework.security.oauth2.client.OAuth2RestTemplate$$EnhancerBySpringCGLIB$$100f8fb0.getAccessToken(<generated>) at org.springframework.security.oauth2.client.filter.OAuth2ClientAuthenticationProcessingFilter.attemptAuthentication(OAuth2ClientAuthenticationProcessingFilter.java:105) at org.geoserver.security.oauth2.GeoServerOAuthAuthenticationFilter.getPreAuthenticatedPrincipal(GeoServerOAuthAuthenticationFilter.java:382) at org.geoserver.security.oauth2.GeoServerOAuthAuthenticationFilter.doAuthenticate(GeoServerOAuthAuthenticationFilter.java:284) at org.geoserver.security.oauth2.GeoServerOAuthAuthenticationFilter.doFilter(GeoServerOAuthAuthenticationFilter.java:156) at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:334) at org.geoserver.security.oauth2.GeoServerOAuthAuthenticationFilter.doFilter(GeoServerOAuthAuthenticationFilter.java:172) at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:334)
also if you have control over the openid connect server, check its logs too
failing that, you'll have to setup the source code in a IDE and do a step by step debugging (that's what I end up doing most of the time anyways)
@bjornharrtell this did not help? https://docs.geoserver.org/stable/en/developer/quickstart/index.html
@aaime: btw looks like geoserver/geoserver#4952 makes flatgeobuf available as datastore with the existing gs-flatgeobuf
well, after follow up fix geoserver/geoserver#4963 that is. :)
Hello everyone, i have a question: i have a custom plugin for geoserver-hbase (CoverageStore) and in the DB i have only tiled images. Now, for huge images, what could be a good strategies to improve geoserver performance on layer-preview. Since now when you request for a preview the flow is: getImageFromDB(filter:BBOX) -> mergeTiles -> return GridCoverage2D ... It works, but of course is really slow since hundred or thousands of MB requires time to download all of those.
Thanks
Thanks
since HBase has distributed processing, it is possible (in general) to do the latter and push the computation to the RegionServers
but yeah, I remember that happening when I did the same thing with Accumulo.
We precomputed coarser versions of the data. shrugs
Other options which do not address that problem directly would include using GWC to pre-render tiles that'd cover the coarse zoom levels and making sure that those requests are never made (via a UI restriction perhaps?)
yeah.... the old GeoMesa code may be helpful..... https://github.com/locationtech/geomesa/tree/geomesa_2.11-2.4.2/geomesa-accumulo/geomesa-accumulo-raster/src/main/scala/org/locationtech/geomesa/raster
you'll end up with a little bit of query planner logic to decide which resolution to use....
Looks like sortpom can do 4 spaces (using
<nrOfIndentSpace>). However now that looks like a big change for a small gain.
Thoughts on revision?
I cannot find the entry in the meeting notes...
Well you can start a dedicated topic on the devel list?
Hi Geoserver Experts, I'm fighting with a strange problem. A Geoserver Instance (2.18 docker that ships with geonode) is starting but is only loading 17 layers out of 222. Only after clicking the "reload configuration" button in server status GUI all layers appear (and work without problems). Unfortunately except for a lot of style warnings I cannot spot any obvious in logs: https://www.dropbox.com/s/j8padwo655qgiad/geoserver.log?dl=0. Has somebody run into something similar or has an idea that could stop the catalog from fully loading on server start?
thanks, James. the only thing I can say for sure is that this is not related to geonode as I can reproduce it on a vanilla gs. The strange thing is the same is happening even if I remove all layer from all workspaces and only and 3 of them. there must be something really silly as you say.