Re: [Geoserver-users] Getting features intersecting with a polygon

[Andrea Aime]

Hi Roel,
yes, adding a ticket would not hurt. Is there anybody around with a more
recent SQL server release that can perform
similar tests? It would be great to know if this finding is valid cross
version

Cheers
Andrea


On Mon, Sep 28, 2015 at 5:59 PM, Roel De Nijs 
wrote:

> Finally after 6 months I have had some time to investigate this further.
> Of course I didn’t know the polygon anymore from my initial simple test, so
> I had to use another one. We are still using SQL Server 2008 R2.
>
>
>
> I did a very simple test using one of our queries with different
> combinations of Filter and/or STIntersects in the where-clause:
>
> a) only Filter: 80836 records in 4215ms
>
> b) only STIntersects: 77729 records in 5017ms
>
> c) Filter and STIntersects: 77729 records in 11364ms
>
> I executed every query using the SQL Server Management Studio and before
> each query I removed the query plans.
>
>
>
> Then I executed every query again using Microsoft JDBC Driver for SQL
> Server (version 4.0.2206.100) and the time needed to execute the query is
> pretty similar. Before executing each query, I removed the query plans as
> well.
>
> a) only Filter: 80836 records in 4459ms
>
> b) only STIntersects: 77729 records in 5180ms
>
> c) Filter and STIntersects: 77729 records in 11604ms
>
>
>
>
>
> If it’s still useful, I will open a jira ticket in the next few days and
> share these results.
>
>
>
> Kind regards,
>
> Roel De Nijs
>
> Senior Java Developer
>
>
>
> *Van:* andrea.a...@gmail.com [mailto:andrea.a...@gmail.com] *Namens *Andrea
> Aime
> *Verzonden:* vrijdag 27 maart 2015 21:40
> *Aan:* Roel De Nijs 
> *CC:* GeoServer Mailing List List 
> *Onderwerp:* Re: [Geoserver-users] Getting features intersecting with a
> polygon
>
>
>
> On Fri, Mar 27, 2015 at 7:36 PM, Roel De Nijs 
> wrote:
>
> We use a few custom-written queries which use only an STIntersects in the
> where-clause and the spatial index is mentioned in the execution plan of
> this query. So I think SQL Server has learned to use the spatial index :)
> According to this blog post [1] it's very important to upgrade (if
> possible)
> to SQL Server 2008 SP1 if you want to ensure the spatial index is being
> used. (We use SQL Server 2008 R2)
>
>
>
> Nah, we had no ends of problems with sql server 2012, that's why we got
> the sponsoring
>
> to add the query hints in just this database.
>
> But it's nice that at least with simple queries, no parallel execution
> options on,
>
> the optimizer can do its job as it should (I guess we just got spoiled by
>
> postgresql/postgis, there are no query hints, and at least in the last 8
> years,
>
> I had no need to use them anyways, Oracle and SQLServer are disappointing
>
> by comparison, but not "bad" in absolute terms).
>
>
>
> I did a very simple test using one of our queries with different
> combinations of Filter and/or STIntersects in the where-clause:
> a) only Filter: 76159 records in 9032ms
> b) only STIntersects: 67490 records in 11472ms
> c) Filter and STIntersects: 67490 records in 21472ms
>
>
>
> Interesting, that's good data. Could you open a ticket asking for an
> improvement (mind,
>
> tomorrow we switch to a new jira server, so it's either tonight, or next
> week).
>
> We need to determine if the above are valid on all versions, or else, need
> to setup
>
> some version recognition and act accordingly
>
>
>
> I executed every query using the SQL Server Management Studio and before
> each query I removed the query plans.
>
>
>
> Mind, the query performance from native sql server tools, and from jdbc,
> sometimes
>
> vary a lot.
>
>
>
> I tried the 3rd point from the blog post [1] as well, but no significant
> changes in query execution time, nor in query execution plans.
>
> [1]
>
> http://www.sqlskills.com/blogs/bobb/how-to-ensure-your-spatial-index-is-being-used/
>
>
>
> Ok, this is a where postgis is vastly superior to both oracle and
> sqlserver.
>
> In postgis you send a query with a bbox the bbox is parsed before the
> query planner
>
> runs, and it can intelligently decide whether to use the index or a
> sequential scan.
>
> The threshold to make index scans faster is surprisingly low, something
> like extracting
>
> 5 to 7% of your data, this is because you have to jump a lot back and
> forth in the
>
> index to collect the record ids, causing quite a bit of extra wait on
> spinnnig disk storage.
>
>
>
> In SQL Server and Oracle, as far as I know, the query is planned before
> the functions
>
> creating the reference geometries are called, so the optimizer normally
> decides to use
>
> the spatial index (minus some patological cases, e.g., parallel query
> execution) and
>
> that's just wrong, performance wise, when you
>
> are trying to access a significant portion of your data (which in mapping,
> is not at all uncommon).
>
>
>
> Soo.. in order to give the optimizer a chance to figure out how much data
> is actually
>
> going to be read, we should go though that @declare business... and this
>

Re: [Geoserver-users] Multiple Layers in GetLegendGraphic?

[Andrea Aime]

On Fri, Sep 25, 2015 at 6:48 PM, Martin Davis  wrote:

> It looks like GetLegendGraphic only supports requesting a legend for a
> single layer. Could this be generalized to allow multiple layers being
> requested?
>

Hi Martin,
sorry for chiming in late. The GetLegendGraphic internal code already
supports a list of layers, this feature has been added by Mauro
almost two years ago when adding supporting layer groups in
GetLegendGraphic (which is, as usual, exploded in its internal list
of layers at parsing time).

What is missing, as far as I can see, is just the code that would parse a
comma separate list of layers/styles in the request, as far as I know

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 Poggio alle Viti 1187
55054  Massarosa (LU)
Italy
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.

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

Re: [Geoserver-users] Multiple Layers in GetLegendGraphic?

[Martin Davis]

Thanks, Jody.  Good to know that it's a relatively simple extension.  Not
sure if/when we'll have time to do development on this thiough.

And the idea of a map/scale-aware GetLegendGraphic is a good one.  Legends
for our maps can get very long, so any way of cutting them down to size is
useful.



On Sun, Sep 27, 2015 at 2:17 PM, Jody Garnett 
wrote:

> Hey Martin:
>
> I am sure we could do that, we already have a bunch of options to try and
> pass in current scale/dpi to try and get a visual that matches what is on
> the screen.
>
> The code is here:
>
>
> https://github.com/geoserver/geoserver/blob/master/src/wms/src/main/java/org/geoserver/wms/GetLegendGraphicRequest.java
>
> The important part is:
>
>  *  LAYER Required Layer for which to produce
> legend graphic. A layergroup can be specified, too. In this case, STYLE and
> RULE parameters can have multiple values (separated by commas), one for
> each of the group layers.
>
> So if style and rule are already setup it should be fairly easy to allow
> layer to have multiple values separated by commas.
>
> Indeed internally the code already has:
>
> /** The featuretype(s) of the requested LAYER(s) */
> private List layers=new ArrayList();
>
> So no change to the data structure and logic should be required, just
> parser and test case.
>
> Aside: As long as we are dreaming here I would love to have one that
> operates like GetFeatureInfo - and includes a reference GetMap complete
> with BBox (and thus could only show the layers / rules that end up having
> something on the screen.
>
> --
> Jody Garnett
>
> On 25 September 2015 at 09:48, Martin Davis  wrote:
>
>> It looks like GetLegendGraphic only supports requesting a legend for a
>> single layer. Could this be generalized to allow multiple layers being
>> requested?
>>
>> The use case is that in some simple clients it's difficult to display an
>> arbitrary-length list of images (e.g. Jasper Reports).
>>
>>
>> --
>>
>> ___
>> Geoserver-users mailing list
>> Geoserver-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>>
>>
>
--
___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] sort on sourceType in mapping file

[Ben Caradoc-Davies]

Wen,

as far as I know, it is not possible to specify a "sort by" ordering of 
a source type. The app-schema plugin uses the natural order of the 
source data store; I am not even sure if it sorts by primary key under 
all circumstances (such as denormalised sources when joining is not used 
(see the mapping file page in the manual)). If you need a particular 
ordering, a view seems to me like a good solution.

Kind regards,
Ben.

On 29/09/15 10:35, Yin, Wentao (IS) (Contr) wrote:
> Is it possible to specify the "sort by" when using sourceType?
>
>   datastore
>  GEOLOGICUNIT
>
> If I want to sort by a column which is not the primary key, do I have to use 
> View instead of Table?
>
> Thanks
> Wen
>
>
>
> --
> ___
> Geoserver-users mailing list
> Geoserver-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>

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

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

[Geoserver-users] sort on sourceType in mapping file

[Yin, Wentao (IS) (Contr)]

Is it possible to specify the "sort by" when using sourceType?

datastore
GEOLOGICUNIT

If I want to sort by a column which is not the primary key, do I have to use 
View instead of Table?

Thanks
Wen



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

Re: [Geoserver-users] EXT :Re: Oracle_Data_ref_set.sql

[Yin, Wentao (IS) (Contr)]

Thanks, Ben

Wen

-Original Message-
From: Ben Caradoc-Davies [mailto:b...@transient.nz] 
Sent: Monday, September 28, 2015 5:22 PM
To: Yin, Wentao (IS) (Contr); geoserver-users@lists.sourceforge.net
Subject: EXT :Re: [Geoserver-users] Oracle_Data_ref_set.sql

There is also a page in the developer manual:

App-Schema Online Tests
http://docs.geoserver.org/latest/en/developer/programming-guide/app-schema/index.html

On 29/09/15 09:28, Ben Caradoc-Davies wrote:
> There is some more information on the these tests here:
> https://www.seegrid.csiro.au/wiki/Infosrvices/DataReferenceSet
> https://www.seegrid.csiro.au/wiki/Infosrvices/JenkinsGeoserverMasterTe
> chnicalNotes
> https://osgeo-org.atlassian.net/browse/GEOS-6883

--
Ben Caradoc-Davies 
Director
Transient Software Limited  New Zealand
--
___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] Oracle_Data_ref_set.sql

[Ben Caradoc-Davies]

There is also a page in the developer manual:

App-Schema Online Tests
http://docs.geoserver.org/latest/en/developer/programming-guide/app-schema/index.html

On 29/09/15 09:28, Ben Caradoc-Davies wrote:
> There is some more information on the these tests here:
> https://www.seegrid.csiro.au/wiki/Infosrvices/DataReferenceSet
> https://www.seegrid.csiro.au/wiki/Infosrvices/JenkinsGeoserverMasterTechnicalNotes
> https://osgeo-org.atlassian.net/browse/GEOS-6883

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

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

Re: [Geoserver-users] EXT :Re: Oracle_Data_ref_set.sql

[Yin, Wentao (IS) (Contr)]

Got it. Thank you, Ben. 

Wen

-Original Message-
From: Ben Caradoc-Davies [mailto:b...@transient.nz] 
Sent: Monday, September 28, 2015 4:28 PM
To: Yin, Wentao (IS) (Contr); geoserver-users@lists.sourceforge.net
Subject: EXT :Re: [Geoserver-users] Oracle_Data_ref_set.sql

Wen,

