Re: [Geoserver-devel] Build failed in Jenkins: geoserver-2.13.x #34

2018-03-21 Thread leizhang 
you can skip the test process.try the command:  mvn compile
-Dmaven.test.skip=true



--
Sent from: http://osgeo-org.1560.x6.nabble.com/GeoServer-Dev-f3819232.html--
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-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] SLD from Postgis or from GeoPackage

2018-03-21 Thread Jody Garnett 
We have a similar need with shape files, the presence of a sidecar SLD file
is great way to pass styling around.

At a GeoTools level I would love a way to "discover" a built-in style for a
layer so we could make it available for either a) GeoServer Data Import
(sadly that would just be a one time solution), or see we could make a
placeholder in the LayerInfo (maybe with a special default style
placeholder.


GeoTools does have a per layer "info" data structure used to pass meta
information on to the application, we could see about making the style
available in this manner.

--
Jody Garnett

On 21 March 2018 at 15:31, Jorge Gustavo Rocha  wrote:

> Hi devs,
>
> QGIS can save the style back to the provider (to Postgis and to
> GeoPackage). The style is stored on a table called layers_style. On
> Postgis, the table is stored in the public schema.
>
> The table has a column to store the native QGIS style format and another
> column to store the SLD style (stylesld).
>
> I would like to use the SLD style stored on layers_style table on
> Geoserver. It would improve the interoperability between QGIS and
> Geoserver.
>
> It can be done both for Postgis and for GeoPackage stores. For example,
> when publishing a GeoPackahe layer, it would be nice to use the SLD
> already stored in the GeoPackage. The same for Postgis.
>
> The layers_table [1] also has a useasdefault column. It would be super
> cool to immediately render the layer using that default style for the
> layer.
>
> I would appreciate your feedback regarding this use case.
>
> I've done a simple mockup [2] to improve the Publishing tab for the
> layer. It adds one more list of styles. The user can choose from the
> 'Available styles' list and also from the 'Available style in Postgis'
> (or 'Available style in GeoPackage') list.
>
> The store (when connecting to Postgis) is always related with a schema
> that might be not the public. To support this use case, we need to add
> an additional connection to the database to the public schema using the
> same credentials.
>
> Regards from Bonn Code Sprint,
>
> Jorge Gustavo
>
>
> [1] CREATE TABLE public.layer_styles (
> id integer NOT NULL DEFAULT nextval('layer_styles_id_seq'::regclass),
> f_table_catalog character varying COLLATE pg_catalog."default",
> f_table_schema character varying COLLATE pg_catalog."default",
> f_table_name character varying COLLATE pg_catalog."default",
> f_geometry_column character varying COLLATE pg_catalog."default",
> stylename text COLLATE pg_catalog."default",
> styleqml xml,
> stylesld xml,
> useasdefault boolean,
> description text COLLATE pg_catalog."default",
> owner character varying(63) COLLATE pg_catalog."default",
> ui xml,
> update_time timestamp without time zone DEFAULT now(),
> CONSTRAINT layer_styles_pkey PRIMARY KEY (id)
> );
>
> [2]
> https://www.dropbox.com/s/nh72i4tv21y1h0o/mockup%20with%
> 20styles%20from%20postgis.png?dl=0
>
> --
> Geomaster, Lda
> Avenida Barros e Soares, 423
> Nogueira
> 4715-214 Braga
> NIF 510906109
> Tm +351 910333888
> Email j...@geomaster.pt
> Site geomaster.pt
> GPS 41.53322,-8.41929
>
> 
> --
> 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-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
--
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-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] Build failed in Jenkins: geoserver-master-app-schema-online #1111

2018-03-21 Thread monitor 
See 


Changes:

[Alessio Fabiani] Log level to FINEST

[Alessio Fabiani] Log level to FINEST

[Andrea Aime] [GEOS-8638] WFS join with ValueReference using local namespaces 
fail to

[Andrea Aime] [GEOS-8657] GeoServer in CITE compliance mode fails to validate an

[Andrea Aime] [GEOS-8646], some fixes to UI and labels

