Re: [Geoserver-users] [Geotools-devel] [Geowebcache-devel] [Geoserver-devel] SourceForge mailing lists unstable

2018-03-01 Thread Ben Caradoc-Davies 
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 least bad option.


--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
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] [Geowebcache-devel] [Geoserver-devel] SourceForge mailing lists unstable

2018-03-01 Thread Ben Caradoc-Davies 
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/03/18 16:38, Jody Garnett wrote:

I would be willing to migrate to OSGeo mailman, if we can somehow get our
history out of SF. Or I guess even if we cannot...

--
Jody Garnett

On 27 February 2018 at 21:02, Ben Caradoc-Davies  wrote:


Well, mail is getting through, after ten days. Snail mail, anyone? At
least it is nice to know that mail was not lost (as far as I can tell).

Kind regards,
Ben.


On 20/02/18 07:02, Torben Barsballe wrote:


This is a general warning that the SourceForge mailing lists currently
appear to be unstable, with mail not being delivered in a timely manner,
or
simply being lost.
If you are not getting replies, it is possible that know one has seen your
message.

A ticket for this issue has been opened here:
https://sourceforge.net/p/forge/site-support/16501/

Torben




--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot



___
Geoserver-devel mailing list
geoserver-de...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel



--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Geowebcache-devel mailing list
geowebcache-de...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geowebcache-devel





--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
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] "Don't know how to handle resource" exception with layergroups created through REST API

2018-03-01 Thread Emanuele Tajariol (GeoSolutions) 
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/geoserver/geoserver/blob/2.12.2/src/community/geofence/src/main/java/org/geoserver/geofence/GeofenceAccessManager.java#L482

Such a class mismatch can happen when different versions are mixed.
Please make sure the plugin version matches your geoserver version.

   Cheers,
   Emanuele

2018-02-27 23:43 GMT+01:00 Olivier Dalang :