Oracle_Data_ref_set.sql can found in refdataset-1.0-1.0.7.jar, which you can 
get from your local maven repository or the osgeo maven repository:
http://download.osgeo.org/webdav/geotools/org/geotools/data/refdataset-1.0/1.0.7/refdataset-1.0-1.0.7.jar

In March I wrote: "as far as I know, the data reference set exists only as a 
jar file. The management workflow is to obtain the jar, unzip it, edit the 
enclosed SQL, re-zip it, increment the version number, and manually deploy it 
to the osgeo maven repository."
http://sourceforge.net/p/geotools/mailman/message/33529509/

There is some more information on the these tests here:
https://www.seegrid.csiro.au/wiki/Infosrvices/DataReferenceSet
https://www.seegrid.csiro.au/wiki/Infosrvices/JenkinsGeoserverMasterTechnicalNotes
https://osgeo-org.atlassian.net/browse/GEOS-6883

Kind regards,
Ben.

On 29/09/15 01:51, Yin, Wentao (IS) (Contr) wrote:
> Hi,
>
> Does anyone know where to find Oracle_Data_ref_set.sql  for 
> gs-app-schema-test? It is no included in the source download.
>
> Thanks,
> Wen
>
>
>
> --
> 
>
>
>
> ___
> Geoserver-users mailing list
> Geoserver-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>

--
Ben Caradoc-Davies 
Director
Transient Software Limited  New Zealand
--
___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] Oracle_Data_ref_set.sql

[Ben Caradoc-Davies]

Wen,

Oracle_Data_ref_set.sql can found in refdataset-1.0-1.0.7.jar, which you 
can get from your local maven repository or the osgeo maven repository:
http://download.osgeo.org/webdav/geotools/org/geotools/data/refdataset-1.0/1.0.7/refdataset-1.0-1.0.7.jar

In March I wrote: "as far as I know, the data reference set exists only 
as a jar file. The management workflow is to obtain the jar, unzip it, 
edit the enclosed SQL, re-zip it, increment the version number, and 
manually deploy it to the osgeo maven repository."
http://sourceforge.net/p/geotools/mailman/message/33529509/

There is some more information on the these tests here:
https://www.seegrid.csiro.au/wiki/Infosrvices/DataReferenceSet
https://www.seegrid.csiro.au/wiki/Infosrvices/JenkinsGeoserverMasterTechnicalNotes
https://osgeo-org.atlassian.net/browse/GEOS-6883

Kind regards,
Ben.

On 29/09/15 01:51, Yin, Wentao (IS) (Contr) wrote:
> Hi,
>
> Does anyone know where to find Oracle_Data_ref_set.sql  for 
> gs-app-schema-test? It is no included in the source download.
>
> Thanks,
> Wen
>
>
>
> --
>
>
>
> ___
> Geoserver-users mailing list
> Geoserver-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>

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

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

Re: [Geoserver-users] Raster projections

[David Haynes II]

Ok,
Now I understand what you are asking about. Thank you Andrea, but for now
this issue seems to occur when using the image-mosaic JDBDC connection. I
will try to reproduce this issue using other data formats.

On Mon, Sep 28, 2015 at 11:16 AM, Andrea Aime 
wrote:

> On Mon, Sep 28, 2015 at 5:58 PM, David Haynes II  wrote:
>
>> what do you mean by "I believe you should have all the files that you
>> need. The raster is loaded using the PostgreSQL JDBC connection."
>>
>> >> I think I have given you all the files if there is something missing
>> please let me know. I am using the image mosaic JDBC module. Do you need
>> that configuration file as well?
>>
>
> The main issue is, I cannot help you if you are using the image mosaic
> JDBC module. If the issue can be reproduced with a plain geotiff,
> then I can have a look, but you will have to tell me if that's the case
> (I'm going to help you in my spare time after all).
> If it's image mosaic JDBC specific, Christian is probably the best person
> to check what's going on after it.
>
> 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 Poggio alle Viti 1187
> 55054  Massarosa (LU)
> Italy
> 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.
>
> ---
>



-- 
David Haynes, Ph.D.
Research Associate Terra Populus
Minnesota Population Center
612-626-3933
www.terrapop.org
--
___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] GetMap-request with CQL_FILTER too slow

[Andrea Aime]

Hi,
have you tried forcing the spatial index usage, it's a flag in the store
configuration (if you have
a GeoServer recent enough... 2.6.x or 2.7.x, cannot remember when exactly
we added those)

Cheers
Andrea


On Mon, Sep 28, 2015 at 6:35 PM, Roel De Nijs 
wrote:

> Hi list,
>
>
>
>
>
> We have a SQL Server 2008 R2 database with a spatial table for every
> feature type (node, pipe, storagearea,…). Our application has two type of
> users: the normal user and the geo-limited user. The first one can view all
> the infrastructure, the latter one is restricted and can only see the
> infrastructure within a polygon (representing a city or some other area).
>
>
>
> To implement this restriction we add a CQL_FILTER to the GetMap-requests.
> But these requests are much slower than the non-limited requests. I
> collected some reference data. Because these data is quite verbose
> (certainly for the geo-limited user), I share just the details of one tile.
>
>
>
> So for a normal user, the geoserver request takes 660ms.
>
>
>
> finished[660] parameters[[FORMAT=image/png, TRANSPARENT=TRUE, SERVICE=WMS, 
> VERSION=1.1.1, REQUEST=GetMap, 
> STYLES=knoopEigenaar,leidingEigenaar,terugslagklep,overstort,afsluiter,knijpconstructie,pomp,wervelventiel,inlaatEigenaar,uitlaatEigenaar,knelpuntStatus,reservoirEigenaar,projectToestand,
>  
> LAYERS=knoop,leiding,terugslagklep,overstort,afsluiter,knijpconstructie,pomp,wervelventiel,inlaat,uitlaat,knelpunt,reservoir,project,
>  SRS=EPSG:31370, 
> BBOX=116547.44384766,188202.28271484,116813.06835938,188467.90722656, 
> WIDTH=512, HEIGHT=512]]
>
>
>
> But fort he geo-limited user, the geoserver request is 5x slower (3063ms).
>
>
>
> finished[3063] parameters[[FORMAT=image/png, TRANSPARENT=TRUE,
> SERVICE=WMS, VERSION=1.1.1, REQUEST=GetMap,
> STYLES=knoopEigenaar,leidingEigenaar,terugslagklep,overstort,afsluiter,knijpconstructie,pomp,wervelventiel,inlaatEigenaar,uitlaatEigenaar,knelpuntStatus,reservoirEigenaar,projectToestand,
> LAYERS=knoop,leiding,terugslagklep,overstort,afsluiter,knijpconstructie,pomp,wervelventiel,inlaat,uitlaat,knelpunt,reservoir,project,
> SRS=EPSG:31370,
> BBOX=116547.44384766,188202.28271484,116813.06835938,188467.90722656,
> WIDTH=512, HEIGHT=512, CQL_FILTER=INTERSECTS("geom", POLYGON
> ((116547.44384766 188202.28271484, 116547.44384766 188467.90722656,
> 116813.06835938 188467.90722656, 116813.06835938 188202.28271484,
> 116547.44384766 188202.28271484)));INTERSECTS("geom", POLYGON
> ((116547.44384766 188202.28271484, 116547.44384766 188467.90722656,
> 116813.06835938 188467.90722656, 116813.06835938 188202.28271484,
> 116547.44384766 188202.28271484)));INTERSECTS("geom", POLYGON
> ((116547.44384766 188202.28271484, 116547.44384766 188467.90722656,
> 116813.06835938 188467.90722656, 116813.06835938 188202.28271484,
> 116547.44384766 188202.28271484)));INTERSECTS("geom", POLYGON
> ((116547.44384766 188202.28271484, 116547.44384766 188467.90722656,
> 116813.06835938 188467.90722656, 116813.06835938 188202.28271484,
> 116547.44384766 188202.28271484)));INTERSECTS("geom", POLYGON
> ((116547.44384766 188202.28271484, 116547.44384766 188467.90722656,
> 116813.06835938 188467.90722656, 116813.06835938 188202.28271484,
> 116547.44384766 188202.28271484)));INTERSECTS("geom", POLYGON
> ((116547.44384766 188202.28271484, 116547.44384766 188467.90722656,
> 116813.06835938 188467.90722656, 116813.06835938 188202.28271484,
> 116547.44384766 188202.28271484)));INTERSECTS("geom", POLYGON
> ((116547.44384766 188202.28271484, 116547.44384766 188467.90722656,
> 116813.06835938 188467.90722656, 116813.06835938 188202.28271484,
> 116547.44384766 188202.28271484)));INTERSECTS("geom", POLYGON
> ((116547.44384766 188202.28271484, 116547.44384766 188467.90722656,
> 116813.06835938 188467.90722656, 116813.06835938 188202.28271484,
> 116547.44384766 188202.28271484)));INTERSECTS("geom", POLYGON
> ((116547.44384766 188202.28271484, 116547.44384766 188467.90722656,
> 116813.06835938 188467.90722656, 116813.06835938 188202.28271484,
> 116547.44384766 188202.28271484)));INTERSECTS("geom", POLYGON
> ((116547.44384766 188202.28271484, 116547.44384766 188467.90722656,
> 116813.06835938 188467.90722656, 116813.06835938 188202.28271484,
> 116547.44384766 188202.28271484)));INTERSECTS("geom", POLYGON
> ((116547.44384766 188202.28271484, 116547.44384766 188467.90722656,
> 116813.06835938 188467.90722656, 116813.06835938 188202.28271484,
> 116547.44384766 188202.28271484)));INTERSECTS("geom", POLYGON
> ((116547.44384766 188202.28271484, 116547.44384766 188467.90722656,
> 116813.06835938 188467.90722656, 116813.06835938 188202.28271484,
> 116547.44384766 188202.28271484)));INTERSECTS("geom", POLYGON
> ((116547.44384766 188202.28271484, 116547.44384766 188467.90722656,
> 116813.06835938 188467.90722656, 116813.06835938 188202.28271484,
> 116547.44384766 188202.28271484)))]]
>
>
>
>
>
> I want to know what could be the cause(s) of this performance issue. And
> if I can make some changes to improve per

[Geoserver-users] GetMap-request with CQL_FILTER too slow

[Roel De Nijs]

Hi list,


We have a SQL Server 2008 R2 database with a spatial table for every feature 
type (node, pipe, storagearea,...). Our application has two type of users: the 
normal user and the geo-limited user. The first one can view all the 
infrastructure, the latter one is restricted and can only see the 
infrastructure within a polygon (representing a city or some other area).

To implement this restriction we add a CQL_FILTER to the GetMap-requests. But 
these requests are much slower than the non-limited requests. I collected some 
reference data. Because these data is quite verbose (certainly for the 
geo-limited user), I share just the details of one tile.

So for a normal user, the geoserver request takes 660ms.


finished[660] parameters[[FORMAT=image/png, TRANSPARENT=TRUE, SERVICE=WMS, 
VERSION=1.1.1, REQUEST=GetMap, 
STYLES=knoopEigenaar,leidingEigenaar,terugslagklep,overstort,afsluiter,knijpconstructie,pomp,wervelventiel,inlaatEigenaar,uitlaatEigenaar,knelpuntStatus,reservoirEigenaar,projectToestand,
 
LAYERS=knoop,leiding,terugslagklep,overstort,afsluiter,knijpconstructie,pomp,wervelventiel,inlaat,uitlaat,knelpunt,reservoir,project,
 SRS=EPSG:31370, 
BBOX=116547.44384766,188202.28271484,116813.06835938,188467.90722656, 
WIDTH=512, HEIGHT=512]]