[github] [GEOS-8652] WMTS multidimensional histogram calculation failures

--
[...truncated 264.94 KB...]
at 
org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)

testQuantityListSubset(org.geoserver.test.TimeSeriesInlineWfsTest)  Time 
elapsed: 79 sec  <<< FAILURE!
org.junit.ComparisonFailure: expected:<[wfs:FeatureCollection]> but 
was:<[ows:ExceptionReport]>
at org.junit.Assert.assertEquals(Assert.java:115)
at org.junit.Assert.assertEquals(Assert.java:144)
at 
org.geoserver.test.TimeSeriesInlineWfsTest.testQuantityListSubset(TimeSeriesInlineWfsTest.java:119)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
at 
org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
at 
org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)

Running org.geoserver.test.TimeSeriesWfsTest
Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 3.8 sec <<< 
FAILURE!
testQuantityListSubset(org.geoserver.test.TimeSeriesWfsTest)  Time elapsed: 79 
sec  <<< FAILURE!
org.junit.ComparisonFailure: expected:<[wfs:FeatureCollection]> but 
was:<[ows:ExceptionReport]>
at org.junit.Assert.assertEquals(Assert.java:115)
at org.junit.Assert.assertEquals(Assert.java:144)
at 
org.geoserver.test.TimeSeriesWfsTest.testQuantityListSubset(TimeSeriesWfsTest.java:240)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at

[Geoserver-devel] Build failed in Jenkins: geoserver-2.13.x #34

2018-03-21 Thread monitor 
See 

--
[...truncated 542.98 KB...]
[INFO] 
[INFO] Skipping WCS UI Module
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Application Schema Integration Test
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Importer Core Module
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Security UI JDBC Module
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Security UI LDAP Module
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping GeoServer Security Extension Modules
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Catalog Services for the Web core module
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Web Processing Service Module
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping GeoServer INSPIRE Extensions
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Web Coverage Service 2.0 Earth Observation extensions
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping WCS NetCDF output Module
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Core Monitor Extension
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Importer REST Api Module-ng
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Importer Berkley DB Persistence Module

Re: [Geoserver-devel] SLD from Postgis or from GeoPackage

2018-03-21 Thread Nuno Oliveira 

Hi,

This looks like something that could be implemented as a community module.

I see at least three major challenges here:

   1. Configure and store the extra information associated to the layer, i.e. 
what are the DB
   available styles, which one is the default etc ...
   2. Plug this info into the layer when it is retrieved from the catalog at 
runtime
   3. Handle the calls that will be made to the catalog looking for the DB 
styles

The first point could be solved by storing the necessary info in the layer 
meta-data.
The second and third point are a bit more difficult to handle and may need to be done at the 
CatalogFacade level, this will need to be investigated.


Regarding the lockups, so basically the user will have two "styles selectors" available where the 
ones coming from the DB will be priority ?

In an ideal world only a single "styles selector" should be made available to 
the user 

Let's see if anyone else has something to add :)

Cheers,

Nuno Oliveira

On 03/21/2018 02:31 PM, Jorge Gustavo Rocha wrote:

Hi devs,

QGIS can save the style back to the provider (to Postgis and to
GeoPackage). The style is stored on a table called layers_style. On
Postgis, the table is stored in the public schema.

The table has a column to store the native QGIS style format and another
column to store the SLD style (stylesld).

I would like to use the SLD style stored on layers_style table on
Geoserver. It would improve the interoperability between QGIS and Geoserver.

It can be done both for Postgis and for GeoPackage stores. For example,
when publishing a GeoPackahe layer, it would be nice to use the SLD
already stored in the GeoPackage. The same for Postgis.

The layers_table [1] also has a useasdefault column. It would be super
cool to immediately render the layer using that default style for the layer.

I would appreciate your feedback regarding this use case.

I've done a simple mockup [2] to improve the Publishing tab for the
layer. It adds one more list of styles. The user can choose from the
'Available styles' list and also from the 'Available style in Postgis'
(or 'Available style in GeoPackage') list.

The store (when connecting to Postgis) is always related with a schema
that might be not the public. To support this use case, we need to add
an additional connection to the database to the public schema using the
same credentials.