> Dear all,
>
> Layer groups created using the REST API cause a "Don't know how to handle
> resource" exception (full stack below [1]) when I try to show them using
> WMS or when accessing the layergroup admin page. Everything works well when
> created manually through the admin.
>
> I need to restart Geoserver so that it works again. I'm using Geoserver
> 2.12.2 with Geofence (which I believe is involved), authkey and printing
> extensions.
>
> And idea what could be happening there ? To me it looks like some Geofence
> cache isn't (re)generated properly after the API call.
>
> Should I open a ticket somewhere, or is there a way to invalidate/refresh
> the Geofence cache?
>
> Thanks !!
>
> Olivier
>
>
> [1]
> java.lang.IllegalArgumentException: Don't know how to handle resource
> SecuredFeatureTypeInfo[FeatureTypeInfoImpl[offline_osm_multipolygons]]
> at org.geoserver.geofence.GeofenceAccessManager.buildAccessLimi
> ts(GeofenceAccessManager.java:501)
> at org.geoserver.geofence.GeofenceAccessManager.getAccessLimits
> (GeofenceAccessManager.java:306)
> at org.geoserver.geofence.GeofenceAccessManager.getAccessLimits
> (GeofenceAccessManager.java:291)
> at org.geoserver.security.ResourceAccessManager.getAccessLimits
> (ResourceAccessManager.java:50)
> at org.geoserver.security.ResourceAccessManagerWrapper.getAcces
> sLimits(ResourceAccessManagerWrapper.java:219)
> at org.geoserver.security.CatalogFilterAccessManager.getAccessL
> imits(CatalogFilterAccessManager.java:64)
> at org.geoserver.security.SecureCatalogImpl.buildWrapperPolicy(
> SecureCatalogImpl.java:861)
> at org.geoserver.security.SecureCatalogImpl.buildWrapperPolicy(
> SecureCatalogImpl.java:820)
> at org.geoserver.security.SecureCatalogImpl.checkAccess(SecureC
> atalogImpl.java:614)
> at org.geoserver.security.SecureCatalogImpl.checkAccess(SecureC
> atalogImpl.java:503)
> at org.geoserver.security.SecureCatalogImpl.checkAccess(SecureC
> atalogImpl.java:662)
> at org.geoserver.security.SecureCatalogImpl.checkAccess(SecureC
> atalogImpl.java:494)
> at org.geoserver.security.SecureCatalogImpl.getLayerGroupByName
> (SecureCatalogImpl.java:310)
> at org.geoserver.catalog.impl.AbstractFilteredCatalog.getLayerG
> roupByName(AbstractFilteredCatalog.java:237)
> at org.geoserver.catalog.impl.AbstractCatalogDecorator.getLayer
> GroupByName(AbstractCatalogDecorator.java:474)
> at org.geoserver.catalog.impl.LocalWorkspaceCatalog.getLayerGro
> upByName(LocalWorkspaceCatalog.java:186)
> at org.geoserver.wms.WMS.getLayerGroupByName(WMS.java:276)
> at org.geoserver.wms.map.GetMapKvpRequestReader.parseLayers(Get
> MapKvpRequestReader.java:1148)
> at org.geoserver.wms.map.GetMapKvpRequestReader.read(GetMapKvpR
> equestReader.java:237)
> at org.geoserver.wms.map.GetMapKvpRequestReader.read(GetMapKvpR
> equestReader.java:87)
> at org.geoserver.ows.Dispatcher.parseRequestKVP(Dispatcher.java
> :1521)
> at org.geoserver.ows.Dispatcher.dispatch(Dispatcher.java:680)
> at org.geoserver.ows.Dispatcher.handleRequestInternal(Dispatche
> r.java:258)
> at org.springframework.web.servlet.mvc.AbstractController.handl
> eRequest(AbstractController.java:174)
> at org.springframework.web.servlet.mvc.SimpleControllerHandlerA
> dapter.handle(SimpleControllerHandlerAdapter.java:50)
> at org.springframework.web.servlet.DispatcherServlet.doDispatch
> (DispatcherServlet.java:963)
> at org.springframework.web.servlet.DispatcherServlet.doService(
> DispatcherServlet.java:897)
> at org.springframework.web.servlet.FrameworkServlet.processRequ
> est(FrameworkServlet.java:970)
> at org.springframework.web.servlet.FrameworkServlet.doGet(
> FrameworkServlet.java:861)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:687)
> at org.springframework.web.servlet.FrameworkServlet.service(
> FrameworkServlet.java:846)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder
> .java:808)
> at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilte
> r(ServletHandler.java:1669)
> at org.geoserver.filters.ThreadLocalsCleanupFilter

Re: [Geoserver-users] Σχετ: NetCDF-4 library not present on GeoServer start-up

2018-03-01 Thread Ben Caradoc-Davies 

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 only required to *write* NetCDF-4. The pure Java 
implementation included with GeoServer can read NetCDF-4. If you only 
want GeoServer to read NetCDF-4, you can safely ignore the WARN message.


Kind regards,
Ben.


On 01/03/18 20:45, Maria Krommyda wrote:

Dear Ben,
Thank you for your response.Unfortunately this did not solve my problem.
I even tried a clean built, on a fresh VM, with only GeoSerever 2.12.2, 
NetCDF-4 and the library installation as you suggested, fearing that my 
multiple attempts to install the library in the previous VM had resulted in 
some conflicts, but I still get the same error.
Is it possible that I am missing an additional package?
Best regards, Maria.

  


 Στις 10:48 μ.μ. Τετάρτη, 28 Φεβρουαρίου 2018, ο/η Ben Caradoc-Davies 
 έγραψε:
  


  Maria,

the easiest way to install the NetCDF-4 native libraries on Ubuntu 16.04
is to install the binary package provided by your distribution with:

sudo update
sudo apt-get install libnetcdf11

Restart Jetty and everything should just work.

The GeoServer documentation should suggest using distribution packages
where available, rather than building from source.

Kind regards,
Ben.

On 01/03/18 01:56, Maria Krommyda via Geoserver-users wrote:

Hello everyone,
Let me start be giving you the current status of my installation progress. I have 
installed on a Ubuntu 16.04 machine with openjdk version 1.8.0_151 the Geoserver 
2.12.2 using the Jetty server.I have successfully installed the WPS, importer and 
geomesa-accumulo extentions.I am currently trying to install the NetCDF extention.I 
have downloaded the correct jar for the GeoServer version, added them to the lib 
folder in the geoserver_path/webapps/geoserver/WEB-INF and I can see the NetCDF 
option under Create new data source->Raster data source-> NetCDF.
I have also tried, but apparently failed, to install the NetCDF-4 native 
libraries as I need to import NetCDF-4 data files. I have followed the 
instruction 
http://docs.geoserver.org/stable/en/user/extensions/netcdf-out/nc4.html but 
upon starting the GeoServer I get the error:
WARN [serverStartup] - Nc4Iosp: NetCDF-4 C library not present 
(jna_path='/usr/local/lib/', libname='netcdf').
Please note that the jna_path is not null, as it is implied in the installation 
instructions, in the error that I get, however it is not set by me and running echo 
$jna_path from the same terminal, before and after starting the GeoServer returns the 
expected null.I think that the error might come from step 5 in the installation 
instructions where it say "Make sure to add the lib folder of the package you have 
extracted, to the PATH environment variable."I am not sure to which extracted 
package is referred, given that none of the zlib, hdf5 and NetCDF-4 downloads include a 
lib folder. What I did instead was add the lib folder of my installation directory, based 
on the example /work/libs/nc4libs/lib, to the PATH environment.I have also tried to 
install the NetCDF-4 library at the /usr/local/lib/ path but that didn't change the 
behavior.
Any help and ideas of what might cause such error are highly appreciated. If 
you need any additional information please let me.
Thank you very much for you time, Maria.



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot



___
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





--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
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

Re: [Geoserver-users] Understanding Layer Groups

2018-03-01 Thread Andrea Aime 
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 and build tiles for CIB10, CIB05 and CIB01 if I
> am looking at an area that has CIB01 (since thats my top layer)?  Or does
> it
> see there is data in that area for CIB01, so it doesnt work 3 times as hard
> and only look at the CIB01 data?
>

GeoServer has no coverage information and will render all the layers in the
group,
bottom to top (painter's model).

There is a way to avoid it, but it's complicated:

   - use the latest GeoServer version
   - put all the imagery into a single heterogeneous mosaic
   - add for each file a "footprint" information (basically what area it's
   actually covered, as a polygon, skipping null/void/black data)
   - enable "excess granule removal" in the mosaic configuration

There are not many deploys doing this, it's functionality that still kind
of new (due to low exposure).

Cheers
Andrea

==

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

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility  for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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] Understanding Layer Groups

2018-03-01 Thread JBaker 
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_CADRG.  I then put all those groups into 2 layer groups, CIB and CADRG, 
Both of those groups I have a base layer of Blue Marble data with a shape
file as outline,  that way when zoomed all the way out user can see where
they are.

Within AZ_CIB, I have layers AZ_CIB10, AZ_CIB05, AZ_CIB01  (the same for VA
and CA)
Within AZ_CADRG I have AZ_CADRGGNC, AZ_CADRGJNC, AZ_CADRGJOG, AZ_CADRGFCDAY,
AZ_CADRGONC, AZ_CADRGTLM100, AZ_CADRGTLM50, and AZ_CADRGTPC (same for VA and
CA)

My CADRG groups I have setup SLDs that have min and maxscaledenominator set
to switch to a different layer depending on zoom level. 

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 and build tiles for CIB10, CIB05 and CIB01 if I
am looking at an area that has CIB01 (since thats my top layer)?  Or does it
see there is data in that area for CIB01, so it doesnt work 3 times as hard
and only look at the CIB01 data?

I guess problem comes in when i try to seed these layers,  sometimes it will
work, but sometimes it will crash. It wont ever say anything other than
"estimating".  I then have to restart the service.

Is there a better way to do this?

Also, when I have layer groups of layer groups.  Can I seed the AZ Layer
group and GWC will look at the AZ Layer group to get its cached tiles, or
will it build its own tiles under CIB?  I see under gwc folder it makes a
CIB folder, so im assuming its a completely different cache,  just trying to
see if there is a best way to get the cache built.  