But fort he geo-limited user, the geoserver request is 5x slower (3063ms).

finished[3063] parameters[[FORMAT=image/png, TRANSPARENT=TRUE, SERVICE=WMS, 
VERSION=1.1.1, REQUEST=GetMap, 
STYLES=knoopEigenaar,leidingEigenaar,terugslagklep,overstort,afsluiter,knijpconstructie,pomp,wervelventiel,inlaatEigenaar,uitlaatEigenaar,knelpuntStatus,reservoirEigenaar,projectToestand,
 
LAYERS=knoop,leiding,terugslagklep,overstort,afsluiter,knijpconstructie,pomp,wervelventiel,inlaat,uitlaat,knelpunt,reservoir,project,
 SRS=EPSG:31370, 
BBOX=116547.44384766,188202.28271484,116813.06835938,188467.90722656, 
WIDTH=512, HEIGHT=512, CQL_FILTER=INTERSECTS("geom", POLYGON ((116547.44384766 
188202.28271484, 116547.44384766 188467.90722656, 116813.06835938 
188467.90722656, 116813.06835938 188202.28271484, 116547.44384766 
188202.28271484)));INTERSECTS("geom", POLYGON ((116547.44384766 
188202.28271484, 116547.44384766 188467.90722656, 116813.06835938 
188467.90722656, 116813.06835938 188202.28271484, 116547.44384766 
188202.28271484)));INTERSECTS("geom", POLYGON ((116547.44384766 
188202.28271484, 116547.44384766 188467.90722656, 116813.06835938 
188467.90722656, 116813.06835938 188202.28271484, 116547.44384766 
188202.28271484)));INTERSECTS("geom", POLYGON ((116547.44384766 
188202.28271484, 116547.44384766 188467.90722656, 116813.06835938 
188467.90722656, 116813.06835938 188202.28271484, 116547.44384766 
188202.28271484)));INTERSECTS("geom", POLYGON ((116547.44384766 
188202.28271484, 116547.44384766 188467.90722656, 116813.06835938 
188467.90722656, 116813.06835938 188202.28271484, 116547.44384766 
188202.28271484)));INTERSECTS("geom", POLYGON ((116547.44384766 
188202.28271484, 116547.44384766 188467.90722656, 116813.06835938 
188467.90722656, 116813.06835938 188202.28271484, 116547.44384766 
188202.28271484)));INTERSECTS("geom", POLYGON ((116547.44384766 
188202.28271484, 116547.44384766 188467.90722656, 116813.06835938 
188467.90722656, 116813.06835938 188202.28271484, 116547.44384766 
188202.28271484)));INTERSECTS("geom", POLYGON ((116547.44384766 
188202.28271484, 116547.44384766 188467.90722656, 116813.06835938 
188467.90722656, 116813.06835938 188202.28271484, 116547.44384766 
188202.28271484)));INTERSECTS("geom", POLYGON ((116547.44384766 
188202.28271484, 116547.44384766 188467.90722656, 116813.06835938 
188467.90722656, 116813.06835938 188202.28271484, 116547.44384766 
188202.28271484)));INTERSECTS("geom", POLYGON ((116547.44384766 
188202.28271484, 116547.44384766 188467.90722656, 116813.06835938 
188467.90722656, 116813.06835938 188202.28271484, 116547.44384766 
188202.28271484)));INTERSECTS("geom", POLYGON ((116547.44384766 
188202.28271484, 116547.44384766 188467.90722656, 116813.06835938 
188467.90722656, 116813.06835938 188202.28271484, 116547.44384766 
188202.28271484)));INTERSECTS("geom", POLYGON ((116547.44384766 
188202.28271484, 116547.44384766 188467.90722656, 116813.06835938 
188467.90722656, 116813.06835938 188202.28271484, 116547.44384766 
188202.28271484)));INTERSECTS("geom", POLYGON ((116547.44384766 
188202.28271484, 116547.44384766 188467.90722656, 116813.06835938 
188467.90722656, 116813.06835938 188202.28271484, 116547.44384766 
188202.28271484)))]]


I want to know what could be the cause(s) of this performance issue. And if I 
can make some changes to improve performance. Any pointers, hints,... are more 
than welcome. I take anything I can get :-) And if it is a really specific 
issue, I'll try debugging some geoserver code.



Kind regards,

Roel De Nijs

Senior Java Developer




Volg Aquafin op Facebook | 
Twitter | 
YouTube

Re: [Geoserver-users] Raster projections

[Andrea Aime]

On Mon, Sep 28, 2015 at 5:58 PM, David Haynes II  wrote:

> what do you mean by "I believe you should have all the files that you
> need. The raster is loaded using the PostgreSQL JDBC connection."
>
> >> I think I have given you all the files if there is something missing
> please let me know. I am using the image mosaic JDBC module. Do you need
> that configuration file as well?
>

The main issue is, I cannot help you if you are using the image mosaic JDBC
module. If the issue can be reproduced with a plain geotiff,
then I can have a look, but you will have to tell me if that's the case
(I'm going to help you in my spare time after all).
If it's image mosaic JDBC specific, Christian is probably the best person
to check what's going on after it.

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 Poggio alle Viti 1187
55054  Massarosa (LU)
Italy
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.

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

Re: [Geoserver-users] Getting features intersecting with a polygon

[Roel De Nijs]

Finally after 6 months I have had some time to investigate this further. Of 
course I didn’t know the polygon anymore from my initial simple test, so I had 
to use another one. We are still using SQL Server 2008 R2.

I did a very simple test using one of our queries with different combinations 
of Filter and/or STIntersects in the where-clause:
a) only Filter: 80836 records in 4215ms
b) only STIntersects: 77729 records in 5017ms
c) Filter and STIntersects: 77729 records in 11364ms
I executed every query using the SQL Server Management Studio and before each 
query I removed the query plans.

Then I executed every query again using Microsoft JDBC Driver for SQL Server 
(version 4.0.2206.100) and the time needed to execute the query is pretty 
similar. Before executing each query, I removed the query plans as well.
a) only Filter: 80836 records in 4459ms
b) only STIntersects: 77729 records in 5180ms
c) Filter and STIntersects: 77729 records in 11604ms


If it’s still useful, I will open a jira ticket in the next few days and share 
these results.

Kind regards,
Roel De Nijs
Senior Java Developer

Van: andrea.a...@gmail.com [mailto:andrea.a...@gmail.com] Namens Andrea Aime
Verzonden: vrijdag 27 maart 2015 21:40
Aan: Roel De Nijs 
CC: GeoServer Mailing List List 
Onderwerp: Re: [Geoserver-users] Getting features intersecting with a polygon

On Fri, Mar 27, 2015 at 7:36 PM, Roel De Nijs 
mailto:roel.den...@aquafin.be>> wrote:
We use a few custom-written queries which use only an STIntersects in the
where-clause and the spatial index is mentioned in the execution plan of
this query. So I think SQL Server has learned to use the spatial index :)
According to this blog post [1] it's very important to upgrade (if possible)
to SQL Server 2008 SP1 if you want to ensure the spatial index is being
used. (We use SQL Server 2008 R2)

Nah, we had no ends of problems with sql server 2012, that's why we got the 
sponsoring
to add the query hints in just this database.
But it's nice that at least with simple queries, no parallel execution options 
on,
the optimizer can do its job as it should (I guess we just got spoiled by
postgresql/postgis, there are no query hints, and at least in the last 8 years,
I had no need to use them anyways, Oracle and SQLServer are disappointing
by comparison, but not "bad" in absolute terms).

I did a very simple test using one of our queries with different
combinations of Filter and/or STIntersects in the where-clause:
a) only Filter: 76159 records in 9032ms
b) only STIntersects: 67490 records in 11472ms
c) Filter and STIntersects: 67490 records in 21472ms