Regards from Bonn Code Sprint,

Jorge Gustavo


[1] CREATE TABLE public.layer_styles (
 id integer NOT NULL DEFAULT nextval('layer_styles_id_seq'::regclass),
 f_table_catalog character varying COLLATE pg_catalog."default",
 f_table_schema character varying COLLATE pg_catalog."default",
 f_table_name character varying COLLATE pg_catalog."default",
 f_geometry_column character varying COLLATE pg_catalog."default",
 stylename text COLLATE pg_catalog."default",
 styleqml xml,
 stylesld xml,
 useasdefault boolean,
 description text COLLATE pg_catalog."default",
 owner character varying(63) COLLATE pg_catalog."default",
 ui xml,
 update_time timestamp without time zone DEFAULT now(),
 CONSTRAINT layer_styles_pkey PRIMARY KEY (id)
);

[2]
https://www.dropbox.com/s/nh72i4tv21y1h0o/mockup%20with%20styles%20from%20postgis.png?dl=0



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

Nuno Miguel Carvalho Oliveira
@nmcoliveira
Software Engineer

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

[Geoserver-devel] Build failed in Jenkins: 2.12-cite-wms-1.3 #169

2018-03-21 Thread monitor 
See 

--
[...truncated 237.54 KB...]
Mar 21, 2018 7:52:02 PM org.geoserver.GeoserverInitStartupListener 
contextDestroyed
INFO: Unregistering JAI factory class com.sun.media.jai.opimage.BandMergeCRIF
Mar 21, 2018 7:52:02 PM org.geoserver.GeoserverInitStartupListener 
contextDestroyed
INFO: Unregistering JAI factory class com.sun.media.jai.opimage.CropCRIF
Mar 21, 2018 7:52:02 PM org.geoserver.GeoserverInitStartupListener 
contextDestroyed
INFO: Unregistering JAI factory class com.sun.media.jai.mlib.MlibExtremaRIF
Mar 21, 2018 7:52:02 PM org.geoserver.GeoserverInitStartupListener 
contextDestroyed
INFO: Unregistering JAI factory class com.sun.media.jai.opimage.ExtremaRIF
Mar 21, 2018 7:52:02 PM org.geoserver.GeoserverInitStartupListener 
contextDestroyed
INFO: Unregistering JAI factory class com.sun.media.jai.mlib.MlibSubtractRIF
Mar 21, 2018 7:52:02 PM org.geoserver.GeoserverInitStartupListener 
contextDestroyed
INFO: Unregistering JAI factory class com.sun.media.jai.opimage.SubtractCRIF
Mar 21, 2018 7:52:02 PM org.geoserver.GeoserverInitStartupListener 
contextDestroyed
INFO: Unregistering JAI factory class com.sun.media.jai.opimage.ConstantCRIF
Mar 21, 2018 7:52:02 PM org.geoserver.GeoserverInitStartupListener 
contextDestroyed
INFO: Unregistering JAI factory class com.sun.media.jai.mlib.MlibIDFTRIF
Mar 21, 2018 7:52:02 PM org.geoserver.GeoserverInitStartupListener 
contextDestroyed
INFO: Unregistering JAI factory class com.sun.media.jai.opimage.IDFTCRIF
Mar 21, 2018 7:52:02 PM org.geoserver.GeoserverInitStartupListener 
contextDestroyed
INFO: Unregistering JAI factory class com.sun.media.jai.mlib.MlibInvertRIF
Mar 21, 2018 7:52:02 PM org.geoserver.GeoserverInitStartupListener 
contextDestroyed
INFO: Unregistering JAI factory class com.sun.media.jai.opimage.InvertCRIF
Mar 21, 2018 7:52:02 PM org.geoserver.GeoserverInitStartupListener 
contextDestroyed
INFO: Unregistering JAI factory class com.sun.media.jai.opimage.PiecewiseCRIF
Mar 21, 2018 7:52:02 PM org.geoserver.GeoserverInitStartupListener 
contextDestroyed
INFO: Unregistering JAI factory class 
com.sun.media.jai.mlib.MlibDivideByConstRIF
Mar 21, 2018 7:52:02 PM org.geoserver.GeoserverInitStartupListener 
contextDestroyed
INFO: Unregistering JAI factory class 
com.sun.media.jai.opimage.DivideByConstCRIF
Mar 21, 2018 7:52:02 PM org.geoserver.GeoserverInitStartupListener 
contextDestroyed
INFO: Unregistering JAI factory class com.sun.media.jai.mlib.MlibOrConstRIF
Mar 21, 2018 7:52:02 PM org.geoserver.GeoserverInitStartupListener 
contextDestroyed
INFO: Unregistering JAI factory class com.sun.media.jai.opimage.OrConstCRIF
Mar 21, 2018 7:52:02 PM org.geoserver.GeoserverInitStartupListener 
contextDestroyed
INFO: Unregistering JAI factory class com.sun.media.jai.opimage.MosaicRIF
Mar 21, 2018 7:52:02 PM org.geoserver.GeoserverInitStartupListener 
contextDestroyed
INFO: Unregistering JAI factory class com.sun.media.jai.mlib.MlibMosaicRIF
Mar 21, 2018 7:52:02 PM org.geoserver.GeoserverInitStartupListener 
contextDestroyed
INFO: Unregistering JAI factory class com.sun.media.jai.mlib.MlibRotateRIF
Mar 21, 2018 7:52:02 PM org.geoserver.GeoserverInitStartupListener 
contextDestroyed
INFO: Unregistering JAI factory class com.sun.media.jai.opimage.RotateCRIF
Mar 21, 2018 7:52:02 PM org.geoserver.GeoserverInitStartupListener 
contextDestroyed
INFO: Unregistering JAI factory class com.sun.media.jai.mlib.MlibXorConstRIF
Mar 21, 2018 7:52:02 PM org.geoserver.GeoserverInitStartupListener 
contextDestroyed
INFO: Unregistering JAI factory class com.sun.media.jai.opimage.XorConstCRIF
Mar 21, 2018 7:52:02 PM org.geoserver.GeoserverInitStartupListener 
contextDestroyed
INFO: Unregistering JAI factory class com.sun.media.jai.mlib.MlibShearRIF
Mar 21, 2018 7:52:02 PM org.geoserver.GeoserverInitStartupListener 
contextDestroyed
INFO: Unregistering JAI factory class com.sun.media.jai.opimage.ShearRIF
Mar 21, 2018 7:52:02 PM org.geoserver.GeoserverInitStartupListener 
contextDestroyed
INFO: Unregistering JAI factory class 
com.sun.media.jai.opimage.MagnitudeSquaredCRIF
Mar 21, 2018 7:52:02 PM org.geoserver.GeoserverInitStartupListener 
contextDestroyed
INFO: Unregistering JAI factory class com.sun.media.jai.mlib.MlibAddConstRIF
Mar 21, 2018 7:52:02 PM org.geoserver.GeoserverInitStartupListener 
contextDestroyed
INFO: Unregistering JAI factory class com.sun.media.jai.opimage.AddConstCRIF
Mar 21, 2018 7:52:02 PM org.geoserver.GeoserverInitStartupListener 
contextDestroyed
INFO: Unregistering JAI factory class 
it.geosolutions.jaiext.rlookup.RangeLookupRIF
Mar 21, 2018 7:52:02 PM org.geoserver.GeoserverInitStartupListener 
contextDestroyed
INFO: Unregistering JAI factory class com.sun.media.jai.mlib.MlibAndRIF
Mar 21, 2018 7:52:02 PM org.geoserver.GeoserverInitStartupListener 
contextDestroyed
INFO: Unregistering JAI factory class com.sun.media.jai.opimage.AndCRIF
Mar