--
Sent from: http://osgeo-org.1560.x6.nabble.com/GeoServer-User-f3786390.html

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
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] GeoFence Authentication

2018-03-01 Thread Emanuele Tajariol 
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 concern, though : it seems that no authentication is needed in
> order to interact with its REST API, while it is asked on the gui.
> I can't find any information regarding how to enable it for the REST API
> as well, can you indicate me where I can find it?
> 
> Thanks a lot,
> 
> Fabio Sinibaldi


-- 

Regards,
Emanuele Tajariol

Ing. Emanuele Tajariol
Technical Lead

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


-- 

Regards,
Emanuele Tajariol
==
GeoServer Professional Services from the experts! Visit http://goo.gl/it488V 
for more information.
==

Ing. Emanuele Tajariol
Technical Lead

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

---
AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i 
file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo 
è consentito esclusivamente al destinatario del messaggio, per le finalità 
indicate nel messaggio stesso. Qualora riceviate questo messaggio senza 
esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-
mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal 
Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, 
distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, 
costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.
 
The information in this message and/or attachments, is intended solely for the 
attention and use of the named addressee(s) and may be confidential or 
proprietary in nature or covered by the provisions of privacy act (Legislative 
Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not 
in accord with its purpose, any disclosure, reproduction, copying, 
distribution, or either dissemination, either whole or partial, is strictly 
forbidden except previous formal approval of the named addressee(s). If you 
are not the intended recipient, please contact immediately the sender by 
telephone, fax or e-mail and delete the information in this message that has 
been received in error. The sender does not give any warranty or accept 
liability as the content, accuracy or completeness of sent messages and 
accepts no responsibility  for changes made after they were sent or for other 
risks which arise as a result of e-mail transmission, viruses, etc.

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
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] Versioning maps within Geoserver

2018-03-01 Thread Andrea Aime 
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/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer

Cheers
Andrea


On Tue, Feb 27, 2018 at 3:35 PM, tommaso via Geoserver-users <
geoserver-users@lists.sourceforge.net> wrote:

> Hello, I'm trying to store several versions of my map in Geoserver.
> Currently I deploy new versions of the map by deleting the old workspace,
> copying the updated one and than restarting the server.
> Now I want to archive the old workspace, so that the old map is still
> available.
> My first try was to rename to whole workspace - instead of deleting it -
> from *myworkspace* to *ver0_myworkspace*, where ver0 means version 0. Than
> the client could be request the old map by requesting
> *ver0_myworkspace:mylayer.*
> Unfortunately this is not possible, because the workspace, layer and style
> ids would be the same in the old and in the new workspace, and Geoserver
> fails to load all elements of the copied workspace.
>
> Could you please suggest another solution?
> Note that I'm not searching for a data versioning system like  Geogig
>   , because I want
> to
> support also changes to styling files and layer structures.
>
>
>
> --
> Sent from: http://osgeo-org.1560.x6.nabble.com/GeoServer-User-
> f3786390.html
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility  for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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 I

Re: [Geoserver-users] Regarding CORS support for REST API

2018-03-01 Thread Torben Barsballe 
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.geoserver.org/latest/en/user/production/container.html#enable-cors

If you are using a WAR install with a servlet container (such as tomcat),
you will need to follow the instructions for that container. Basic tomcat
CORS documentation is here:
http://tomcat.apache.org/tomcat-8.0-doc/config/filter.html#CORS_Filter

Torben


On Thu, Mar 1, 2018 at 9:12 AM, Andrea Aime 
wrote:

> 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?
> Windows installer? bin package? war file?
>
> Cheers
> Andrea
>
>
> On Wed, Feb 28, 2018 at 8:08 AM, Vaibhav Josh 
> wrote:
>
>> Hi everyone,
>>
>> I am making a geoserver manager as a part of my internship and I have run
>> into a little road block.
>> I am using jQuery (3.3.1) to fire an AJAX POST request to create a
>> workspace via the REST API.
>> However, I am facing a CORS issue in Firefox (58.0.2)
>> I tried using jsonp datatype in AJAX but that didn't work.
>> I am running the latest Georserver (2.13 beta) and CORS support was one
>> of the improvements over the last version.
>>
>> Any help will be appreciated.
>>
>> Thanks a lot,
>>
>> Vaibhav
>>
>> 
>> --
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> ___
>> 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-req
>> uesting-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 <+39%200584%20962313>
> fax: +39 0584 1660272 <+39%200584%20166%200272>
> mob: +39  339 8844549 <+39%20339%20884%204549>
>
> http://www.geo-solutions.it
> http://twitter.com/geosolutions_it
>
> AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
>
> Le informazioni contenute in questo messaggio di posta elettronica e/o
> nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
> loro utilizzo è consentito esclusivamente al destinatario del messaggio,
> per le finalità indicate nel messaggio stesso. Qualora riceviate questo
> messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
> darcene notizia via e-mail e di procedere alla distruzione del messaggio
> stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
> divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
> utilizzarlo per finalità diverse, costituisce comportamento contrario ai
> principi dettati dal D.Lgs. 196/2003.
>
> The information in this message and/or attachments, is intended solely for
> the attention and use of the named addressee(s) and may be confidential or
> proprietary in nature or covered by the provisions of privacy act
> (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
> Code).Any use not in accord with its purpose, any disclosure, reproduction,
> copying, distribution, or either dissemination, either whole or partial, is
> strictly forbidden except previous formal approval of the named
> addressee(s). If you are not the intended recipient, please contact
> immediately the sender by telephone, fax or e-mail and delete the
> information in this message that has been received in error. The sender
> does not give any warranty or accept liability as the content, accuracy or
> completeness of sent messages and accepts no responsibility  for changes
> made after they were sent or for other risks which arise as a result of
> e-mail transmission,

Re: [Geoserver-users] No Data not handled in GeoTiff 16Bits Multiband - Sentinel datasets

2018-03-01 Thread Andrea Aime 
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 in regard to
the Sentinel2 publishing case (the german spatial agency is publishing
Sentinel2 data straight
from the jp2 files using it)

Cheers
Andrea


On Tue, Feb 27, 2018 at 6:53 PM, Pascal Coulon 
wrote:

> All,
>
>
>
> We are hoping to publish some 16Bits Multi-bands (10 bands) GeoTiff –
> Earth Observation Dataset Sentinel2. We have some major issue making
> transparent the “*nodata*” area available in the GeoTIFF
>
>
>
> The idea is to apply a range of SLD (e.g. true colour, false colour). Each
> SLD we apply makes the most of the channel selection along with some
> ContrastEnhancement. Note, we need to need to publish the full GeoTiff as
> opposed to pre-process the dataset off line. We will need to allow the WCS
> to run of the full GeoTiff as opposed to a simplified RGB GeoTiff.
>
>
>
> The channel selection and the ContrastEnhancement work well. However, we
> have now exhausted all avenues to make the no data area transparent.
>
>
>
> Our approach is similar to the one employed by Simone Giannecchini -
> http://blog.geoserver.org/2008/12/18/raster-symbolizer-tips-tricks-part-2/.
> We understand that this approach was successful and the post, it is also
> mentioned a sample file (EmissiveCampania.tif); it would be great if we
> could get access to it as a mean to compare with our data.
>
>
>
> We have tried a number of options
>
>
>
> ·Apply specific nodata value, but so far not luck (gdalwarp
> -srcnodata 255 -dstalpha input.tif output.tif) – as per reported here
> http://osgeo-org.1560.x6.nabble.com/10-bands-geotiff-
> 16-bits-handling-transparency-for-no-data-tc5354305.html
>
> ·set an InputTransparentColor to a layer – but this throw an
> error as per reported here http://osgeo-org.1560.x6.
> nabble.com/Unsupported-data-type-when-using-a-transparent-
> color-td5261925.html
>
>
>
> For information, I am including below some information on the file,
> GeoServer version and the SLD being used.
>
>
>
> Any help would be greatly appreciated from the GeoServer community.
>
>
>
> Regards,
>
>
>
> Pascal
>
>
>
> #
>
> *GDLAINFO (note that I am only including the first two bands for economy.)*
>
> Driver: GTiff/GeoTIFF
>
> Files: test_16b.tif
>
> Size is 10818, 11120
>
> Coordinate System is:
>
> PROJCS["OSGB 1936 / British National Grid",
>
> GEOGCS["OSGB 1936",
>
> DATUM["OSGB_1936",
>
> SPHEROID["Airy 1830",6377563.396,299.3249646,
>
> AUTHORITY["EPSG","7001"]],
>
> TOWGS84[446.448,-125.157,542.06,0.15,0.247,0.842,-20.489],
>
> AUTHORITY["EPSG","6277"]],
>
> PRIMEM["Greenwich",0,
>
> AUTHORITY["EPSG","8901"]],
>
> UNIT["degree",0.0174532925199433,
>
> AUTHORITY["EPSG","9122"]],
>
> AUTHORITY["EPSG","4277"]],
>
> PROJECTION["Transverse_Mercator"],
>
> PARAMETER["latitude_of_origin",49],
>
> PARAMETER["central_meridian",-2],
>
> PARAMETER["scale_factor",0.9996012717],
>
> PARAMETER["false_easting",40],
>
> PARAMETER["false_northing",-10],
>
> UNIT["metre",1,
>
> AUTHORITY["EPSG","9001"]],
>
> AXIS["Easting",EAST],
>
> AXIS["Northing",NORTH],
>
> AUTHORITY["EPSG","27700"]]
>
> Origin = (430590.000,171580.000)
>
> Pixel Size = (10.000,-10.000)
>
> Metadata:
>
>   AREA_OR_POINT=Area
>
> Image Structure Metadata:
>
>   COMPRESSION=LZW
>
>   INTERLEAVE=PIXEL
>
> Corner Coordinates:
>
> Upper Left  (  430590.000,  171580.000) (  1d33'35.35"W, 51d26'30.82"N)
>
> Lower Left  (  430590.000,   60380.000) (  1d34' 8.98"W, 50d26'30.70"N)
>
> Upper Right (  538770.000,  171580.000) (  0d 0'13.54"W, 51d25'32.60"N)
>
> Lower Right (  538770.000,   60380.000) (  0d 2'45.96"W, 50d25'34.51"N)
>
> Center  (  484680.000,  115980.000) (  0d47'40.99"W, 50d56'11.37"N)
>
> Band 1 Block=256x256 Type=UInt16, ColorInterp=Gray
>
>   Description = Blue
>
>   Min=1.000 Max=2459.000
>
>  Minimum=1.000, Maximum=2459.000, Mean=93.234, StdDev=155.846
>
>   NoData Value=0
>
>   Overviews: 2704x2780, 1352x1390, 676x695, 338x347, 169x173
>
>   Metadata:
>
> ATTRIBUTETABLE_CHUNKSIZE=1000
>
> LAYER_TYPE=athematic
>
> STATISTICS_EXCLUDEDVALUES=0
>
> STATISTICS_HISTOBINFUNCTION=linear
>
> STATISTICS_HISTOBINVALUES=313|132138|3218980|10696252|
> 15875437|9418712|4137267|2396392|1547224|1319819|
> 871921|689650|480895|312188|275321|206391|202031|179196|
> 147838|154172|132337|139280|133389|114713|123262|107450|
> 116572|112379|98792|107788|94840|102595|99792|88529|
> 95852|85074|93346|91822|81827|88194|78309|85110|84842|75079|
> 82032|72224|80071|78

Re: [Geoserver-users] Updating coveragestore URL - REST API

2018-03-01 Thread Andrea Aime 
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/workspaces/ws_name/coveragestores/coveragestore_name;
>
> // PUT data (its same as in POST)
> $xmlStr = "
> 
> coveragestorename
> GeoTIFF
> true
> ws_name
>  file:///path/to/the/file/". $filename . "
> 
> ";
>
> > Hi!
> >
> > I am trying to modify coveragestore URL (with Geoserver REST API), with
> > purpose of getting up-to-date coverage that's been created every 15 min,
> > but I end up getting:
> > < HTTP/1.1 405 Method Not Allowed
> > < Allow: DELETE, GET, PUT
> >
> > This is my method (using PHP):
> >
> > $filename = "GEOTIF_201802280845.tif" // This variable is changable, and
> I
> > always get it automatically in a form GEOTIF_mmddhmin.tif
> > ...
> > // POST
> > $request = "rest/workspaces/ws_name/coveragestores";
> > ...
> > //POST data
> > $xmlStr = "
> > 
> > coveragestorename
> > GeoTIFF
> > true
> > ws_name
> >  file:///path/to/the/file/". $filename . "
> > 
> > ";
> >
> > Can someone point out what am I doing wrong?
> >
> > Thanks in advance!
> >
> > Daria
> >
> >
> >
> >
> >
> >
> >
> > 
> --
> > Check out the vibrant tech community on one of the world's most
> > engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> > ___
> > 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
> >
>
>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give an

Re: [Geoserver-users] Longitude > 180 in WCS

2018-03-01 Thread Andrea Aime 
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 limited.
That said, for sure WMS style general data wrapping is not available in WCS.

It may help to see the requests you're making and what you're getting back.

Cheers
Andrea


On Wed, Feb 21, 2018 at 1:44 AM, James Goldie  wrote:

> Hi everyone,
>
> I'm trying to serve some NetCDFs that have longitude 0:360 (instead of
> -180:+180) to Leaflet over WCS, but I found that they distorted when my
> requested box fell over X < 0. After doing some investigating (
> https://gis.stackexchange.com/questions/272092/
> distortion-in-netcdf-served-to-leaflet-with-geoserver/272103), I realised
> that WMS supports longitude > 180 and longitudinal wrapping as of 2.10 (
> http://blog.geoserver.org/2016/09/20/geoserver-2-10-beta-released/).
> However, I can't find any mention of this also being supported for WCS.
>
> Is it possible to serve these NetCDFs as they are over WCS using
> GeoServer, or do I need to fall back to WMS (sacrificing some client-side
> styling and metadata) or preprocess the NetCDFs?
>
> Thanks very much,
>
> James
> --
> =
> James Goldie: PhD Student, Climate Change Research Centre
> Email: j.gol...@unsw.edu.au, m...@rensa.co
> Tel: +61 421 747 208 <+61%20421%20747%20208>
> Skype: james-goldie
> Web: https://rensa.co
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility  for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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: 
h

Re: [Geoserver-users] Regarding CORS support for REST API

2018-03-01 Thread Andrea Aime 
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?
Windows installer? bin package? war file?

Cheers
Andrea


On Wed, Feb 28, 2018 at 8:08 AM, Vaibhav Josh 
wrote:

> Hi everyone,
>
> I am making a geoserver manager as a part of my internship and I have run
> into a little road block.
> I am using jQuery (3.3.1) to fire an AJAX POST request to create a
> workspace via the REST API.
> However, I am facing a CORS issue in Firefox (58.0.2)
> I tried using jsonp datatype in AJAX but that didn't work.
> I am running the latest Georserver (2.13 beta) and CORS support was one of
> the improvements over the last version.
>
> Any help will be appreciated.
>
> Thanks a lot,
>
> Vaibhav
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility  for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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 slowing down with bigger CQL filters

2018-03-01 Thread Ian Turton 
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 Kiselka <
bernhard.kise...@prisma-solutions.at> wrote:

> 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 someone has any guesses why GeoServer is slowing down exponentially?
>
> I assume that parsing the filter is slow, because the postgres database
> query is _not_ slowing down that much (the query itself takes less than
> 100ms).
>
> Thanks for any thoughts!
>
> Best regards,
> Bernhard
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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
>



-- 
Ian Turton
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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] GeoServer slowing down with bigger CQL filters

2018-03-01 Thread Bernhard Kiselka 
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 someone has any guesses why GeoServer is slowing down exponentially?

I assume that parsing the filter is slow, because the postgres database query 
is _not_ slowing down that much (the query itself takes less than 100ms).

Thanks for any thoughts!

Best regards,
Bernhard

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
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