[Geoserver-devel] [JIRA] (GEOS-8164) java.util.HashMap cannot be cast to org.eclipse.emf.ecore.EObject when sending WCS XML GetCoverage request

2017-05-30 Thread Torben Barsballe (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Torben Barsballe created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 GeoServer /  GEOS-8164  
 
 
  java.util.HashMap cannot be cast to org.eclipse.emf.ecore.EObject when sending WCS XML GetCoverage request   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 WCS  
 
 
Created: 
 31/May/17 1:04 AM  
 
 
Priority: 
  Medium  
 
 
Reporter: 
 Torben Barsballe  
 

  
 
 
 
 

 
 Given an arbitrary coverage, run: noformat curl -v -u admin:geoserver -XPOST -H "Content-type: text/xml" -d @getcov2.xml "localhost:8080/geoserver/wcs" noformat See getcov2.xml, attached, and change the "topp__world" to your exact coverage id. NOTE: REQUEST COULD BE WRONG, got from http://mapserver.org/ogc/wcs_server.html#wcs-2-0 GeoServer returns the following error message: 

 

  
java.lang.ClassCastException: java.util.HashMap cannot be cast to org.eclipse.emf.ecore.EObject
java.util.HashMap cannot be cast to org.eclipse.emf.ecore.EObject
[]
  

 

 The full stacktrace from the logs is: 

 
java.lang.ClassCastException: java.util.HashMap cannot be cast to org.eclipse.emf.ecore.EObject
	at net.opengis.wcs20.impl.ExtensionItemTypeImpl.getObjectContent(ExtensionItemTypeImpl.java:194)
	at net.opengis.wcs20.impl.ExtensionItemTypeImpl.eGet(ExtensionItemTypeImpl.java:241)
	at org.eclipse.emf.ecore.impl.BasicEObjectImpl.eGet(BasicEObjectImpl.java:1021)
	at org.eclipse.emf.ecore.impl.BasicEObjectImpl.eGet(BasicEObjectImpl.java:1013)
	at org.eclipse.emf.ecore.impl.BasicEObjectImpl.eGet(BasicEObjectImpl.java:1008)
	at org.geoserver.ows.util.EMFLogger.log(EMFLogger.java:37)
	at

Re: [Geoserver-devel] [Geotools-devel] upgrade postgresql JDBC driver to 42.1.1 (full binary xfer)

2017-05-30 Thread Ben Caradoc-Davies 
Thanks, Dave. That is a good point. I think 8.2 came out in 2006 or so. 
Last release for 8.1 was in 2010.


Developers, are we happy to drop support for PostgreSQL below 8.2?

Kind regards,
Ben.

On 31/05/17 05:43, Dave Blasby wrote:

Hi, Ben,

Thanks for putting the PR together and making sure everything was tested
(esp online tests).

WRT postgresql version support, I found this in the release notes for
42.0.0;


   - Support for PostgreSQL versions below 8.2 was dropped


Thanks,
Dave

On Mon, May 29, 2017 at 8:31 PM, Ben Caradoc-Davies 
wrote:


Dave,

with this upgrade, a full GeoTools build with online jdbc-postgis tests,
GeoServer build, community module compilation, and app-schema online tests
against postgis all pass. I also confirmed that the correct jar is included
in the assembled war and zip files.

Jira issue: https://osgeo-org.atlassian.net/browse/GEOT-5741
Pull request for master: https://github.com/geotools/geotools/pull/1605

Tested on debian unstable amd64:
postgresql-9.6 9.6.3-3 amd64
postgresql-9.6-postgis-2.3 2.3.1+dfsg-2 amd64

It would be good if someone could test this upgrade against an older
postgresql (especially 8).

$ mvn -version
Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426;
2017-04-04T07:39:06+12:00)
Maven home: /home/ben/java/maven
Java version: 1.8.0_131, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-8-openjdk-amd64/jre
Default locale: en_GB, platform encoding: UTF-8
OS name: "linux", version: "4.9.0-3-amd64", arch: "amd64", family: "unix"

Kind regards,
Ben.