Re: [Geoserver-devel] How to apply CQL Filter on FeatureType Property that contains Json Object

2018-03-21 Thread Nuno Oliveira 

Right, e.g. PostgreSQL has some support for JSON.

On 03/21/2018 05:06 PM, Andrea Aime wrote:

On Wed, Mar 21, 2018 at 5:38 PM, Jim Hughes > wrote:

In the short term, one may be able to drop in the geomesa-feature-kryo jar 
(with enough
dependencies) to make things work.


To work... slowly (against anything by small datasets) as the function is 
evaluated in memory.
For good performance, one should also implement translation of the function 
down into native SQL
(an exercise left for the reader ;-) )

Cheers
Andrea
==

GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more 
information.==Ing. Andrea Aime @geowolfTechnical LeadGeoSolutions S.A.S.Via di Montramito 3/A55054 
 Massarosa (LU)phone: +39 0584 962313fax: +39 0584 1660272mob: +39  339 
8844549http://www.geo-solutions.ithttp://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-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel


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

Nuno Miguel Carvalho Oliveira
@nmcoliveira
Software Engineer

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

[Geoserver-devel] Jenkins build is back to normal : geoserver-2.13.x #33

2018-03-21 Thread monitor 
See 



--
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-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] [JIRA] (GEOS-8657) GeoServer in CITE compliance mode fails to validate an empty LockFeature request