Interesting, that's good data. Could you open a ticket asking for an 
improvement (mind,
tomorrow we switch to a new jira server, so it's either tonight, or next week).
We need to determine if the above are valid on all versions, or else, need to 
setup
some version recognition and act accordingly

I executed every query using the SQL Server Management Studio and before
each query I removed the query plans.

Mind, the query performance from native sql server tools, and from jdbc, 
sometimes
vary a lot.

I tried the 3rd point from the blog post [1] as well, but no significant
changes in query execution time, nor in query execution plans.

[1]
http://www.sqlskills.com/blogs/bobb/how-to-ensure-your-spatial-index-is-being-used/

Ok, this is a where postgis is vastly superior to both oracle and sqlserver.
In postgis you send a query with a bbox the bbox is parsed before the query 
planner
runs, and it can intelligently decide whether to use the index or a sequential 
scan.
The threshold to make index scans faster is surprisingly low, something like 
extracting
5 to 7% of your data, this is because you have to jump a lot back and forth in 
the
index to collect the record ids, causing quite a bit of extra wait on spinnnig 
disk storage.

In SQL Server and Oracle, as far as I know, the query is planned before the 
functions
creating the reference geometries are called, so the optimizer normally decides 
to use
the spatial index (minus some patological cases, e.g., parallel query 
execution) and
that's just wrong, performance wise, when you
are trying to access a significant portion of your data (which in mapping, is 
not at all uncommon).

Soo.. in order to give the optimizer a chance to figure out how much data is 
actually
going to be read, we should go though that @declare business... and this is 
where we'd
need funding.

Cheers
Andrea

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

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054  Massarosa (LU)
Italy
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 st

Re: [Geoserver-users] Raster projections

[David Haynes II]

what do you mean by "I believe you should have all the files that you need.
The raster is loaded using the PostgreSQL JDBC connection."

>> I think I have given you all the files if there is something missing
please let me know. I am using the image mosaic JDBC module. Do you need
that configuration file as well?



On Mon, Sep 28, 2015 at 10:35 AM, Andrea Aime 
wrote:

> Hi David,
> what do you mean by "I believe you should have all the files that you
> need. The raster is loaded using the PostgreSQL JDBC connection."
>
> Are you using the image mosaic JDBC module? Like, data stored in postgis
> raster?
>
> Cheers
> Andrea
>
>
> On Mon, Sep 28, 2015 at 5:30 PM, David Haynes II  wrote:
>
>> I will send a google drive invitation to your personal e-mails. I am
>> using geoserver 2.7
>>
>> On Mon, Sep 28, 2015 at 9:45 AM, Andrea Aime <
>> andrea.a...@geo-solutions.it> wrote:
>>
>>> Hi David,
>>> we likely need data, style and request to reproduce locally, in order to
>>> provide any help.
>>> Also, which version of GeoServer are you using?
>>>
>>> Cheers
>>> Andrea
>>>
>>>
>>> On Mon, Sep 28, 2015 at 4:31 PM, David Haynes II 
>>> wrote:
>>>
 Hello Jody,

 Thanks for the reply. I seem to be encountering an issue related to
 raster projections and SLD visualization. I shall try to explain.

 The goal is to make an application that allows the user to visualize a
 raster dataset by turning pixel values on and off. Currently we are working
 with the raster dataset GLC2000, which is the landcover classification of
 the world for the year 2000. We have created an SLD for this dataset that
 converts the raster to transparent, setting each pixel value opacity to
 zero. Through the application users can turn on and off raster pixel values
 like water. We simply update the SLD with the env parameter
 'env=lcwater:1'. Now all of the water is visible on the map.


 Here is a subset of the SLD we are currently using
 Title>Global Landcover Legend dynamic
   .Text goes here.

   
 
   
 
>>> ="${env('lcprimveg',0)}" />
 >>> ="${env('lcbrdevgrn',0)}"/>
 >>> ="${env('lcdecidcl',0)}" />
 >>> ="${env('lcdecidop',0)}" />
 >>> ="${env('lcndlevgrn',0)}"/>
 >>> ="${env('lcndldecid',0)}" />
 >>> ="${env('lcmxlftree',0)}" />
 >>> ="${env('lcaqtrfrsh',0)}" />
 >>> ="${env('lcwater',0)}" />


 The problem we are having is that the raster style (SLD) is not working
 at all map extents. The raster layer has the native SRS set as 4326 and the
 declared SRS set to 3857. SRS handling is set to project native to
 declared. The interpolation is set to nearest neighbor and the default SLD
 is glc_dynamic.

 I preview the glc_dynamic raster layer through geoserver everything
 shows up fine, the screen is blank.I add the &env=lcwater:1 parameter and
 now I see water across the whole map. The only thing visible on the map is
 water. Preview scale is at 1:279M, rough bbox dimensions are -19144282.29W
 and 13927505.70963E. Now if I Pan west to -19535201.77042 the entire color
 legend is now visible on the map. This same error will occur if I pan to
 far east. If map zoom level goes out further to 1:558M. The error
 disappears, by some potential artifacts appear around the east and west
 edges of the map.

 I pulled the map requests from the log file to determine what was going
 on. I don't find any errors. Comparing the two files, I get differences on
 two lines. However these just look like differences in the bbox request. I
 am unable to recreate this error using the same raster data set in its
 native WGS84 projection or if I project it to 3857 and add it as a new data
 storage. However, this error does appear when I use the geoserver raster
 projection framework.


 Request #1 (Initial View, No error)
   AUTHORITY["EPSG","3857"]]
 Bbox = SRSEnvelope[-1.926155811957313E7 : 1.3966597672528865E7,
 -1.6109824066402005E7 : 4.401359194330725E7]
 RemoteOwsType = null
 RemoteOwsURL = null
 Env = {GSUSER=auser, LCWATER=1}
 FormatOptions = {}
 Angle = 0.0
 CQLFilter = null
 Elevation = []
 FeatureId = null
 StartIndex = null
 ViewParams = null
 Transparent = true
 StyleFormat = sld
 SldBody = null
 ValidateSchema = false
 Sld = null
 StyleUrl = null
 TilesOrigin = null
 Interpolations = []
 Filters = null
 Exceptions = SE_XML
 StyleBody = null
 SldVersion = null
 StyleVersion = null
 ScaleMethod = null
 Version = 1.1.1
 Request = GetMap
 Get = true
 RawKvp = {TRANSPARENT=true,
 BBOX=-19261558.11957313,-16109824.066402005,139

Re: [Geoserver-users] Raster projections

[Andrea Aime]

Hi David,
what do you mean by "I believe you should have all the files that you need.
The raster is loaded using the PostgreSQL JDBC connection."

Are you using the image mosaic JDBC module? Like, data stored in postgis
raster?

Cheers
Andrea


On Mon, Sep 28, 2015 at 5:30 PM, David Haynes II  wrote:

> I will send a google drive invitation to your personal e-mails. I am using
> geoserver 2.7
>
> On Mon, Sep 28, 2015 at 9:45 AM, Andrea Aime  > wrote:
>
>> Hi David,
>> we likely need data, style and request to reproduce locally, in order to
>> provide any help.
>> Also, which version of GeoServer are you using?
>>
>> Cheers
>> Andrea
>>
>>
>> On Mon, Sep 28, 2015 at 4:31 PM, David Haynes II 
>> wrote:
>>
>>> Hello Jody,
>>>
>>> Thanks for the reply. I seem to be encountering an issue related to
>>> raster projections and SLD visualization. I shall try to explain.
>>>
>>> The goal is to make an application that allows the user to visualize a
>>> raster dataset by turning pixel values on and off. Currently we are working
>>> with the raster dataset GLC2000, which is the landcover classification of
>>> the world for the year 2000. We have created an SLD for this dataset that
>>> converts the raster to transparent, setting each pixel value opacity to
>>> zero. Through the application users can turn on and off raster pixel values
>>> like water. We simply update the SLD with the env parameter
>>> 'env=lcwater:1'. Now all of the water is visible on the map.
>>>
>>>
>>> Here is a subset of the SLD we are currently using
>>> Title>Global Landcover Legend dynamic
>>>   .Text goes here.
>>>
>>>   
>>> 
>>>   
>>> 
>>>>> ="${env('lcprimveg',0)}" />
>>> >> ="${env('lcbrdevgrn',0)}"/>
>>> >> ="${env('lcdecidcl',0)}" />
>>> >> ="${env('lcdecidop',0)}" />
>>> >> ="${env('lcndlevgrn',0)}"/>
>>> >> ="${env('lcndldecid',0)}" />
>>> >> ="${env('lcmxlftree',0)}" />
>>> >> ="${env('lcaqtrfrsh',0)}" />
>>> >> ="${env('lcwater',0)}" />
>>>
>>>
>>> The problem we are having is that the raster style (SLD) is not working
>>> at all map extents. The raster layer has the native SRS set as 4326 and the
>>> declared SRS set to 3857. SRS handling is set to project native to
>>> declared. The interpolation is set to nearest neighbor and the default SLD
>>> is glc_dynamic.
>>>
>>> I preview the glc_dynamic raster layer through geoserver everything
>>> shows up fine, the screen is blank.I add the &env=lcwater:1 parameter and
>>> now I see water across the whole map. The only thing visible on the map is
>>> water. Preview scale is at 1:279M, rough bbox dimensions are -19144282.29W
>>> and 13927505.70963E. Now if I Pan west to -19535201.77042 the entire color
>>> legend is now visible on the map. This same error will occur if I pan to
>>> far east. If map zoom level goes out further to 1:558M. The error
>>> disappears, by some potential artifacts appear around the east and west
>>> edges of the map.
>>>
>>> I pulled the map requests from the log file to determine what was going
>>> on. I don't find any errors. Comparing the two files, I get differences on
>>> two lines. However these just look like differences in the bbox request. I
>>> am unable to recreate this error using the same raster data set in its
>>> native WGS84 projection or if I project it to 3857 and add it as a new data
>>> storage. However, this error does appear when I use the geoserver raster
>>> projection framework.
>>>
>>>
>>> Request #1 (Initial View, No error)
>>>   AUTHORITY["EPSG","3857"]]
>>> Bbox = SRSEnvelope[-1.926155811957313E7 : 1.3966597672528865E7,
>>> -1.6109824066402005E7 : 4.401359194330725E7]
>>> RemoteOwsType = null
>>> RemoteOwsURL = null
>>> Env = {GSUSER=auser, LCWATER=1}
>>> FormatOptions = {}
>>> Angle = 0.0
>>> CQLFilter = null
>>> Elevation = []
>>> FeatureId = null
>>> StartIndex = null
>>> ViewParams = null
>>> Transparent = true
>>> StyleFormat = sld
>>> SldBody = null
>>> ValidateSchema = false
>>> Sld = null
>>> StyleUrl = null
>>> TilesOrigin = null
>>> Interpolations = []
>>> Filters = null
>>> Exceptions = SE_XML
>>> StyleBody = null
>>> SldVersion = null
>>> StyleVersion = null
>>> ScaleMethod = null
>>> Version = 1.1.1
>>> Request = GetMap
>>> Get = true
>>> RawKvp = {TRANSPARENT=true,
>>> BBOX=-19261558.11957313,-16109824.066402005,13966597.672528865,44013591.94330725,
>>> VERSION=1.1.1, FORMAT=image/jpeg, SERVICE=WMS, HEIGHT=769, ENV=lcwater:1,
>>> REQUEST=GetMap, LAYERS=Shoumith:glc_dynamic, STYLES=Shoumith:glc_dynamic,
>>> SRS=EPSG:3857, WIDTH=425}
>>> BaseUrl = https://localhost:8080/geoserver/
>>> RequestCharset = UTF-8
>>>
>>> Request #2 (Pan West, with error)
>>>   AUTHORITY["EPSG","3857"]]
>>> Bbox = SRSEnvelope[-1.965247759948021E7 : 1.3575678192621782E7,
>>> -1.6109824066402005E7 : 4.401359194330725E7]
>>> RemoteOwsType = null
>>> RemoteOwsURL = null
>>> Env 

Re: [Geoserver-users] Raster projections

[David Haynes II]

I will send a google drive invitation to your personal e-mails. I am using
geoserver 2.7

On Mon, Sep 28, 2015 at 9:45 AM, Andrea Aime 
wrote:

> Hi David,
> we likely need data, style and request to reproduce locally, in order to
> provide any help.
> Also, which version of GeoServer are you using?
>
> Cheers
> Andrea
>
>
> On Mon, Sep 28, 2015 at 4:31 PM, David Haynes II  wrote:
>
>> Hello Jody,
>>
>> Thanks for the reply. I seem to be encountering an issue related to
>> raster projections and SLD visualization. I shall try to explain.
>>
>> The goal is to make an application that allows the user to visualize a
>> raster dataset by turning pixel values on and off. Currently we are working
>> with the raster dataset GLC2000, which is the landcover classification of
>> the world for the year 2000. We have created an SLD for this dataset that
>> converts the raster to transparent, setting each pixel value opacity to
>> zero. Through the application users can turn on and off raster pixel values
>> like water. We simply update the SLD with the env parameter
>> 'env=lcwater:1'. Now all of the water is visible on the map.
>>
>>
>> Here is a subset of the SLD we are currently using
>> Title>Global Landcover Legend dynamic
>>   .Text goes here.
>>
>>   
>> 
>>   
>> 
>>> ="${env('lcprimveg',0)}" />
>> > ="${env('lcbrdevgrn',0)}"/>
>> > ="${env('lcdecidcl',0)}" />
>> > ="${env('lcdecidop',0)}" />
>> > ="${env('lcndlevgrn',0)}"/>
>> > ="${env('lcndldecid',0)}" />
>> > ="${env('lcmxlftree',0)}" />
>> > ="${env('lcaqtrfrsh',0)}" />
>> > ="${env('lcwater',0)}" />
>>
>>
>> The problem we are having is that the raster style (SLD) is not working
>> at all map extents. The raster layer has the native SRS set as 4326 and the
>> declared SRS set to 3857. SRS handling is set to project native to
>> declared. The interpolation is set to nearest neighbor and the default SLD
>> is glc_dynamic.
>>
>> I preview the glc_dynamic raster layer through geoserver everything shows
>> up fine, the screen is blank.I add the &env=lcwater:1 parameter and now I
>> see water across the whole map. The only thing visible on the map is water.
>> Preview scale is at 1:279M, rough bbox dimensions are -19144282.29W and
>> 13927505.70963E. Now if I Pan west to -19535201.77042 the entire color
>> legend is now visible on the map. This same error will occur if I pan to
>> far east. If map zoom level goes out further to 1:558M. The error
>> disappears, by some potential artifacts appear around the east and west
>> edges of the map.
>>
>> I pulled the map requests from the log file to determine what was going
>> on. I don't find any errors. Comparing the two files, I get differences on
>> two lines. However these just look like differences in the bbox request. I
>> am unable to recreate this error using the same raster data set in its
>> native WGS84 projection or if I project it to 3857 and add it as a new data
>> storage. However, this error does appear when I use the geoserver raster
>> projection framework.
>>
>>
>> Request #1 (Initial View, No error)
>>   AUTHORITY["EPSG","3857"]]
>> Bbox = SRSEnvelope[-1.926155811957313E7 : 1.3966597672528865E7,
>> -1.6109824066402005E7 : 4.401359194330725E7]
>> RemoteOwsType = null
>> RemoteOwsURL = null
>> Env = {GSUSER=auser, LCWATER=1}
>> FormatOptions = {}
>> Angle = 0.0
>> CQLFilter = null
>> Elevation = []
>> FeatureId = null
>> StartIndex = null
>> ViewParams = null
>> Transparent = true
>> StyleFormat = sld
>> SldBody = null
>> ValidateSchema = false
>> Sld = null
>> StyleUrl = null
>> TilesOrigin = null
>> Interpolations = []
>> Filters = null
>> Exceptions = SE_XML
>> StyleBody = null
>> SldVersion = null
>> StyleVersion = null
>> ScaleMethod = null
>> Version = 1.1.1
>> Request = GetMap
>> Get = true
>> RawKvp = {TRANSPARENT=true,
>> BBOX=-19261558.11957313,-16109824.066402005,13966597.672528865,44013591.94330725,
>> VERSION=1.1.1, FORMAT=image/jpeg, SERVICE=WMS, HEIGHT=769, ENV=lcwater:1,
>> REQUEST=GetMap, LAYERS=Shoumith:glc_dynamic, STYLES=Shoumith:glc_dynamic,
>> SRS=EPSG:3857, WIDTH=425}
>> BaseUrl = https://localhost:8080/geoserver/
>> RequestCharset = UTF-8
>>
>> Request #2 (Pan West, with error)
>>   AUTHORITY["EPSG","3857"]]
>> Bbox = SRSEnvelope[-1.965247759948021E7 : 1.3575678192621782E7,
>> -1.6109824066402005E7 : 4.401359194330725E7]
>> RemoteOwsType = null
>> RemoteOwsURL = null
>> Env = {GSUSER=auser, LCWATER=1}
>> FormatOptions = {}
>> Angle = 0.0
>> CQLFilter = null
>> Elevation = []
>> FeatureId = null
>> StartIndex = null
>> ViewParams = null
>> Transparent = true
>> StyleFormat = sld
>> SldBody = null
>> ValidateSchema = false
>> Sld = null
>> StyleUrl = null
>> TilesOrigin = null
>> Interpolations = []
>> Filters = null
>> Exceptions = SE_XML
>> StyleBody = null
>> SldVersion = null
>> StyleVersion = null
>> Sca

Re: [Geoserver-users] Raster projections

[Andrea Aime]

Hi David,
we likely need data, style and request to reproduce locally, in order to
provide any help.
Also, which version of GeoServer are you using?

Cheers
Andrea


On Mon, Sep 28, 2015 at 4:31 PM, David Haynes II  wrote:

> Hello Jody,
>
> Thanks for the reply. I seem to be encountering an issue related to raster
> projections and SLD visualization. I shall try to explain.
>
> The goal is to make an application that allows the user to visualize a
> raster dataset by turning pixel values on and off. Currently we are working
> with the raster dataset GLC2000, which is the landcover classification of
> the world for the year 2000. We have created an SLD for this dataset that
> converts the raster to transparent, setting each pixel value opacity to
> zero. Through the application users can turn on and off raster pixel values
> like water. We simply update the SLD with the env parameter
> 'env=lcwater:1'. Now all of the water is visible on the map.
>
>
> Here is a subset of the SLD we are currently using
> Title>Global Landcover Legend dynamic
>   .Text goes here.
>
>   
> 
>   
> 
> ="${env('lcprimveg',0)}" />
>  ="${env('lcbrdevgrn',0)}"/>
>  ="${env('lcdecidcl',0)}" />
>  ="${env('lcdecidop',0)}" />
>  ="${env('lcndlevgrn',0)}"/>
>  ="${env('lcndldecid',0)}" />
>  ="${env('lcmxlftree',0)}" />
>  ="${env('lcaqtrfrsh',0)}" />
>  ="${env('lcwater',0)}" />
>
>
> The problem we are having is that the raster style (SLD) is not working at
> all map extents. The raster layer has the native SRS set as 4326 and the
> declared SRS set to 3857. SRS handling is set to project native to
> declared. The interpolation is set to nearest neighbor and the default SLD
> is glc_dynamic.
>
> I preview the glc_dynamic raster layer through geoserver everything shows
> up fine, the screen is blank.I add the &env=lcwater:1 parameter and now I
> see water across the whole map. The only thing visible on the map is water.
> Preview scale is at 1:279M, rough bbox dimensions are -19144282.29W and
> 13927505.70963E. Now if I Pan west to -19535201.77042 the entire color
> legend is now visible on the map. This same error will occur if I pan to
> far east. If map zoom level goes out further to 1:558M. The error
> disappears, by some potential artifacts appear around the east and west
> edges of the map.
>
> I pulled the map requests from the log file to determine what was going
> on. I don't find any errors. Comparing the two files, I get differences on
> two lines. However these just look like differences in the bbox request. I
> am unable to recreate this error using the same raster data set in its
> native WGS84 projection or if I project it to 3857 and add it as a new data
> storage. However, this error does appear when I use the geoserver raster
> projection framework.
>
>
> Request #1 (Initial View, No error)
>   AUTHORITY["EPSG","3857"]]
> Bbox = SRSEnvelope[-1.926155811957313E7 : 1.3966597672528865E7,
> -1.6109824066402005E7 : 4.401359194330725E7]
> RemoteOwsType = null
> RemoteOwsURL = null
> Env = {GSUSER=auser, LCWATER=1}
> FormatOptions = {}
> Angle = 0.0
> CQLFilter = null
> Elevation = []
> FeatureId = null
> StartIndex = null
> ViewParams = null
> Transparent = true
> StyleFormat = sld
> SldBody = null
> ValidateSchema = false
> Sld = null
> StyleUrl = null
> TilesOrigin = null
> Interpolations = []
> Filters = null
> Exceptions = SE_XML
> StyleBody = null
> SldVersion = null
> StyleVersion = null
> ScaleMethod = null
> Version = 1.1.1
> Request = GetMap
> Get = true
> RawKvp = {TRANSPARENT=true,
> BBOX=-19261558.11957313,-16109824.066402005,13966597.672528865,44013591.94330725,
> VERSION=1.1.1, FORMAT=image/jpeg, SERVICE=WMS, HEIGHT=769, ENV=lcwater:1,
> REQUEST=GetMap, LAYERS=Shoumith:glc_dynamic, STYLES=Shoumith:glc_dynamic,
> SRS=EPSG:3857, WIDTH=425}
> BaseUrl = https://localhost:8080/geoserver/
> RequestCharset = UTF-8
>
> Request #2 (Pan West, with error)
>   AUTHORITY["EPSG","3857"]]
> Bbox = SRSEnvelope[-1.965247759948021E7 : 1.3575678192621782E7,
> -1.6109824066402005E7 : 4.401359194330725E7]
> RemoteOwsType = null
> RemoteOwsURL = null
> Env = {GSUSER=auser, LCWATER=1}
> FormatOptions = {}
> Angle = 0.0
> CQLFilter = null
> Elevation = []
> FeatureId = null
> StartIndex = null
> ViewParams = null
> Transparent = true
> StyleFormat = sld
> SldBody = null
> ValidateSchema = false
> Sld = null
> StyleUrl = null
> TilesOrigin = null
> Interpolations = []
> Filters = null
> Exceptions = SE_XML
> StyleBody = null
> SldVersion = null
> StyleVersion = null
> ScaleMethod = null
> Version = 1.1.1
> Request = GetMap
> Get = true
> RawKvp = {TRANSPARENT=true,
> BBOX=-19652477.59948021,-16109824.066402005,13575678.192621782,44013591.94330725,
> VERSION=1.1.1, FORMAT=image/jpeg, SERVICE=WMS, HEIGHT=769, ENV=lcwater:1,
> REQUEST=GetMap, LAYERS=Shoumith:glc_dyn

Re: [Geoserver-users] Raster projections

[David Haynes II]

Hello Jody,

Thanks for the reply. I seem to be encountering an issue related to raster
projections and SLD visualization. I shall try to explain.

The goal is to make an application that allows the user to visualize a
raster dataset by turning pixel values on and off. Currently we are working
with the raster dataset GLC2000, which is the landcover classification of
the world for the year 2000. We have created an SLD for this dataset that
converts the raster to transparent, setting each pixel value opacity to
zero. Through the application users can turn on and off raster pixel values
like water. We simply update the SLD with the env parameter
'env=lcwater:1'. Now all of the water is visible on the map.


Here is a subset of the SLD we are currently using
Title>Global Landcover Legend dynamic
  .Text goes here.

  

  

   










The problem we are having is that the raster style (SLD) is not working at
all map extents. The raster layer has the native SRS set as 4326 and the
declared SRS set to 3857. SRS handling is set to project native to
declared. The interpolation is set to nearest neighbor and the default SLD
is glc_dynamic.

I preview the glc_dynamic raster layer through geoserver everything shows
up fine, the screen is blank.I add the &env=lcwater:1 parameter and now I
see water across the whole map. The only thing visible on the map is water.
Preview scale is at 1:279M, rough bbox dimensions are -19144282.29W and
13927505.70963E. Now if I Pan west to -19535201.77042 the entire color
legend is now visible on the map. This same error will occur if I pan to
far east. If map zoom level goes out further to 1:558M. The error
disappears, by some potential artifacts appear around the east and west
edges of the map.

I pulled the map requests from the log file to determine what was going on.
I don't find any errors. Comparing the two files, I get differences on two
lines. However these just look like differences in the bbox request. I am
unable to recreate this error using the same raster data set in its native
WGS84 projection or if I project it to 3857 and add it as a new data
storage. However, this error does appear when I use the geoserver raster
projection framework.


Request #1 (Initial View, No error)
  AUTHORITY["EPSG","3857"]]
Bbox = SRSEnvelope[-1.926155811957313E7 : 1.3966597672528865E7,
-1.6109824066402005E7 : 4.401359194330725E7]
RemoteOwsType = null
RemoteOwsURL = null
Env = {GSUSER=auser, LCWATER=1}
FormatOptions = {}
Angle = 0.0
CQLFilter = null
Elevation = []
FeatureId = null
StartIndex = null
ViewParams = null
Transparent = true
StyleFormat = sld
SldBody = null
ValidateSchema = false
Sld = null
StyleUrl = null
TilesOrigin = null
Interpolations = []
Filters = null
Exceptions = SE_XML
StyleBody = null
SldVersion = null
StyleVersion = null
ScaleMethod = null
Version = 1.1.1
Request = GetMap
Get = true
RawKvp = {TRANSPARENT=true,
BBOX=-19261558.11957313,-16109824.066402005,13966597.672528865,44013591.94330725,
VERSION=1.1.1, FORMAT=image/jpeg, SERVICE=WMS, HEIGHT=769, ENV=lcwater:1,
REQUEST=GetMap, LAYERS=Shoumith:glc_dynamic, STYLES=Shoumith:glc_dynamic,
SRS=EPSG:3857, WIDTH=425}
BaseUrl = https://localhost:8080/geoserver/
RequestCharset = UTF-8