On 30/05/17 09:22, Dave Blasby wrote:


Hi,

For GeoGig, we noticed that the latest Postgresql JDBC driver (42.1.1) now
allows full-binary data transfer.  This is better than 25% less bandwidth
than Base64 encoding!

I'd like to update the pom.xml  from 9.4.1211 to 42.1.1.

NOTE: PostGIS could be upgraded to use this as its a big win for a remote
(networked) database.
Note: you must use a prepared statement!


https://jdbc.postgresql.org/download.html

From the pom.xml;



9.4.1211

Comments?

Thanks,
Dave




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



___
GeoTools-Devel mailing list
geotools-de...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel



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





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

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

[Geoserver-devel] [JIRA] (GEOS-8163) Duplicate GeoPackage formats in layer preview page

2017-05-30 Thread Torben Barsballe (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Torben Barsballe created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 GeoServer /  GEOS-8163  
 
 
  Duplicate GeoPackage formats in layer preview page   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 geopackage  
 
 
Created: 
 30/May/17 11:57 PM  
 
 
Priority: 
  Low  
 
 
Reporter: 
 Torben Barsballe  
 

  
 
 
 
 

 
 With the GeoPackage extension installed, there are four slightly different GeoPackage formats listed under the WFS formats section of the Layer Preview Page "Choose format" dropdown. All four use the same output format and have the same effect. See attached screenshot for an example.  
 

  
 
 
  
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
 

[Geoserver-devel] [JIRA] (GEOS-8162) CSV Data store does not support relative store paths

2017-05-30 Thread Torben Barsballe (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Torben Barsballe created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 GeoServer /  GEOS-8162  
 
 
  CSV Data store does not support relative store paths   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 30/May/17 10:28 PM  
 
 
Priority: 
  Medium  
 
 
Reporter: 
 Torben Barsballe  
 

  
 
 
 
 

 
 When trying to publish a layer from a csv store, I get the following error: 

 
java.lang.RuntimeException: Error occurred while building the resources for the configuration page
 at org.geoserver.web.data.layer.NewLayerPage.buildLayerInfo(NewLayerPage.java:356)
 at org.geoserver.web.data.layer.NewLayerPage$8.onClick(NewLayerPage.java:281)
 at org.geoserver.web.wicket.SimpleAjaxLink$1.onClick(SimpleAjaxLink.java:46)
 at org.apache.wicket.ajax.markup.html.AjaxLink$1.onEvent(AjaxLink.java:68)
 at org.apache.wicket.ajax.AjaxEventBehavior.respond(AjaxEventBehavior.java:177)
 at org.apache.wicket.ajax.AbstractDefaultAjaxBehavior.onRequest(AbstractDefaultAjaxBehavior.java:300)
 at org.apache.wicket.request.target.component.listener.BehaviorRequestTarget.processEvents(BehaviorRequestTarget.java:119)
 at org.apache.wicket.request.AbstractRequestCycleProcessor.processEvents(AbstractRequestCycleProcessor.java:92)
 at org.apache.wicket.RequestCycle.processEventsAndRespond(RequestCycle.java:1250)
 at org.apache.wicket.RequestCycle.step(RequestCycle.java:1329)
 at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1436)
 at org.apache.wicket.RequestCycle.request(RequestCycle.java:545)
 at org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:484)
 at org.apache.wicket.protocol.http.WicketServlet.doGet(WicketServlet.java:138)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:620)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
 at org.springframework.web.servlet.mvc.ServletWrappingController.handleRequestInternal(ServletWrappingController.java:156)
 at org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:153)
 at

[Geoserver-devel] [JIRA] (GEOS-8161) GeoServer Importer does not support Geometries in CSV Stores