2018-03-21 Thread Andrea Aime (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrea Aime created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 GeoServer /  GEOS-8657  
 
 
  GeoServer in CITE compliance mode fails to validate an empty LockFeature request   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 21/Mar/18 6:10 PM  
 
 
Priority: 
  Medium  
 
 
Reporter: 
 Andrea Aime  
 

  
 
 
 
 

 
 A request like this is valid according to standard, but fails validation in GeoServer: 

 

"http://www.opengis.net/wfs/2.0" lockId="GeoServer_eb5fd6b6b6024d5" service="WFS" version="2.0.0"> 
 

  
 

  
 
 
  
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
 

Re: [Geoserver-devel] How to apply CQL Filter on FeatureType Property that contains Json Object

2018-03-21 Thread Andrea Aime 
On Wed, Mar 21, 2018 at 5:38 PM, Jim Hughes  wrote:

> In the short term, one may be able to drop in the geomesa-feature-kryo jar
> (with enough dependencies) to make things work.
>

To work... slowly (against anything by small datasets) as the function is
evaluated in memory.
For good performance, one should also implement translation of the function
down into native SQL
(an exercise left for the reader ;-) )

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-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] How to apply CQL Filter on FeatureType Property that contains Json Object

2018-03-21 Thread Jim Hughes 

Hi all,

We did something like Nuno's first suggestion in GeoMesa:

https://github.com/locationtech/geomesa/blob/master/geomesa-features/geomesa-feature-kryo/src/main/scala/org/locationtech/geomesa/features/kryo/json/JsonPathFilterFunction.scala

https://github.com/locationtech/geomesa/blob/master/geomesa-features/geomesa-feature-kryo/src/test/scala/org/locationtech/geomesa/features/kryo/json/JsonPathFilterFunctionTest.scala

In the short term, one may be able to drop in the geomesa-feature-kryo 
jar (with enough dependencies) to make things work.


Cheers,

Jim


On 03/20/2018 04:57 PM, Nuno Oliveira wrote:

Hi,

As far as I know filtering with CQL\OGC Filter\ECQL on the JSON 
content of a property is not possible, for GeoServer the EntityUser 
value is just a normal String.


I can see two paths for this:

  * Implement a custom function that would help you dealing with JSON
and then use it in the CQL filter

  o for example a function that given a certain path extract the
correspond value from JSON

  * create a view, a real view in the database or a GeoServer view,
that would put the content of the

Hope it helps,

Nuno Oliveira

On 03/20/2018 04:20 AM, C.Ram wrote:

I have mssql datastore and named layer Compressor generated based on SQL view
query that I want to filter from Openlayer wms request based on Property
EntityUser that contains JSON object with a key.

Sample JSON that contains EntityUser Column/Property is:
 
   {

 "4742ed9e-384c-41fe-9240-8ced1da67759": {
 "242b5425-2abb-45f1-8f6f-e962ef0861e0":
["746c8188-0125-41f5-aa61-e42c753a77ac"]
 },
 "fff4f98e-cddd-4c7e-aa3e-57e20ec682e9": {
 "242b5425-2abb-45f1-8f6f-e962ef0861e0":
["746c8188-0125-41f5-aa61-e42c753a77ac"]
 }
 }