Request #2 (Pan West, with error)
  AUTHORITY["EPSG","3857"]]
Bbox = SRSEnvelope[-1.965247759948021E7 : 1.3575678192621782E7,
-1.6109824066402005E7 : 4.401359194330725E7]
RemoteOwsType = null
RemoteOwsURL = null
Env = {GSUSER=auser, LCWATER=1}
FormatOptions = {}
Angle = 0.0
CQLFilter = null
Elevation = []
FeatureId = null
StartIndex = null
ViewParams = null
Transparent = true
StyleFormat = sld
SldBody = null
ValidateSchema = false
Sld = null
StyleUrl = null
TilesOrigin = null
Interpolations = []
Filters = null
Exceptions = SE_XML
StyleBody = null
SldVersion = null
StyleVersion = null
ScaleMethod = null
Version = 1.1.1
Request = GetMap
Get = true
RawKvp = {TRANSPARENT=true,
BBOX=-19652477.59948021,-16109824.066402005,13575678.192621782,44013591.94330725,
VERSION=1.1.1, FORMAT=image/jpeg, SERVICE=WMS, HEIGHT=769, ENV=lcwater:1,
REQUEST=GetMap, LAYERS=Shoumith:glc_dynamic, STYLES=Shoumith:glc_dynamic,
SRS=EPSG:3857, WIDTH=425}
BaseUrl = https://localhost:8080/geoserver/
RequestCharset = UTF-8



On Sun, Sep 27, 2015 at 4:20 PM, Jody Garnett 
wrote:

> I am not sure I understand you question Dr. Haynes - the blog post is a
> new feature (rather than an error). The feature has been included in recent
> GeoServer releases ..
>
> For example see 2.6.0 release aouncement
> 
>
> --
> Jody Garnett
>
> On 25 September 2015 at 13:07, David Haynes II  wrote:
>
>> Hello,
>>
>> I recently ran into this post and I am wondering if this error will be
>> fixed in updated versions of geoserver.
>> http://www.geo-solutions.it/blog/develope

[Geoserver-users] Oracle_Data_ref_set.sql

[Yin, Wentao (IS) (Contr)]

Hi,

Does anyone know where to find Oracle_Data_ref_set.sql  for gs-app-schema-test? 
It is no included in the source download.

Thanks,
Wen

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

Re: [Geoserver-users] Unable to create geofence h2 database under Linux

[Walter Stovall]

Thanks – it may be a few days before I can upgrade to 2.8 but I will indeed get 
to that soon.

I did find a workaround for my problem.  Seems like there’s definitely a bug in 
the handling of the property-override file.  I used procmon to verify that 
geofence is indeed reading from my property override file.  In that file I have 
this:
geofenceDataSource.url=jdbc:h2:c:/fdotwebsvc/h2db/geofence

That line is ineffective, as geofence still creates the file at its default 
location.  So I modified the file at 
geofence/WEB-INF/classes/geofence-datasource-ovr.properties.

There, I changed this line that creates the h2db in the tomcat directory:
geofenceDataSource.url=jdbc:h2:geofence_db/geofence

I set it the same as the ineffective setting in my property override file.  Now 
it works correctly.

From: Jody Garnett [mailto:jody.garn...@gmail.com]
Sent: Sunday, September 27, 2015 5:28 PM
To: Walter Stovall
Cc: geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] Unable to create geofence h2 database under Linux

I have not tried GeoFence on 2.7.x yet ... but a lot of work has been done a 
community module for 2.8 (including REST API and a new integrated GUI).

If you are in position to test please give it a go - feedback / testing / 
encouragement for the developers involved is always a good thing.



--
Jody Garnett

On 25 September 2015 at 05:24, Walter Stovall 
mailto:walter.stov...@byers.com>> wrote:
Using GeoServer 2.7.2 and the matching download of GeoFence.  On my local 
Windows computer geofence starts up and creates its h2 (default) database by 
default at the home directory of my tomcat instance.  That’s OK under Windows 
but not Linux.

I tried creating a property override file so I can change the location where 
the h2 database gets created but I’m having no luck getting it to happen there 
in spite of confirming in the tomcat log that my property file is being read.

In the JVM startup flags I have:
-Dgeofence-ovr=file:/C:\fdotwebsvc\GeoServerDataDir\geofence-byers-ovr.properties

During tomcat startup I observe this in the log:
12:17:12,047  INFO PropertyOverrideConfigurer:177 - Loading properties file from
URL [file:/C:/fdotwebsvc/GeoServerDataDir/geofence-byers-ovr.properties]

In the geofence-byers-ovr.properties file I have a single line with:
geofenceDataSource.url=jdbc:h2:C:\fdotwebsvc\h2db\geofence.h2.db

But when I start my local tomcat I see nothing get created in the above h2db 
directory and I see a lock-file added to the {tomcat-home}/geofence_db 
directory.

What can I do to change the location where the db gets created?

Thanks for any assistance!

Walter

--

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

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

Re: [Geoserver-users] Help : Geoserver publish shapefile -> Schema does not exist

[GILLARD Nicolas]

Hi,

Indeed, I use the absolute path.

I feared that the problem is jdbc config. Unfortunately I have to use it in my 
project.
However, I have found a less clean solution to resolve my problem. I will use 
it.

I will test the solution without the JDBC config in the future and give you my 
feedback.

Thank you to both of you for the time you have given me to answer my questions.

Nicolas
[cid:cirb1d8435]

Nicolas GILLARD
Analyst Programmer
Projects - IS
Avenue des Arts 21, 1000 Bruxelles - cirb.brussels - 
disclaimer
T +32 2 600 43 13 | G +32 479 57 92 04 | Helpdesk +32 2 801 00 00
Be green, leave it on the screen !  
 [cid:lna28115]    
[cid:tw8caadf]   [cid:ecodyn227d54] 



A noter ! L'adresse email de votre correspondant CIRB a changé pour devenir 
@cirb.brussels.

Opgelet! Het e-mailadres van uw CIBG-contact is veranderd en eindigt voortaan 
op @cibg.brussels.


De : Stefano Costa [stefano.co...@geo-solutions.it]
Envoyé : lundi 28 septembre 2015 13:00
À : GILLARD Nicolas
Cc : Andrea Aime; geoserver-users@lists.sourceforge.net
Objet : Re: [Geoserver-users] Help : Geoserver publish shapefile -> Schema does 
not exist