2017-05-30 Thread Torben Barsballe (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Torben Barsballe created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 GeoServer /  GEOS-8161  
 
 
  GeoServer Importer does not support Geometries in CSV Stores   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 Importer  
 
 
Created: 
 30/May/17 10:25 PM  
 
 
Priority: 
  Lowest  
 
 
Reporter: 
 Torben Barsballe  
 

  
 
 
 
 

 
 The GeoServer importer is currently only able to import CSV's as lists of attributes only (no Geometry).  Given that Geometry support does exist in the CSV DataStore, importer should probably support it.  
 

  
 
 
  
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message

[Geoserver-devel] [JIRA] (GEOS-8160) Importer - strange default postgis database name on windows

2017-05-30 Thread Torben Barsballe (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Torben Barsballe created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 GeoServer /  GEOS-8160  
 
 
  Importer - strange default postgis database name on windows   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 Importer  
 
 
Created: 
 30/May/17 10:21 PM  
 
 
Priority: 
  Lowest  
 
 
Reporter: 
 Torben Barsballe  
 

  
 
 
 
 

 
 When adding data from a PostGIS store using the Importer, the default database/username is usually populated from current user. Using a Windows 7 VM, it is instead filled with OG7VM2011$. This does not seem especially user-friendly. (Note: this appears to be the computer name, followed by a $)  
 

  
 
 
  
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
 

Re: [Geoserver-devel] upgrade postgresql JDBC driver to 42.1.1 (full binary xfer)

2017-05-30 Thread Dave Blasby 
Hi, Andrea,

if you aren't using prepared statements, it doesn't know that the data is
binary and it will "kick back" to the standard encoding (with a lot of
"\001"-like in the text).  It will work, but you are at approximately 300%
overhead.

As mentioned, above, I believe it works for PostgreSQL 8.2+ (December 2006).

I did take a look at TWKB, but for GeoGig purposes, the loss of precision
is a problem.  However, I am planning to look into it - it makes huge space
savings when you are looking at already-reduced-precision geometries.

I was also going to look at TWKB-like lossless encoding
(ie. Double#doubleToLongBits() and then using a TWKB-like int-diff
encoding).  However, it's likely better to just LZ4 the WKB.  When I do the
testing, I'll let you know what happens.

Either way, encoding TWKB as real "binary" (wrt Base64) will be another big
win.

Thanks,
Dave

On Tue, May 30, 2017 at 10:43 AM, Andrea Aime 
wrote:

> On Tue, May 30, 2017 at 7:01 PM, Dave Blasby 
> wrote:
>
>> Hi, Andrea,
>>
>> Only updating the driver version.
>>
>> I can work with the PostGIS maintainer to get it in - it's fairly easy
>> (just need to ensure that you are using prepared statements).
>>
>
> Maintainer eh? It used to be me and Justin.
> When you say "ensure that you are using prepared statements" is that only
> to get the actual binary transfer, or it would just
> break?
> And does that require some specific version of postgresql?
>
> The 25% less transfer is interesting, wondering if you have been looking
> at TWKB, that should provide greater savings (with
> some potential loss of precision).
>
> Cheers
> Andrea
>
> --
> ==
> GeoServer Professional Services from the experts! Visit
> http://goo.gl/it488V for more information.
> ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions S.A.S.
> Via di Montramito 3/A
> 55054  Massarosa (LU)
> phone: +39 0584 962313 <+39%200584%20962313>
> fax: +39 0584 1660272 <+39%200584%20166%200272>
> mob: +39  339 8844549 <+39%20339%20884%204549>
>
> http://www.geo-solutions.it
> http://twitter.com/geosolutions_it
>
> *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*
>
> Le informazioni contenute in questo messaggio di posta elettronica e/o
> nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
> loro utilizzo è consentito esclusivamente al destinatario del messaggio,
> per le finalità indicate nel messaggio stesso. Qualora riceviate questo
> messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
> darcene notizia via e-mail e di procedere alla distruzione del messaggio
> stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
> divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
> utilizzarlo per finalità diverse, costituisce comportamento contrario ai
> principi dettati dal D.Lgs. 196/2003.
>
>
>
> The information in this message and/or attachments, is intended solely for
> the attention and use of the named addressee(s) and may be confidential or
> proprietary in nature or covered by the provisions of privacy act
> (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
> Code).Any use not in accord with its purpose, any disclosure, reproduction,
> copying, distribution, or either dissemination, either whole or partial, is
> strictly forbidden except previous formal approval of the named
> addressee(s). If you are not the intended recipient, please contact
> immediately the sender by telephone, fax or e-mail and delete the
> information in this message that has been received in error. The sender
> does not give any warranty or accept liability as the content, accuracy or
> completeness of sent messages and accepts no responsibility  for changes
> made after they were sent or for other risks which arise as a result of
> e-mail transmission, viruses, etc.
>
> ---
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] [Geotools-devel] upgrade postgresql JDBC driver to 42.1.1 (full binary xfer)

2017-05-30 Thread Dave Blasby 
Hi, Ben,

Thanks for putting the PR together and making sure everything was tested
(esp online tests).

WRT postgresql version support, I found this in the release notes for
42.0.0;


   - Support for PostgreSQL versions below 8.2 was dropped


Thanks,
Dave

On Mon, May 29, 2017 at 8:31 PM, Ben Caradoc-Davies 
wrote:

> Dave,
>
> with this upgrade, a full GeoTools build with online jdbc-postgis tests,
> GeoServer build, community module compilation, and app-schema online tests
> against postgis all pass. I also confirmed that the correct jar is included
> in the assembled war and zip files.
>
> Jira issue: https://osgeo-org.atlassian.net/browse/GEOT-5741
> Pull request for master: https://github.com/geotools/geotools/pull/1605
>
> Tested on debian unstable amd64:
> postgresql-9.6 9.6.3-3 amd64
> postgresql-9.6-postgis-2.3 2.3.1+dfsg-2 amd64
>
> It would be good if someone could test this upgrade against an older
> postgresql (especially 8).
>
> $ mvn -version
> Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426;
> 2017-04-04T07:39:06+12:00)
> Maven home: /home/ben/java/maven
> Java version: 1.8.0_131, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/java-8-openjdk-amd64/jre
> Default locale: en_GB, platform encoding: UTF-8
> OS name: "linux", version: "4.9.0-3-amd64", arch: "amd64", family: "unix"
>
> Kind regards,
> Ben.
>
>
> On 30/05/17 09:22, Dave Blasby wrote:
>
>> Hi,
>>
>> For GeoGig, we noticed that the latest Postgresql JDBC driver (42.1.1) now
>> allows full-binary data transfer.  This is better than 25% less bandwidth
>> than Base64 encoding!
>>
>> I'd like to update the pom.xml  from 9.4.1211 to 42.1.1.
>>
>> NOTE: PostGIS could be upgraded to use this as its a big win for a remote
>> (networked) database.
>> Note: you must use a prepared statement!
>>
>>
>> https://jdbc.postgresql.org/download.html
>>
>> From the pom.xml;
>>>
>> 9.4.1211
>>
>> Comments?
>>
>> Thanks,
>> Dave
>>
>>
>>
>> 
>> --
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>
>>
>>
>> ___
>> GeoTools-Devel mailing list
>> geotools-de...@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>>
>>
> --
> Ben Caradoc-Davies 
> Director
> Transient Software Limited 
> New Zealand
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] upgrade postgresql JDBC driver to 42.1.1 (full binary xfer)