So how I apply cql or ogc filter on Property that having JSONObject?

Layer Preview Image:
  


And also suggest what are all the way possible to filter layer.



--
Sent from:http://osgeo-org.1560.x6.nabble.com/GeoServer-Dev-f3819232.html

--
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-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel



--
Regards,
Nuno Oliveira
==
GeoServer Professional Services from the experts! Visithttp://goo.gl/it488V  
for more information.
==

Nuno Miguel Carvalho Oliveira
@nmcoliveira
Software Engineer

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-devel

[Geoserver-devel] Jenkins build is back to normal : geoserver-master #5664

2018-03-21 Thread monitor 
See 



--
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-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] Build failed in Jenkins: geoserver-2.13.x #32

2018-03-21 Thread monitor 
See 


Changes:

[Alessio Fabiani] Log level to FINEST

[Alessio Fabiani] Log level to FINEST

--
[...truncated 542.06 KB...]
[INFO] 
[INFO] Skipping GWC UI Module
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping GeoServer INSPIRE Extensions
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Ysld GeoServer Plugin
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping GeoServer CSS Styling
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping WCS UI Module
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Application Schema Integration Test
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Importer Core Module
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping WCS NetCDF output Module
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Security UI JDBC Module
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Security UI LDAP Module
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping GeoServer Security Extension Modules
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping OGR WPS
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Web process status sharing with Hazelcast
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Web

[Geoserver-devel] Build failed in Jenkins: geoserver-master #5662

2018-03-21 Thread monitor 
See 


Changes:

[Alessio Fabiani] Log level to FINEST

[Alessio Fabiani] Log level to FINEST

--
[...truncated 542.43 KB...]
[INFO] 
[INFO] Skipping GWC UI Module
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping GeoServer INSPIRE Extensions
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Ysld GeoServer Plugin
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping GeoServer CSS Styling
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping WCS UI Module
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Application Schema Integration Test
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Importer Core Module
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping WCS NetCDF output Module
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Security UI JDBC Module
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Security UI LDAP Module
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping GeoServer Security Extension Modules
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Catalog Services for the Web core module
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping OGR WPS
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Web

[Geoserver-devel] SLD from Postgis or from GeoPackage

2018-03-21 Thread Jorge Gustavo Rocha 
Hi devs,

QGIS can save the style back to the provider (to Postgis and to
GeoPackage). The style is stored on a table called layers_style. On
Postgis, the table is stored in the public schema.

The table has a column to store the native QGIS style format and another
column to store the SLD style (stylesld).

I would like to use the SLD style stored on layers_style table on
Geoserver. It would improve the interoperability between QGIS and Geoserver.

It can be done both for Postgis and for GeoPackage stores. For example,
when publishing a GeoPackahe layer, it would be nice to use the SLD
already stored in the GeoPackage. The same for Postgis.

The layers_table [1] also has a useasdefault column. It would be super
cool to immediately render the layer using that default style for the layer.

I would appreciate your feedback regarding this use case.

I've done a simple mockup [2] to improve the Publishing tab for the
layer. It adds one more list of styles. The user can choose from the
'Available styles' list and also from the 'Available style in Postgis'
(or 'Available style in GeoPackage') list.

The store (when connecting to Postgis) is always related with a schema
that might be not the public. To support this use case, we need to add
an additional connection to the database to the public schema using the
same credentials.

Regards from Bonn Code Sprint,

Jorge Gustavo


[1] CREATE TABLE public.layer_styles (
id integer NOT NULL DEFAULT nextval('layer_styles_id_seq'::regclass),
f_table_catalog character varying COLLATE pg_catalog."default",
f_table_schema character varying COLLATE pg_catalog."default",
f_table_name character varying COLLATE pg_catalog."default",
f_geometry_column character varying COLLATE pg_catalog."default",
stylename text COLLATE pg_catalog."default",
styleqml xml,
stylesld xml,
useasdefault boolean,
description text COLLATE pg_catalog."default",
owner character varying(63) COLLATE pg_catalog."default",
ui xml,
update_time timestamp without time zone DEFAULT now(),
CONSTRAINT layer_styles_pkey PRIMARY KEY (id)
);