Hi Nicolas,
right, you're uploading an existing shapefile... I thought you were uploading 
it in the request body (I seem to have issues accessing GeoServer's online docs 
this morning and I couldn't open your link).

Your code looks correct (as far as I can understand): are you using the 
absolute path to the shapefile in your request?

If the answer is yes, I'd do what Andrea suggested and try without the 
JDBCConfig module.

On Mon, Sep 28, 2015 at 11:34 AM, GILLARD Nicolas 
mailto:ngillard@cirb.brussels>> wrote:
Hi Stefano,
Indeed, i'm uploading a shapefile.

But in geoserver documentation, this is the example based on shapefile :  
http://docs.geoserver.org/2.7.0/user/rest/examples/curl.html#adding-an-existing-shapefile

curl -v -u admin:geoserver -XPUT -H "Content-type: text/plain"
  -d "file:///data/shapefiles/rivers/rivers.shp"
  
http://localhost:8080/geoserver/rest/workspaces/acme/datastores/rivers/external.shp

I'd rather not have to zip the files

This is my curl call in python:

ITERATION :
url = 
geoserverDestination.service_url+"/workspaces/"+workspace.name+"/datastores/"+storeName+"/external.shp"
data = "file://"+shapefilesPath+".shp"#
curl = c = pycurl.Curl()
curl.setopt(pycurl.URL, url)
data = "%s" % data
curl.setopt(pycurl.CUSTOMREQUEST, "PUT")
curl.setopt(pycurl.POSTFIELDS, data)
curl.setopt(pycurl.HTTPHEADER, ["Content-type: text/plain; 
charset=UTF-8"])
curl.setopt(pycurl.VERBOSE, 0)
curl.setopt(pycurl.USERPWD, 
environment['userDestination']+':'+environment['passwordDestination'])#Geoserver
 credential
try:
curl.perform()
except pycurl.error, error:
errno, errstr = error
print 'An error occurred: ', errstr

Best regards,

Nicolas

--

Best regards,
Stefano Costa

==
GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V for more information.
==
Dott. Stefano Costa
Senior Software Engineer

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
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 no

Re: [Geoserver-users] Help : Geoserver publish shapefile -> Schema does not exist

[Stefano Costa]

Hi Nicolas,
right, you're uploading an existing shapefile... I thought you were
uploading it in the request body (I seem to have issues accessing
GeoServer's online docs this morning and I couldn't open your link).

Your code looks correct (as far as I can understand): are you using the
absolute path to the shapefile in your request?

If the answer is yes, I'd do what Andrea suggested and try without the
JDBCConfig module.

On Mon, Sep 28, 2015 at 11:34 AM, GILLARD Nicolas 
wrote:

> Hi Stefano,
> Indeed, i'm uploading a shapefile.
>
> But in geoserver documentation, this is the example based on shapefile :
> http://docs.geoserver.org/2.7.0/user/rest/examples/curl.html#adding-an-existing-shapefile
>
> curl -v -u admin:geoserver -XPUT -H "Content-type: *text/plain*"  -d 
> "file:///data/shapefiles/rivers/rivers.*shp*"  
> http://localhost:8080/geoserver/rest/workspaces/acme/datastores/rivers/external.shp
>
> I'd rather not have to zip the files
>
> This is my curl call in python:
>
> ITERATION :
> url = geoserverDestination.service_url+"/workspaces/"+
> workspace.name+"/datastores/"+storeName+"/external.shp"
> data = "file://"+shapefilesPath+".shp"#
> curl = c = pycurl.Curl()
> curl.setopt(pycurl.URL, url)
> data = "%s" % data
> curl.setopt(pycurl.CUSTOMREQUEST, "PUT")
> curl.setopt(pycurl.POSTFIELDS, data)
> curl.setopt(pycurl.HTTPHEADER, ["Content-type: text/plain;
> charset=UTF-8"])
> curl.setopt(pycurl.VERBOSE, 0)
> curl.setopt(pycurl.USERPWD,
> environment['userDestination']+':'+environment['passwordDestination'])#Geoserver
> credential
> try:
> curl.perform()
> except pycurl.error, error:
> errno, errstr = error
> print 'An error occurred: ', errstr
>
> Best regards,
>
> Nicolas
>
> --

Best regards,
Stefano Costa

==
GeoServer Professional Services from the experts!
Visithttp://goo.gl/it488V for more information.
==
Dott. Stefano Costa
Senior Software Engineer

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054  Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
http://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.
--
___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] Help : Geoserver publish shapefile -> Schema does not exist

[Andrea Aime]

Hi Nicolas,
I see you are using the JDBCConfig module, which is not officially
supported by the GeoServer community (it's a community module,
which means it has not yet reached the desired quality level and/or has no
one stepping up to be its maintainer).

Wondering if you could reproduce the same issue with a normal GeoServer
without JDBCConfig?
It would help a lot checking if the issue is in the core GeoServer, or in
JDBCConfig itself

Cheers
Andrea


On Mon, Sep 28, 2015 at 10:59 AM, GILLARD Nicolas 
wrote:

> Hi Andrea,
>
> *Log when I publish the first layer : *
> --
>
> 28 Sep 10:47:16 INFO [catalog.rest] - PUT file, mimetype: text/plain;
> charset=UTF-8
> 28 Sep 10:47:16 INFO [catalog.rest] - Auto-configuring datastore:
> ShpDirUrbis
> 28 Sep 10:47:20 INFO [catalog.rest] - Added feature type MuNeighbour
> 28 Sep 10:47:21 INFO [catalog.rest] - PUT layer MuNeighbour
> 28 Sep 10:47:21 INFO [org.geoserver] - Loaded feature type 'null', enabled
> 28 Sep 10:47:21 WARN [catalog.impl] - Failed to load actual store for
> FeatureTypeInfoImpl[null]
> 28 Sep 10:47:21 WARN [catalog.impl] - Failed to load actual store for
> FeatureTypeInfoImpl[null]
> 28 Sep 10:47:21 INFO [catalog.rest] - PUT
> FeatureTypeShpDirUrbis,MuNeighbour updated metadata only
> 28 Sep 10:47:21 ERROR [jdbcconfig.config] - Problem while reinitializing
> Logging from JDBC Config.  Log configuration may not be correct.
> java.lang.NullPointerException
> at sun.reflect.GeneratedMethodAccessor328.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.geoserver.jdbcconfig.config.JDBCGeoServerFacade.reinitializeLogging(JDBCGeoServerFacade.java:99)
> at
> org.geoserver.jdbcconfig.config.JDBCGeoServerFacade.setGeoServer(JDBCGeoServerFacade.java:132)
> at
> org.geoserver.config.impl.GeoServerImpl.setFacade(GeoServerImpl.java:71)
> at
> org.geoserver.jdbcconfig.JDBCGeoServerLoader.loadGeoServer(JDBCGeoServerLoader.java:102)
> at
> org.geoserver.config.GeoServerLoader.reload(GeoServerLoader.java:208)
> at
> org.geoserver.jdbcconfig.JDBCGeoServerLoader.reload(JDBCGeoServerLoader.java:143)
> at
> org.geoserver.config.GeoServerLoaderProxy.reload(GeoServerLoaderProxy.java:66)
> at
> org.geoserver.config.impl.GeoServerImpl.reload(GeoServerImpl.java:452)
> at
> org.geoserver.catalog.rest.CatalogReloader.reloadCatalog(CatalogReloader.java:76)
> at
> org.geoserver.catalog.rest.CatalogReloader$1.handlePost(CatalogReloader.java:56)
> at org.restlet.Finder.handle(Finder.java:296)
> at
> org.geoserver.rest.BeanDelegatingRestlet.handle(BeanDelegatingRestlet.java:38)
> at org.restlet.Filter.doHandle(Filter.java:105)
> at org.restlet.Filter.handle(Filter.java:134)
> at org.restlet.Router.handle(Router.java:444)
>
> ...
>
> 28 Sep 10:47:21 INFO [gwc.layer] - GeoServer TileLayer store base
> directory is: /srv/data/geoserver/gwc-layers
> 28 Sep 10:47:21 INFO [gwc.layer] - Loading tile layers from
> /srv/data/geoserver/gwc-layers
> 28 Sep 10:47:21 INFO [gwc.layer] - Initializing GWC configuration based on
> GeoServer's Catalog
> 28 Sep 10:47:21 INFO [gwc.layer] - GeoServer TileLayer store base
> directory is: /srv/data/geoserver/gwc-layers
> 28 Sep 10:47:21 INFO [gwc.layer] - Loading tile layers from
> /srv/data/geoserver/gwc-layers
> 28 Sep 10:47:21 INFO [gwc.layer] - GWC configuration based on GeoServer's
> Catalog loaded successfuly
> 28 Sep 10:47:23 INFO [gwc.layer] - Truncating default style for layer
> Urbis:MuNeighbour, as it changed from polygon to
> UrbisMuNeighbourZoomAttrLblNAMEFRPolygon0.4
> 28 Sep 10:47:23 INFO [geoserver.gwc] - Saving GeoSeverTileLayer
> Urbis:MuNeighbour
> 28 Sep 10:47:23 INFO [catalog.rest] - PUT layer MuNeighbour
>
>
> *The second one : *
> 
>
> 28 Sep 10:47:24 INFO [catalog.rest] - PUT style UrbisHighwaysZoomLineSized
> 28 Sep 10:47:26 INFO [catalog.rest] - PUT file, mimetype: text/plain;
> charset=UTF-8
> 28 Sep 10:47:26 INFO [catalog.rest] - Using existing datastore: ShpDirUrbis
> 28 Sep 10:47:30 INFO [catalog.rest] - Added feature type Highways
> 28 Sep 10:47:31 INFO [catalog.rest] - PUT layer Highways
> 28 Sep 10:47:31 INFO [org.geoserver] - Loaded feature type 'null', enabled
> 28 Sep 10:47:31 WARN [catalog.impl] - Failed to load actual store for
> FeatureTypeInfoImpl[null]
> 28 Sep 10:47:31 WARN [catalog.impl] - Failed to load actual store for
> FeatureTypeInfoImpl[null]
> 28 Sep 10:

Re: [Geoserver-users] Geofence integrated server extension

[Patrick Valsecchi]

Andrea,

OK, issue created:
https://osgeo-org.atlassian.net/browse/GEOS-7219

Thanks.

On Mon, Sep 28, 2015 at 11:17 AM, Andrea Aime 
wrote:

> On Mon, Sep 28, 2015 at 10:34 AM, Patrick Valsecchi <
> patrick.valsec...@camptocamp.com> wrote:
>
>> Hi,
>>
>> I'm trying to follow those instructions:
>>
>> http://ares.opengeo.org/geoserver/master/doc/en/user/community/geofence-server/installing.html
>>
>> Sadly, when doing so, the webapp is missing classes. For example:
>> Caused by: java.lang.ClassNotFoundException:
>> com.googlecode.genericdao.search.MetadataUtil
>>at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
>>at
>> org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:366)
>>
>> I tried to install both current master (2015-09-26) and 2.8.x
>> (2015-09.27) of geoserver and the matching version of
>> geofence-server-plugin, but they both have this same problem.
>>
>> Then, I went to manually add the missing JARs that I copied from the
>> separate geofence WAR file (dao-1.1.0.jar, search-1.1.0.jar,
>> spring-orm-3.1.1.RELEASE.jar, dom4j-1.6.1.jar, javassist-3.8.0.GA.jar) and
>> I hit a wall. Log4j used by geoserver is version 1.2 and I start needing
>> classes provided by log4j version 2.
>>
>> Is anybody had success installing this plugin? What I am doing wrong?
>>
>
> The plugin does not have a complete packaging descriptor, so the zip file
> does not contain
> all the jars it should.
> I guess Niels (cc'ed) set the file up (
> https://github.com/geoserver/geoserver/commits/master/src/community/release/ext-geofence-server.xml
> ),
> but did not actually try the results ;-)
>
> You should probably add a bug report for this at
> https://osgeo-org.atlassian.net/projects/GEOS/summary
>
> 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 Poggio alle Viti 1187
> 55054  Massarosa (LU)
> Italy
> 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.
>
> ---
>
--
___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] Help : Geoserver publish shapefile -> Schema does not exist

[GILLARD Nicolas]

Hi Stefano,
Indeed, i'm uploading a shapefile.

But in geoserver documentation, this is the example based on shapefile :  
http://docs.geoserver.org/2.7.0/user/rest/examples/curl.html#adding-an-existing-shapefile

curl -v -u admin:geoserver -XPUT -H "Content-type: text/plain"
  -d "file:///data/shapefiles/rivers/rivers.shp"
  
http://localhost:8080/geoserver/rest/workspaces/acme/datastores/rivers/external.shp

I'd rather not have to zip the files

This is my curl call in python:

ITERATION :
url = 
geoserverDestination.service_url+"/workspaces/"+workspace.name+"/datastores/"+storeName+"/external.shp"
data = "file://"+shapefilesPath+".shp"#
curl = c = pycurl.Curl()
curl.setopt(pycurl.URL, url)
data = "%s" % data
curl.setopt(pycurl.CUSTOMREQUEST, "PUT")
curl.setopt(pycurl.POSTFIELDS, data)
curl.setopt(pycurl.HTTPHEADER, ["Content-type: text/plain; 
charset=UTF-8"])
curl.setopt(pycurl.VERBOSE, 0)
curl.setopt(pycurl.USERPWD, 
environment['userDestination']+':'+environment['passwordDestination'])#Geoserver
 credential
try:
curl.perform()
except pycurl.error, error:
errno, errstr = error
print 'An error occurred: ', errstr

Best regards,

Nicolas
[cid:cirb6bc2dd]

Nicolas GILLARD
Analyst Programmer
Projects - IS
Avenue des Arts 21, 1000 Bruxelles - cirb.brussels - 
disclaimer
T +32 2 600 43 13 | G +32 479 57 92 04 | Helpdesk +32 2 801 00 00
Be green, leave it on the screen !  
 [cid:ln69bb63]    
[cid:tw2c77fc]   [cid:ecodyne58613] 



A noter ! L'adresse email de votre correspondant CIRB a changé pour devenir 
@cirb.brussels.

Opgelet! Het e-mailadres van uw CIBG-contact is veranderd en eindigt voortaan 
op @cibg.brussels.


De : Stefano Costa [stefano.co...@geo-solutions.it]
Envoyé : lundi 28 septembre 2015 11:24
À : GILLARD Nicolas
Cc : Andrea Aime; geoserver-users@lists.sourceforge.net
Objet : Re: [Geoserver-users] Help : Geoserver publish shapefile -> Schema does 
not exist

Hi Nicolas,

On Mon, Sep 28, 2015 at 10:59 AM, GILLARD Nicolas 
mailto:ngillard@cirb.brussels>> wrote:
28 Sep 10:47:16 INFO [catalog.rest] - PUT file, mimetype: text/plain; 
charset=UTF-8

Hum... you're uploading a shapefile, right? So this content-type doesn't look 
good: you should zip the .shp, .shx, .dbf and .prj files and upload the zip 
archive setting the header "Content-Type: application/zip"

Could you post also the cURL command you're running?

--

Best regards,
Stefano Costa

==
GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V for more information.
==
Dott. Stefano Costa
Senior Software Engineer

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
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.


---

Re: [Geoserver-users] Help : Geoserver publish shapefile -> Schema does not exist

[Stefano Costa]

Hi Nicolas,

On Mon, Sep 28, 2015 at 10:59 AM, GILLARD Nicolas 
wrote:

> 28 Sep 10:47:16 INFO [catalog.rest] - PUT file, mimetype: text/plain;
> charset=UTF-8
>

Hum... you're uploading a shapefile, right? So this content-type doesn't
look good: you should zip the .shp, .shx, .dbf and .prj files and upload
the zip archive setting the header "Content-Type: application/zip"

Could you post also the cURL command you're running?

-- 

Best regards,
Stefano Costa

==
GeoServer Professional Services from the experts!
Visithttp://goo.gl/it488V for more information.
==
Dott. Stefano Costa
Senior Software Engineer

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054  Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
http://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.
--
___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] Geofence integrated server extension

[Andrea Aime]

On Mon, Sep 28, 2015 at 10:34 AM, Patrick Valsecchi <
patrick.valsec...@camptocamp.com> wrote:

> Hi,
>
> I'm trying to follow those instructions:
>
> http://ares.opengeo.org/geoserver/master/doc/en/user/community/geofence-server/installing.html
>
> Sadly, when doing so, the webapp is missing classes. For example:
> Caused by: java.lang.ClassNotFoundException:
> com.googlecode.genericdao.search.MetadataUtil
>at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
>at
> org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:366)
>
> I tried to install both current master (2015-09-26) and 2.8.x (2015-09.27)
> of geoserver and the matching version of geofence-server-plugin, but they
> both have this same problem.
>
> Then, I went to manually add the missing JARs that I copied from the
> separate geofence WAR file (dao-1.1.0.jar, search-1.1.0.jar,
> spring-orm-3.1.1.RELEASE.jar, dom4j-1.6.1.jar, javassist-3.8.0.GA.jar) and
> I hit a wall. Log4j used by geoserver is version 1.2 and I start needing
> classes provided by log4j version 2.
>
> Is anybody had success installing this plugin? What I am doing wrong?
>

The plugin does not have a complete packaging descriptor, so the zip file
does not contain
all the jars it should.
I guess Niels (cc'ed) set the file up (
https://github.com/geoserver/geoserver/commits/master/src/community/release/ext-geofence-server.xml
),
but did not actually try the results ;-)