2017-05-30 Thread Andrea Aime 
On Tue, May 30, 2017 at 7:01 PM, Dave Blasby 
wrote:

> Hi, Andrea,
>
> Only updating the driver version.
>
> I can work with the PostGIS maintainer to get it in - it's fairly easy
> (just need to ensure that you are using prepared statements).
>

Maintainer eh? It used to be me and Justin.
When you say "ensure that you are using prepared statements" is that only
to get the actual binary transfer, or it would just
break?
And does that require some specific version of postgresql?

The 25% less transfer is interesting, wondering if you have been looking at
TWKB, that should provide greater savings (with
some potential loss of precision).

Cheers
Andrea

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

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054  Massarosa (LU)
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39  339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

*AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*

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



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

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

Re: [Geoserver-devel] upgrade postgresql JDBC driver to 42.1.1 (full binary xfer)

2017-05-30 Thread Dave Blasby 
Hi, Andrea,

Only updating the driver version.

I can work with the PostGIS maintainer to get it in - it's fairly easy
(just need to ensure that you are using prepared statements).  The
difficulty is in verifying it's working - you don't really have any access
to what's happening in the driver.  For GeoGig, I verified using wireshark
(you can also verify by stepping into the driver).

Thanks,
Dave

On Tue, May 30, 2017 at 1:03 AM, Andrea Aime 
wrote:

> So, are you proposing just an upgrade of the driver, or are you also going
> to change the postgis store code to leverage the
> binary transfer?
>
> Cheers
> Andrea
>
> On Mon, May 29, 2017 at 11:22 PM, Dave Blasby 
> wrote:
>
>> Hi,
>>
>> For GeoGig, we noticed that the latest Postgresql JDBC driver (42.1.1)
>> now allows full-binary data transfer.  This is better than 25% less
>> bandwidth than Base64 encoding!
>>
>> I'd like to update the pom.xml  from 9.4.1211 to 42.1.1.
>>
>> NOTE: PostGIS could be upgraded to use this as its a big win for a remote
>> (networked) database.
>> Note: you must use a prepared statement!
>>
>>
>> https://jdbc.postgresql.org/download.html
>>
>> From the pom.xml;
>> 9.4.1211
>>
>> Comments?
>>
>> Thanks,
>> Dave
>>
>> 
>> --
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> ___
>> Geoserver-devel mailing list
>> Geoserver-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>
>>
>
>
> --
> ==
> GeoServer Professional Services from the experts! Visit
> http://goo.gl/it488V for more information.
> ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions S.A.S.
> Via di Montramito 3/A
> 55054  Massarosa (LU)
> phone: +39 0584 962313 <+39%200584%20962313>
> fax: +39 0584 1660272 <+39%200584%20166%200272>
> mob: +39  339 8844549 <+39%20339%20884%204549>
>
> http://www.geo-solutions.it
> http://twitter.com/geosolutions_it
>
> *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*
>
> Le informazioni contenute in questo messaggio di posta elettronica e/o
> nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
> loro utilizzo è consentito esclusivamente al destinatario del messaggio,
> per le finalità indicate nel messaggio stesso. Qualora riceviate questo
> messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
> darcene notizia via e-mail e di procedere alla distruzione del messaggio
> stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
> divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
> utilizzarlo per finalità diverse, costituisce comportamento contrario ai
> principi dettati dal D.Lgs. 196/2003.
>
>
>
> The information in this message and/or attachments, is intended solely for
> the attention and use of the named addressee(s) and may be confidential or
> proprietary in nature or covered by the provisions of privacy act
> (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
> Code).Any use not in accord with its purpose, any disclosure, reproduction,
> copying, distribution, or either dissemination, either whole or partial, is
> strictly forbidden except previous formal approval of the named
> addressee(s). If you are not the intended recipient, please contact
> immediately the sender by telephone, fax or e-mail and delete the
> information in this message that has been received in error. The sender
> does not give any warranty or accept liability as the content, accuracy or
> completeness of sent messages and accepts no responsibility  for changes
> made after they were sent or for other risks which arise as a result of
> e-mail transmission, viruses, etc.
>
> ---
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] GeoTools / GeoWebCache / GeoServer Meeting 2017-05-30

2017-05-30 Thread Torben Barsballe 
Attending

Andrea Aime

Ian Turton

Jody Garnett

Jukka Rahkonen

Kevin Smith

Torben Barsballe
Agenda

   -

   CalGIS Workshop retrospective
   -

   Better description for community modules
   -

   Chit Chat


Action items

   -

   AA: make a GSIP to get some more information out of developers asking
   for a community module
   -

   JG: follow up GSIP with actual developers guide documentation changes

Action Items from last meeting

   -

   TB/KS: release 17.1 / 2.11.1 (done)
   -

   KS: make GeoServer change proposal for GWC vulnerability (pending)
   -

   JG: FOSS4G Blog post when presentations announced (pending)

CalGIS Workshop