[2]
https://www.dropbox.com/s/nh72i4tv21y1h0o/mockup%20with%20styles%20from%20postgis.png?dl=0

-- 
Geomaster, Lda
Avenida Barros e Soares, 423
Nogueira
4715-214 Braga
NIF 510906109
Tm +351 910333888
Email j...@geomaster.pt
Site geomaster.pt
GPS 41.53322,-8.41929

--
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-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] [JIRA] (GEOS-8656) GeoServer v2.13.0 Web User Administration has corrupted display corrupted character for french language

2018-03-21 Thread Fabrice Chauvet (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Fabrice Chauvet created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 GeoServer /  GEOS-8656  
 
 
  GeoServer v2.13.0 Web User Administration has corrupted display corrupted character for french language   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 2.13.0  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 UI  
 
 
Created: 
 21/Mar/18 3:00 PM  
 
 
Priority: 
  Low  
 
 
Reporter: 
 Fabrice Chauvet  
 

  
 
 
 
 

 
 GeoServer v2.13.0 Web User Administration has corrupted display corrupted character for french language. It seems that a one month commit has corrupted ressource file encoding. Just setup your brower in french language first and display web user administration to see the corruption.  
 

  
 
 
  
 

 
 
 

 
 
 Add Comment

[Geoserver-devel] Support for renaming published dimensions

2018-03-21 Thread Matthew Campbell 
Good morning,

As there is currently no OGC method (that I am aware of) for dimension 
discovery, clients have to know what dimension names to use when interacting 
with a multi-dimensional OGC service.  Even in instances where dimension 
attribution could be used to infer the type of dimension, there is no way to 
differentiate the purposes of similar typed dimensions other than the dimension 
name until something resembling dimension discovery is standardized. For 
example,  a forecast coverage may have two time dimensions - one is the 
forecast model run time and one is forecast validity time. 
The client has to "know" that the dimension "reference_time" is the forecast 
model run time, and that "time" is the forecast validity time.  Furthermore, 
creators of software clients have to embed this special knowledge into client 
software.  As a result, the service owners must be able to advertise dimension 
names consistently, regardless of changes in underlying reader / data libraries 
in order to maintain client compatibility and conform to any organizational 
standard names or naming conventions.

I’d like to offer my current use case as an example:

Under normal circumstances, we use the FMRC capabilities provided by 
netCDF-java via featureCollection XML files to aggregate datasets with 
different runtimes (these datasets are themselves NCML aggregations of .nc 
files). When opening such a featureCollection in java, we get a dataset that 
that has a dimension variable named ‘run’ for the different run times, and 
everything works beautifully.  However, I’m working on a project where we have 
a custom runtime dimension configured as “reference_time” which is a 
requirement from our customer.  When the netCDF plugin encounters the metadata 
configuration for the custom dimension in the coverage configuration it 
attempts to look up a “reference_time” dimension in the netCDF dataset. In this 
case, the plugin will not locate the correct runtime dimensions and throws a 
null pointer exception in some WCS / WMS operations.  The exceptions in the 
service occur because Geoserver assumes that coverages are configured a certain 
way.
I am proposing a design for Geoserver to allow the user to define what the 
custom dimension name is, thereby giving the implementers greater flexibility 
and enable a way to get past the null pointer exception as well as allowing 
Buisness level standards for naming conventions with their interfaces.

I envision a setting in the dimension tab when viewing a published layer which 
will map custom dimension names available in the dataset to a user defined 
string.  This string would be stored in the coverage.xml under the custom 
dimension element as an advertised name, perhaps as an example: 
“run”.  When Geoserver then computes the custom 
dimension (and here is where I’m not sure it should ultimately be done) for 
example, when determining the “dimensionName” (as used in 
AbstractDefaultValueSelectonStrategy.java 
)
 Geoserver will first check for the “” element and use it’s 
contents henceforth, otherwise default to the custom dimension name as usual.


Thank you for your time,
Matt Campbell--
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-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] [JIRA] (GEOS-8655) WMS 1.3 GetMap request significantly slower than WMS 1.1.0 since GeoServer 2.11.4

