Today SourceForge mailing lists are faster than I have ever seen. I no
longer have to wait tens of minutes for mail to be delivered to the lists.
On 02/03/18 07:31, Ben Caradoc-Davies wrote:
For all their problems, I think SourceForge are serious about keeping
their services working and are the
Not only would we lose our history, we would also change the list
address. How would we redirect users of the Nabble interface seeking
support?
For all their problems, I think SourceForge are serious about keeping
their services working and are the least bad option.
Kind regards,
Ben.
On 01
Hi Olivier,
the error is quite strange:
you're entering the else block at
https://github.com/geoserver/geoserver/blob/2.12.2/src/community/geofence/src/main/java/org/geoserver/geofence/GeofenceAccessManager.java#L501
while your SecuredFeatureTypeInfo should be handled at
https://github.com/geoserv
Maria,
all dependencies should be installed automatically by the package
management system.
Are your libnetcdf11 and JVM the same same architecture? For example,
both amd64, and not one amd64 and another i386?
I re-read your original question and note that the native NetCDF-4
library is on
On Thu, Mar 1, 2018 at 7:05 PM, JBaker wrote:
> On CIB groups I have them Layered CIB10 to draw first then CIB05, lastly
> CIB01. These maps show different resolutions, 10 meter, 5 meter and 1
> meter. So lets say I am trying to look at or cache the the AZ area, is
> Geoserver trying to render
Hello,
I am trying to get a better grasp on how layer groups work.
I am attempting to load about 200GB of Raster data, 70% CIB and 30% CADRG,
RPFTOCs. So right now I have created Layer groups of each area, For
instance, I have Layer Group AZ_CIB, VA_CIB, CA_CIB, AZ_CADRG, VA_CADRG, and
CA_CAD
Hi Fabio,
as reported in issue #9, the REST API does not provide any auth mechanism at
the moment.
Cheers,
Emanuele
Alle 17:38:57 di Wednesday 21 February 2018, Fabio Sinibaldi ha scritto:
> Hi,
>
> we're trying to exploit a standalone GeoFence for our GeoServer cluster.
> I've one conc
Hi Tommaso,
there is no simple way to copy an entire workspace and its contents, you'll
probably have to script
it using the REST API.
I guess it would be nice to have a "create copy" button somewhere in the
UI, if you are interested in having that
see this guide:
https://github.com/geoserver/geo
Hi Vaibhav,
Andrea is correct, the latest CORS support fix was just adding a library to
the minimal jetty installation. You will still need to enable CORS. How you
enable CORS will depend upon how you installed GeoServer. Basic
instructions for the standalone version are here:
http://docs.geoserve
Hi,
considering that the files have nodata explictily marked, the best way
would be to enable jai-ext and
not mess with the SLD:
http://docs.geoserver.org/stable/en/user/configuration/image_processing/index.html#jai-ext
GeoServer 2.13-beta recommended, it's the version that has got the most
fixes
Hi,
you should probably give us some more information... is the target of your
request a image mosaic?
Or are you trying to create a new layer instead?
Cheers
Andrea
On Wed, Feb 28, 2018 at 1:45 PM, wrote:
> I apologize, correction to previous post:
>
> // PUT request
> $request = "rest/worksp
Hi James,
I remember that in older version of WCS request crossing the dateline had
to be specified with minLon > maxLon,
and then the service would have taken the "long road around the dateline"
(well, long or short).
Not sure if that applies to WCS 2.0, my involvement in that implementation
was
Hi,
I believe you still need to configure CORS in Jetty, the ticket (to my
limited knowledge) was
just about adding a library to our minimized Jetty installation that would
make configuration
work.
Torben (cc'ed) should know more, but in the meantime, which flavor of
GeoServer are you installing?
Parsing a CQL filter of that size is bound to take a while and then it has
to be translated into an SQL statement which will also take a while.
I suspect there must be an easier way of doing what ever you are doing with
out the need for a 20Kb filter.
Ian
On 1 March 2018 at 13:14, Bernhard Kisel
Hi list!
I did not do so much research as in https://gis.stackexchange.com/a/82305 but
as my data increased, my CQL_FILTER containing IDs that shall be rendered
increased from 600 to 1800 (20 kilobyte of filter string!) and GeoServer
response time increased from 1 second to 5 seconds.
Does som
15 matches
Mail list logo