You should probably add a bug report for this at
https://osgeo-org.atlassian.net/projects/GEOS/summary

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 Poggio alle Viti 1187
55054  Massarosa (LU)
Italy
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.

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

[Geoserver-users] Geofence integrated server extension

[Patrick Valsecchi]

Hi,

I'm trying to follow those instructions:
http://ares.opengeo.org/geoserver/master/doc/en/user/community/geofence-server/installing.html

Sadly, when doing so, the webapp is missing classes. For example:
Caused by: java.lang.ClassNotFoundException:
com.googlecode.genericdao.search.MetadataUtil
   at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
   at
org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:366)

I tried to install both current master (2015-09-26) and 2.8.x (2015-09.27)
of geoserver and the matching version of geofence-server-plugin, but they
both have this same problem.

Then, I went to manually add the missing JARs that I copied from the
separate geofence WAR file (dao-1.1.0.jar, search-1.1.0.jar,
spring-orm-3.1.1.RELEASE.jar, dom4j-1.6.1.jar, javassist-3.8.0.GA.jar) and
I hit a wall. Log4j used by geoserver is version 1.2 and I start needing
classes provided by log4j version 2.

Is anybody had success installing this plugin? What I am doing wrong?

Thanks for your help.
--
___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] Help : Geoserver publish shapefile -> Schema does not exist

[GILLARD Nicolas]

Hi Andrea,

Log when I publish the first layer : 
--

28 Sep 10:47:16 INFO [catalog.rest] - PUT file, mimetype: text/plain; 
charset=UTF-8
28 Sep 10:47:16 INFO [catalog.rest] - Auto-configuring datastore: ShpDirUrbis
28 Sep 10:47:20 INFO [catalog.rest] - Added feature type MuNeighbour
28 Sep 10:47:21 INFO [catalog.rest] - PUT layer MuNeighbour
28 Sep 10:47:21 INFO [org.geoserver] - Loaded feature type 'null', enabled
28 Sep 10:47:21 WARN [catalog.impl] - Failed to load actual store for 
FeatureTypeInfoImpl[null]
28 Sep 10:47:21 WARN [catalog.impl] - Failed to load actual store for 
FeatureTypeInfoImpl[null]
28 Sep 10:47:21 INFO [catalog.rest] - PUT FeatureTypeShpDirUrbis,MuNeighbour 
updated metadata only
28 Sep 10:47:21 ERROR [jdbcconfig.config] - Problem while reinitializing 
Logging from JDBC Config.  Log configuration may not be correct.
java.lang.NullPointerException
at sun.reflect.GeneratedMethodAccessor328.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.geoserver.jdbcconfig.config.JDBCGeoServerFacade.reinitializeLogging(JDBCGeoServerFacade.java:99)
at 
org.geoserver.jdbcconfig.config.JDBCGeoServerFacade.setGeoServer(JDBCGeoServerFacade.java:132)
at 
org.geoserver.config.impl.GeoServerImpl.setFacade(GeoServerImpl.java:71)
at 
org.geoserver.jdbcconfig.JDBCGeoServerLoader.loadGeoServer(JDBCGeoServerLoader.java:102)
at org.geoserver.config.GeoServerLoader.reload(GeoServerLoader.java:208)
at 
org.geoserver.jdbcconfig.JDBCGeoServerLoader.reload(JDBCGeoServerLoader.java:143)
at 
org.geoserver.config.GeoServerLoaderProxy.reload(GeoServerLoaderProxy.java:66)
at 
org.geoserver.config.impl.GeoServerImpl.reload(GeoServerImpl.java:452)
at 
org.geoserver.catalog.rest.CatalogReloader.reloadCatalog(CatalogReloader.java:76)
at 
org.geoserver.catalog.rest.CatalogReloader$1.handlePost(CatalogReloader.java:56)
at org.restlet.Finder.handle(Finder.java:296)
at 
org.geoserver.rest.BeanDelegatingRestlet.handle(BeanDelegatingRestlet.java:38)
at org.restlet.Filter.doHandle(Filter.java:105)
at org.restlet.Filter.handle(Filter.java:134)
at org.restlet.Router.handle(Router.java:444)

...

28 Sep 10:47:21 INFO [gwc.layer] - GeoServer TileLayer store base directory is: 
/srv/data/geoserver/gwc-layers
28 Sep 10:47:21 INFO [gwc.layer] - Loading tile layers from 
/srv/data/geoserver/gwc-layers
28 Sep 10:47:21 INFO [gwc.layer] - Initializing GWC configuration based on 
GeoServer's Catalog
28 Sep 10:47:21 INFO [gwc.layer] - GeoServer TileLayer store base directory is: 
/srv/data/geoserver/gwc-layers
28 Sep 10:47:21 INFO [gwc.layer] - Loading tile layers from 
/srv/data/geoserver/gwc-layers
28 Sep 10:47:21 INFO [gwc.layer] - GWC configuration based on GeoServer's 
Catalog loaded successfuly
28 Sep 10:47:23 INFO [gwc.layer] - Truncating default style for layer 
Urbis:MuNeighbour, as it changed from polygon to 
UrbisMuNeighbourZoomAttrLblNAMEFRPolygon0.4
28 Sep 10:47:23 INFO [geoserver.gwc] - Saving GeoSeverTileLayer 
Urbis:MuNeighbour
28 Sep 10:47:23 INFO [catalog.rest] - PUT layer MuNeighbour


The second one : 


28 Sep 10:47:24 INFO [catalog.rest] - PUT style UrbisHighwaysZoomLineSized
28 Sep 10:47:26 INFO [catalog.rest] - PUT file, mimetype: text/plain; 
charset=UTF-8
28 Sep 10:47:26 INFO [catalog.rest] - Using existing datastore: ShpDirUrbis
28 Sep 10:47:30 INFO [catalog.rest] - Added feature type Highways
28 Sep 10:47:31 INFO [catalog.rest] - PUT layer Highways
28 Sep 10:47:31 INFO [org.geoserver] - Loaded feature type 'null', enabled
28 Sep 10:47:31 WARN [catalog.impl] - Failed to load actual store for 
FeatureTypeInfoImpl[null]
28 Sep 10:47:31 WARN [catalog.impl] - Failed to load actual store for 
FeatureTypeInfoImpl[null]
28 Sep 10:47:31 INFO [catalog.rest] - PUT FeatureTypeShpDirUrbis,Highways 
updated metadata only
28 Sep 10:47:31 ERROR [jdbcconfig.config] - Problem while reinitializing 
Logging from JDBC Config.  Log configuration may not be correct.
java.lang.NullPointerException
at sun.reflect.GeneratedMethodAccessor328.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.geoserver.jdbcconfig.config.JDBCGeoServerFacade.reinitializeLogging(JDBCGeoServerFacade.java:99)
at 
org.geoserver.jdbcconfig.config.JDBCGeoServerFacade

Re: [Geoserver-users] Help : Geoserver publish shapefile -> Schema does not exist

[Andrea Aime]

On Mon, Sep 28, 2015 at 10:22 AM, GILLARD Nicolas 
wrote:

> 
>   java.lang.RuntimeException: Error getting FeatureType, this should
> never happen!
> Error getting FeatureType, this should never happen!
> Schema 'MuNeighbour' does not exist.
> 
>
> In geoserver logs :
>
>  Error while getting feature type, flushing cache and retrying: Schema
> 'MuNeighbour' does not exist.
> 28 Sep 09:46:36 WARN [geoserver.catalog] - Unable to flush '
> http://www.cirb.brussels/urbis:MuNeighbour
> java.io.IOException: Schema 'MuNeighbour' does not exist.
> java.lang.RuntimeException: Error getting FeatureType, this should never
> happen!
>

Do you have a full stack trace? I don't have enough information to help
with the above

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 Poggio alle Viti 1187
55054  Massarosa (LU)
Italy
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.

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

[Geoserver-users] Help : Geoserver publish shapefile -> Schema does not exist

[GILLARD Nicolas]

Hello everyone,

I have the following problem in geoserver 2.7.1.

I'm posting two shapefiles already located in geoserver.
I use curl to performed the publish operation. I followed it to the 
documentation:

http://docs.geoserver.org/2.7.0/user/rest/examples/curl.html#adding-an-existing-shapefile

The problem is:

The first shapefiles passes properly, a store +  layer is created.
The second shapefiles looks correct (the layer is created), but when I wish 
previsualize, I catch the following error message:


  java.lang.RuntimeException: Error getting FeatureType, this should never 
happen!
Error getting FeatureType, this should never happen!
Schema 'MuNeighbour' does not exist.


In geoserver logs :

 Error while getting feature type, flushing cache and retrying: Schema 
'MuNeighbour' does not exist.
28 Sep 09:46:36 WARN [geoserver.catalog] - Unable to flush 
'http://www.cirb.brussels/urbis:MuNeighbour
java.io.IOException: Schema 'MuNeighbour' does not exist.
java.lang.RuntimeException: Error getting FeatureType, this should never happen!



I don't understant what's happening.


Does someone already had the same problem?
Is there a fix?

I thank you in advance

Nicolas

[cid:cirbf7bd3c]

Nicolas GILLARD
Analyst Programmer
Projects - IS
Avenue des Arts 21, 1000 Bruxelles - cirb.brussels - 
disclaimer
T +32 2 600 43 13 | G +32 479 57 92 04 | Helpdesk +32 2 801 00 00
Be green, leave it on the screen !  
 [cid:ln6b174c]    
[cid:tw04702a]   [cid:ecodyna2ca1e] 



A noter ! L'adresse email de votre correspondant CIRB a changé pour devenir 
@cirb.brussels.

Opgelet! Het e-mailadres van uw CIBG-contact is veranderd en eindigt voortaan 
op @cibg.brussels.

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