2018-03-21 Thread Manuel Timita (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Manuel Timita created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 GeoServer /  GEOS-8655  
 
 
  WMS 1.3 GetMap request significantly slower than WMS 1.1.0 since GeoServer 2.11.4   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 2.11.4, 2.12.2, 2.13.0  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 screenshot_1_wms_1.1.0.png, screenshot_2_wms_1.3.0.png, screenshot_3_wms_1.1.0.png, screenshot_4_wms_1.3.0.png  
 
 
Components: 
 WMS  
 
 
Created: 
 21/Mar/18 1:12 PM  
 
 
Environment: 
 Ubuntu 16.04.1 LTS PostgreSQL 9.6 + PostGIS 2.3 Tomcat 9  
 
 
Priority: 
  Medium  
 
 
Reporter: 
 Manuel Timita  
 

  
 
 
 
 

 
 I noticed that, since version 2.11.4, the WMS 1.3.0 GetMap requests were returning the tiles very slowly. I tried all the GeoServer versions, from 2.11.4 to 2.13.0, and the same happens. The styling language used seems to also have an impact. I've been using the GeoServer default config, plus the following: Marlin (I tried from version 7.5 to version 9.1), WPS plugin, and YSLD. No other plugin or library, like Image IO and such have been added. If I switch to WMS version 1.1, it all works well.  Geoserver 2.10.4 works fine using either version, and either styling language. Details I created a layer from a PostGIS table with 600K polygons (whether it's an SQL view, or a simple FeatureType, the problem seems to be the same). Then: 1) Styled with the default polygon SLD, and requesting GetMap with WMS 1.1.0, the map is returned in 3 seconds. See screenshot 1.

[Geoserver-devel] Upgrade printing-plugin to use geosolutions fork of mapfish-print 2.x

2018-03-21 Thread Mauro Bartolomeoli 
Hi,
since probably upgrading our dependency on mapfish-print to latest versions
is not going to happen quickly, I was wondering if switching to our
improved 2.x version would be a good move.

It would be a very low effort upgrade that will enable several improvements
(one for all, clustering support).

Other improvements are listed here:
https://github.com/geosolutions-it/mapfish-print/wiki

Any thought?


-- 

Regards,

Mauro Bartolomeoli

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

Dott. Mauro Bartolomeoli
@mauro_bart
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-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] [JIRA] (GEOS-8654) Error during GeoServer bootstrapping (InsufficientAuthenticationException)

2018-03-21 Thread Christian Mueller (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christian Mueller created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 GeoServer /  GEOS-8654  
 
 
  Error during GeoServer bootstrapping (InsufficientAuthenticationException)   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 2.12.1, 2.13.0  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 Security  
 
 
Created: 
 21/Mar/18 9:18 AM  
 
 
Priority: 
  High  
 
 
Reporter: 
 Christian Mueller  
 

  
 
 
 
 

 
 GeoServer does not load settings of a protected workspace when using Catalog Mode == Mixed Steps to reproduce: 
 
Add a role "testrole" 
Add a workspace "testworkspace" 
 Add the following data access rules: testworkspace.*.r  testworkspace.*.w and assign these rules to the role "testrole" Restart GeoServer and have a look at the log file. There is a stack trace caused by org.springframework.security.authentication.InsufficientAuthenticationException As a consequence, GeoServer does not load the workspace settings for "testworkspace" and falls back to the default values. Unfortunately there is no indicator on the admin GUI that something went wrong. A debug session shows that GeoServer uses the SecureCatalog implementation during bootstrapping. During this phase is the current user is null (treated as anonymous). Ideas/questions: 1) Is it possible to use the non secure implementation of the catalog during bootstrapping 2) If not, does it make sense to boostrap as "admin" or even better as "root" user.