Intro to GeoServer workshop:

   -

   90 % were windows users
   -

   Many had not seen open source before
   -

   Around 50 people, mix of VM and Community Downloads
   -

   Installation of extensions was “why is this so technical” :)
   -

   TLDR: Windows installers are earning their keep :)

Better description for community modules

Like: text? Or how well they can be trusted?

Goal: An extensive description of what community module is for, see all the
questions around Neil's recent proposal for an example :)

Jody: Do we care if the codebase is not ready for the codebase?

   -

   Andrea: Yes we should if it plans to merge eventually


Ideas:

   -

   What the module does
   -

   Ideas about configuration/UI/whatever if applicable
   -

   Dependencies
   -

   Verify overlap with existing modules, making sure we are not duplicating
   work/effort (just a show that this was considered)
   -

   Any  plan to get it into support land anytime soon?


Previously: GeoTools used to ask for wiki page for unsupported modules;
kind of like a mini design document?

   -

   Andrea was thinking more high level…


Thoughts:

   -

   Jody - wanted something lightweight to help onboard new committees
   -

  Andrea - that is not working :P
  -

   We can supply a sample email, that shows covering the above topics
   -

  Wiki page or developers guide
  -


 
http://docs.geoserver.org/latest/en/developer/policies/community-modules.html
 -

   GSIP or PR?
   -

  Action (Andrea/Simone) to make a GSIP to define the above list.
  -

  Action (Jody) PR to update the developers guide.

Chit Chat

For Ben - Urls vs URLs

   -

   Jody - URLs ← follow our coding conventions
   -

  Can we resolve this now or let ben suffer on the email
  -

  http://docs.geotools.org/latest/developer/conventions/name.html
  -

  http://www.oracle.com/technetwork/java/codeconventions-135099.html
  -

 Try to keep your class names simple and descriptive. Use whole
 words-avoid acronyms and abbreviations (unless the
abbreviation is much
 more widely used than the long form, such as URL or HTML).
 -

   This is a follow on from another bug, trying to fix the code once


CalGIS Code sprint focused on geotools:

   -

   Adding parameter descriptions to functions
   -

  copy from geoserver user guide, to geotools data structure
  -

  See pictures http://www.osgeo.org/node/1791


Bug stomp?

   -

   Andrea and Torben got a lot done
   -

  If it takes a couple hours, move on it is too big :)
  -

   There are a number of pull requests awaiting review


Marlin:

   -

   Can we upload new version?
   -


   
https://github.com/bourgesl/marlin-renderer/releases/download/v0.7.5_2/marlin-0.7.5-Unsafe.jar
   -

   Uploaded:
   https://repo.boundlessgeo.com/main/org/marlin/marlin/0.7.5-Unsafe/


JAI-EXT

   -

   Getting close to be used for default
   -

   GeoSolutions has a number of production servers, Boundless includes
   JAI-EXT for our customers


Technical Debt JAI replacement: update?

   -

   OSGeo Live has started collaboration with Debian; who is very much
   against sun binary license used by JAI. GeoServer may not be included in
   subsequent OSGeo Live distributions. Talk to Ben for details?
   -

   LocationTech is also keen to get the Raster Processing Engine project
   started
   -

   See wiki for plan https://github.com/geotools/geotools/wiki/Replace-JAI


Technical Debt XML Parsing:

   -

   For Schema we considered EMF and Xerces
   -

  Technically this is XSD (which is an EMF representation of schema)
  -

  We have problems with memory leaks here
  -

  Xerces offered the other stable representation of Schema
  -

   JAXB - http://www.ogcnetwork.net/jaxb4ogc
   -

  Able to generate java beans as static Java Beans
  -

  We need to generate the parser bindings by hand
  -

   EMF - did its own beans (called EObject), also able to model collection
   contents
   -

  Very strict on use of factories, etc…
  -

  The tech stack here is ECORE and GenModel, not JavaBeans
  -

  Justin did ‘reflection’ to auto generate the parser bindings
  -

   GML representation - has two uses
   -

