Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Björn Harrtell
    @bjornharrtell
    @aaime: Whatever I do I can't seem to get it to live with the unresolved lifecycle things.
    Björn Harrtell
    @bjornharrtell
    @aaime: finally got it to work, but only after removing git-commit-id-plugin and avoiding all community modules
    Andrea Aime
    @aaime
    odd... dunno, haven't been using eclipse in a while
    Björn Harrtell
    @bjornharrtell
    What are you using?
    Brad Hards
    @bradh
    IntelliJ is popular, and I think that is what @aaime uses. I like netbeans though. Its had a bit of a rough time in migrating to Apache, but seems to be getting back on its feet now.
    Andrea Aime
    @aaime
    What Brad said, yup
    James Hughes
    @jnh5y
    I've used IntelliJ when working with GT/GWC/GS and I have liked it
    Gabriel Roldan
    @groldan
    @jodygarnett would you have a moment to review geotools/geotools#3444 sometime soon?
    loridigia
    @loridigia
    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
    James Hughes
    @jnh5y
    Two obvious suggestions come to mind: 1) pre-compute coarser versions of the images (basically, make a pyramid) 2) set up a way to generate downsampled images on the fly in HBase
    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?)
    loridigia
    @loridigia
    Hi James, thanks for your answer, yeah i was thing about pre-compute different different tiles resolutions, think i will go with that
    James Hughes
    @jnh5y
    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....
    Brad Hards
    @bradh
    During the POM formatting change, I complained about inconsistency between AOSP being 4 spaces, and the XML being 2.
    Looks like sortpom can do 4 spaces (using <nrOfIndentSpace>). However now that looks like a big change for a small gain.
    Thoughts on revision?
    Andrea Aime
    @aaime
    @bradh it was discussed during the PSC meeting and we settled on 2 spaces
    I cannot find the entry in the meeting notes...
    Well you can start a dedicated topic on the devel list?
    Brad Hards
    @bradh
    I don't think that it matters that much.
    Toni
    @t-book
    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?
    James Hughes
    @jnh5y
    @t-book Have you tried removing the files mentioned in the exceptions? e.g. stylecover_shrub_databc_nwbc_2014_12_10.xml?
    Toni
    @t-book
    @jnh5y yep unfortunately no difference :/
    James Hughes
    @jnh5y
    If those are gone, then it should result in a different set of exceptions. If that's not the case, then something silly may be happening. Also, if the GeoServer is packaged by GeoNode, it may be worth asking on GeoNode channels about the issue
    Toni
    @t-book
    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.
    James Hughes
    @jnh5y
    well, sounds like you are doing the things that most of us would: reduce the problem and look at the smaller logs
    Toni
    @t-book
    this gives hope :))
    Jody Garnett
    @jodygarnett
    One thing to consider, many layers reference the default built-in line.sld, point.sld etc... using a style info reference. Double check in the xml that the references line up between layer and style.
    You may want to look at the layer “just after” the one that failed to load.
    Toni
    @t-book
    great thanks Jody!
    (I will!)

    You may want to look at the layer “just after” the one that failed to load.

    Unfortunately they are not loaded in alphabetical order, so I would get this info from logs right?

    Toni
    @t-book
    thanks, @jnh5y @jodygarnett your tip with styles brought me back on track. After double-checking (removed all styles again, only added layers in the workspace) at least the layers are loaded. So now I know the culprit must be a style. Have a sunny day and stay healthy ;)
    James Hughes
    @jnh5y
    that's the plan; do the same!
    Toni
    @t-book
    May I ask one more (silly) question? the definition of which style a layer uses is defined in its corresponding featuretype.xml (in workspaces/*)?
    (to double-check a correct path to style xml and sld ;)
    Björn Harrtell
    @bjornharrtell

    I'm getting cut of stack traces in the geoserver log, in this case trouble initializing a data store, making it hard to debug the issue. Anyone know why and/or how to make it produce the full stack trace? It looks like this:

    2021-04-20T19:53:45.091001170Z at org.geoserver.catalog.LockingCatalogFacade.invoke(LockingCatalogFacade.java:36)
    2021-04-20T19:53:45.099225762Z ... 127 more
    2021-04-20T19:53:45.099238462Z Caused by: java.lang.NullPointerException
    2021-04-20T19:53:45.099282862Z at com.sun.proxy.$Proxy25.isIsolated(Unknown Source)
    2021-04-20T19:53:45.099298262Z at org.geoserver.catalog.impl.IsolatedCatalogFacade.canSeeWorkspace(IsolatedCatalogFacade.java:650)
    2021-04-20T19:53:45.099302562Z at org.geoserver.catalog.impl.IsolatedCatalogFacade.getStoreByName(IsolatedCatalogFacade.java:86)
    2021-04-20T19:53:45.099306262Z ... 132 more
    2021-04-20T19:53:45.152908210Z 20 Apr 19:53:45 WARN [org.geoserver] - Failed to load data store 'HNV2021_20210226'

    James Hughes
    @jnh5y
    that's mighty odd. Were it me, I'd load up the GS codebase and debug what you can see. If I had to guess I'd be looking for things around the namespace parameter that was discussed previously
    Jody Garnett
    @jodygarnett

    @t-book no silly questions, the style references are in ... layer.xml.

    Here is an example in sf/sf/roads/layer.xml, you can see two StyleInfoImpl instances referenced (one as the defaultStyle and one in the styles list).

    Toni
    @t-book
    @jodygarnett thanks a lot! and every style.xml has a matching id. got it.
    Bildschirmfoto 2021-04-21 um 07.06.46.png
    Jody Garnett
    @jodygarnett
    These kind of debugging this are a pain, if it helps there is a REST API call you can use to "reload", or use the "reload" button on the Server > About page.
    Toni
    @t-book
    thanks @jodygarnett the rest endpoint looks heapful also to check by script which styles geoserver is aware of.
    Andrea Aime
    @aaime
    I've found the main branch nightly build to run only @daily. We agreed time ago that main is used for demos of current state of GeoServer, and that it needed a more frequent build because of that. I've changed the build trigger to follow gs-main build.
    Jody Garnett
    @jodygarnett
    I just copied what was there, do what is needed :)
    James Hughes
    @jnh5y
    OGC question of the day: A WFS/WMS GetCapabilities returns lots of data about a layer (like keywords, abstract, etc). Can DescribeFeatureType return any "extra" info? (differently, my goal is to provide database details like indexes through some endpoint that's moderated by the Catalog)
    Andrea Aime
    @aaime
    @jnh5y only the schema is returned