[Geoserver-devel] [JIRA] (GEOS-8159) WPS DownloadProcess doesn't respect cropToROI parameter

2017-05-30 Thread Daniele Romagnoli (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniele Romagnoli created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 GeoServer /  GEOS-8159  
 
 
  WPS DownloadProcess doesn't respect cropToROI parameter   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 2.10.3, 2.11.1  
 
 
Assignee: 
 Daniele Romagnoli  
 
 
Components: 
 Community modules  
 
 
Created: 
 30/May/17 6:24 PM  
 
 
Fix Versions: 
 2.10.4, 2.11.2  
 
 
Priority: 
  Medium  
 
 
Reporter: 
 Daniele Romagnoli  
 

  
 
 
 
 

 
 Quoting from the Download Process documentation: http://docs.geoserver.org/stable/en/user/community/wps-download/index.html#download-process cropToROI : boolean parameter to allow cropping to actual ROI, or its envelope (optional) At the moment, it always crop to actual ROI, no matter which value is set to cropToROI.  
 

  
 
 
  
 

 
 
 

 
 
 Add Comment

[Geoserver-devel] [JIRA] (GEOS-8158) WFSPPIO fails to remove MetaDataProperty attributes

2017-05-30 Thread Ian Turton (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ian Turton created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 GeoServer /  GEOS-8158  
 
 
  WFSPPIO fails to remove MetaDataProperty attributes   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 2.11.1  
 
 
Assignee: 
 Ian Turton  
 
 
Components: 
 WPS  
 
 
Created: 
 30/May/17 5:55 PM  
 
 
Fix Versions: 
 2.11.2  
 
 
Priority: 
  Medium  
 
 
Reporter: 
 Ian Turton  
 

  
 
 
 
 

 
 If you load data from a WFS in a WPS and then try to write the results out as a Zipped Shapefile (and other formats) fail as the features still contain the MetaDataProperty attribute which is an object.  
 

  
 
 
  
 

 
 
 

 
 
 Add Comment

[Geoserver-devel] [JIRA] (GEOS-8157) NCWMS - GetLegendGraphic throws an exception when invoked for dynamic palette styles

2017-05-30 Thread Nuno Oliveira (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nuno Oliveira created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 GeoServer /  GEOS-8157  
 
 
  NCWMS - GetLegendGraphic throws an exception when invoked for dynamic palette styles
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Nuno Oliveira  
 
 
Components: 
 Community modules  
 
 
Created: 
 30/May/17 5:46 PM  
 
 
Priority: 
  Medium  
 
 
Reporter: 
 Nuno Oliveira  
 

  
 
 
 
 

 
 This issues happens because colormap module on which ncwms depends is not instantiation the coverage reader with the coverage info. In consequence only no-data dimension will be available, since the ncwms needs to access actual data the following exception is returned: 

 

"1.0" encoding="UTF-8" standalone="no"?>"http://localhost:8080/geoserver/schemas/wms/1.1.1/WMS_exception_1_1_1.dtd"> "1.1.1" >   
  Failed to extract legend
Filter Function problem for function gridCoverageStats
Could not find the minimum from RenderedSampleDimension(precip30min:[-.0 ... -.0])
  ‣ Category(No data:[-.0 ... -.0])
 of band 0

Re: [Geoserver-devel] Documentation build

2017-05-30 Thread Jody Garnett 
yep, that was the goal :)

--
Jody Garnett

On 26 May 2017 at 14:14, Nuno Oliveira 
wrote:

> Hi Ben,
>
> Indeed with "ant user" it works just fine and only HTML seems to be build
> :)
>
> Thanks Ben !
>
> On 26-05-2017 21:55, Ben Caradoc-Davies wrote:
>
>> On 27/05/17 01:17, Nuno Oliveira wrote:
>>
>>> It was really nice to be able to build only HTML documentation for
>>> example with the makefiles.
>>>
>>
>> I use "ant user" which I think builds just the HTML. The is documented in
>> the README.md. I am using apache-ant-1.10.1. I have not tried using Maven
>> to build the docs.
>>
>> Kind regards,
>>
>>
> --
> ==
> GeoServer Professional Services from the experts!
> Visit http://goo.gl/it488V for more information.
> ==
> Nuno Miguel Carvalho Oliveira
> @nmcoliveira
> Software Engineer
>
> GeoSolutions S.A.S.
> Via di Montramito 3/A
> 55054  Massarosa (LU)
> Italy
>
> phone: +39 0584 962313
> fax:   +39 0584 1660272
> mob:   +39 333 8128928
>
> http://www.geo-solutions.it
> http://twitter.com/geosolutions_it
>
> ---
>
> AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
> Le informazioni contenute in questo messaggio di posta elettronica e/o
> nel/i file/s allegato/i sono
> da considerarsi strettamente riservate. Il loro utilizzo è consentito
> esclusivamente al destinatario del messaggio, per le finalità indicate
> nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il
> destinatario, Vi preghiamo cortesemente di darcene notizia via e
> -mail e di procedere alla distruzione del messaggio stesso, cancellandolo
> dal Vostro sistema. Conservare il messaggio stesso, divulgarlo
> anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo
> per finalità diverse, costituisce comportamento contrario ai
> principi dettati dal D.Lgs. 196/2003.
>  The information in this message and/or attachments, is intended solely
> for the attention and use of
> the named addressee(s) and may be confidential or proprietary in nature or
> covered by the provisions of privacy act (Legislative Decree
> June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in
> accord with its purpose, any disclosure, reproduction, copying,
> distribution, or either dissemination, either whole or partial, is
> strictly forbidden except previous formal approval of the named
> addressee(s). If you are not the intended recipient, please contact
> immediately the sender by telephone, fax or e-mail and delete the
> information in this message that has been received in error. The sender
> does not give any warranty or accept liability as the content,
> accuracy or completeness of sent messages and accepts no responsibility
> for changes made after they were sent or for other risks which
> arise as a result of e-mail transmission, viruses, etc.
>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] new community module workflow

2017-05-30 Thread Niels Charlier 

What is your opinion on the dependency concern?

What do you think of having the new module be called "task manager" or 
something like that.


Although it will contain a quite a bit of task implementation that 
regards remote data management specifically. Should I add two new 
modules though :/


Regards

Niels


On 30-05-17 04:05, Ben Caradoc-Davies wrote:

On 30/05/17 00:55, Niels Charlier wrote:

Therefore, logically, it would be importer that needs be modified to be
built on top of my API rather than me building on top of importer.


This sounds like a great option. A modest investment in refactoring 
now will save us the future maintenance overhead introduced by 
duplication. (And I speak us someone currently fixing my own 
ill-considered DataUtilities duplication from five years ago.)


Kind regards,




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

Re: [Geoserver-devel] upgrade postgresql JDBC driver to 42.1.1 (full binary xfer)

2017-05-30 Thread Andrea Aime 
So, are you proposing just an upgrade of the driver, or are you also going
to change the postgis store code to leverage the
binary transfer?

Cheers
Andrea

On Mon, May 29, 2017 at 11:22 PM, Dave Blasby 
wrote:

> Hi,
>
> For GeoGig, we noticed that the latest Postgresql JDBC driver (42.1.1) now
> allows full-binary data transfer.  This is better than 25% less bandwidth
> than Base64 encoding!
>
> I'd like to update the pom.xml  from 9.4.1211 to 42.1.1.
>
> NOTE: PostGIS could be upgraded to use this as its a big win for a remote
> (networked) database.
> Note: you must use a prepared statement!
>
>
> https://jdbc.postgresql.org/download.html
>
> From the pom.xml;
> 9.4.1211
>
> Comments?
>
> Thanks,
> Dave
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
>


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

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054  Massarosa (LU)
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39  339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

*AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*

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



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

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

Re: [Geoserver-devel] Reminder: Geo{Tools, WebCache, Server} Meeting at 15:30 UTC on Tuesday

2017-05-30 Thread Brad Hards 
Please accept my apologies (for whoever is there), but its 0130 for me.

Brad




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