Re: [Geotools-devel] Moving the geopackage module to supported land

2016-10-25 Thread Andrea Aime 
Cough cough... anyone? :-)

Cheers
Andrea

On Thu, Oct 20, 2016 at 12:51 PM, Andrea Aime 
wrote:

> Hi,
> I'm writing this mail to propose the move of the geopackge module to
> supported land.
> The proposal is backed by this pull request, adding the final touches to
> the module:
> https://github.com/geotools/geotools/pull/1358
>
> Looking at the procedures, it does not look like I have to write a format
> proposal in the wiki
> http://docs.geotools.org/latest/developer/procedures/supported.html
>
> In terms of "gold stars" (http://docs.geotools.org/
> latest/developer/procedures/check.html) the module has:
>
>- Correct headers: check
>- Releasable no blocking bugs in jira: check
>- Used in anger: sort of, GeoServer has a
>- Optimised: one can use the low level API, the high level is as
>optimised as as any other JDBC based module, the reader reads the right
>overview and only the tiles need to cover the requested area. Changes made
>so that we don't try to create all geopackage tables each and every time a
>connection is grabbed. Check.
>- Supported: the pull request has docs, the module maintainer would be
>me but others are welcomed to join :-). Check.
>
> I'd say the module is 4 stars and something.
>
> In terms of compliance with the CITE tests, there are two small picky
> tests that we are failing, I plan to fix that soon too (not that CITE
> compliance, or lack there of, has been part of module evaluations before,
> but it's nice to know that we're 99% there).
>
> Feedback welcomed!
>
> 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.
>
> ---
>



-- 
==
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 conf

Re: [Geotools-devel] Moving the geopackage module to supported land

2016-10-25 Thread Simone Giannecchini 
Well, if nobody else is interested I'll give my +1.




Regards,
Simone Giannecchini
==
GeoServer Professional Services from the experts!
Visit http://goo.gl/it488V for more information.
==
Ing. Simone Giannecchini
@simogeo
Founder/Director

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.


On Tue, Oct 25, 2016 at 9:44 AM, Andrea Aime
 wrote:
> Cough cough... anyone? :-)
>
> Cheers
> Andrea
>
> On Thu, Oct 20, 2016 at 12:51 PM, Andrea Aime 
> wrote:
>>
>> Hi,
>> I'm writing this mail to propose the move of the geopackge module to
>> supported land.
>> The proposal is backed by this pull request, adding the final touches to
>> the module:
>> https://github.com/geotools/geotools/pull/1358
>>
>> Looking at the procedures, it does not look like I have to write a format
>> proposal in the wiki
>> http://docs.geotools.org/latest/developer/procedures/supported.html
>>
>> In terms of "gold stars"
>> (http://docs.geotools.org/latest/developer/procedures/check.html) the module
>> has:
>>
>> Correct headers: check
>> Releasable no blocking bugs in jira: check
>> Used in anger: sort of, GeoServer has a
>> Optimised: one can use the low level API, the high level is as optimised
>> as as any other JDBC based module, the reader reads the right overview and
>> only the tiles need to cover the requested area. Changes made so that we
>> don't try to create all geopackage tables each and every time a connection
>> is grabbed. Check.
>> Supported: the pull request has docs, the module maintainer would be me
>> but others are welcomed to join :-). Check.
>>
>> I'd say the module is 4 stars and something.
>>
>> In terms of compliance with the CITE tests, there are two small picky
>> tests that we are failing, I plan to fix that soon too (not that CITE
>> compliance, or lack there of, has been part of module evaluations before,
>> but it's nice to know that we're 99% there).
>>
>> Feedback welcomed!
>>
>> 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.L

[Geotools-devel] Build failed in Jenkins: geotools-master-online-sqlserver-jtds #6

2016-10-25 Thread monitor 
See 


--
[...truncated 6968 lines...]
 [exec] copying downloadable files... [ 69%] 

 [exec] copying downloadable files... [ 71%] 

 [exec] copying downloadable files... [ 73%] 

 [exec] copying downloadable files... [ 76%] 

 [exec] copying downloadable files... [ 78%] 

 [exec] copying downloadable files... [ 80%] 

 [exec] copying downloadable files... [ 82%] 

 [exec] copying downloadable files... [ 84%] 

 [exec] copying downloadable files... [ 86%] 

 [exec] copying downloadable files... [ 89%] 

 [exec] copying downloadable files... [ 91%] 

 [exec] copying downloadable files... [ 93%] 

 [exec] copying downloadable files... [ 95%] 

 [exec] copying downloadable files... [ 97%] 

 [exec] copying downloadable files... [100%] 


 [exec] copying static files... done
 [exec] dumping search index... done
 [exec] dumping object inventory... done
 [exec] build succeeded.

web:

sphinx:
 [echo] Running sphinx-build -D release=17-SNAPSHOT -W -b html -d 
"
 . 
"
 [exec] Making output directory...
 [exec] Running Sphinx v1.2b1
 [exec] loading pickled environment... not yet created
 [exec] building [html]: targets for 3 source files that are out of date
 [exec] updating environment: 3 added, 0 changed, 0 removed
 [exec] reading sources... [ 33%] about
 [exec] reading sources... [ 66%] getinvolved
 [exec] reading sources... [100%] index

 [exec] looking for now-outdated files... none found
 [exec] pickling environment... done
 [exec] checking consistency... done
 [exec] preparing documents... done
 [exec] writing output... [ 33%] about
 [exec] writing output... [ 66%] getinvolved
 [exec] writing output... [100%] index

 [exec] writing additional files... search
 [exec] copying static files... done
 [exec] dumping search index... done
 [exec] dumping object inventory... done
 [exec] build succeeded.

developer:

sphinx:
 [echo] Running sphinx-build -D release=17-SNAPSHOT -W -b html -d 
"
 . 
"

[Geotools-devel] Heads up for release day tomorrow

2016-10-25 Thread Ian Turton 
I'm planning (with Kevin's help) to push the GeoTools 16.0 and GeoServer 2.10.0
releases, so if you have any bug fixes that you want to get into the
releases please make sure you push them today.

Ian

-- 
Ian Turton
--
The Command Line: Reinvented for Modern Developers
Did the resurgence of CLI tooling catch you by surprise?
Reconnect with the command line and become more productive. 
Learn the new .NET and ASP.NET CLI. Get your free copy!
http://sdm.link/telerik___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

[Geotools-devel] [JIRA] (GEOT-5554) SQLServerJNDIDataSourceOnlineTest fails if the Microsoft driver is not in the classpath

2016-10-25 Thread Andrea Aime [Administrator] (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrea Aime [Administrator] created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 GeoTools /  GEOT-5554  
 
 
  SQLServerJNDIDataSourceOnlineTest fails if the Microsoft driver is not in the classpath   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 jdbc-sqlserver plugin  
 
 
Created: 
 25/Oct/16 10:59 AM  
 
 
Priority: 
  Medium  
 
 
Reporter: 
 Andrea Aime [Administrator]  
 

  
 
 
 
 

 
 Since the default driver in the classpath is the JTDS one, and the Microsoft one is optional, the test should not run if the Microsoft one is missing  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This mes

[Geotools-devel] Jenkins build is back to normal : geotools-master-online-sqlserver-jtds #7

2016-10-25 Thread monitor 
See 



--
The Command Line: Reinvented for Modern Developers
Did the resurgence of CLI tooling catch you by surprise?
Reconnect with the command line and become more productive. 
Learn the new .NET and ASP.NET CLI. Get your free copy!
http://sdm.link/telerik
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

[Geotools-devel] [JIRA] (GEOT-5555) PointStacker needs to have an option to compute cluster position based on the position of clustered points

2016-10-25 Thread Cosmin Cioranu (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cosmin Cioranu created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 GeoTools /  GEOT-  
 
 
  PointStacker needs to have an option to compute cluster position based on the position of clustered points   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Affects Versions: 
 17-beta  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 process  
 
 
Created: 
 25/Oct/16 2:12 PM  
 
 
Environment: 
 ALL  
 
 
Labels: 
 gs:PointStaker weighted cluster position  
 
 
Priority: 
  Low  
 
 
Reporter: 
 Cosmin Cioranu  
 
 
Original Estimate: 
1 week 
 
 
Remaining Estimate:  
1 week 
 

  
 
 
 
 

 
 gs:PointStacker computes the cluster position as closest to the center of it's virtual square (derived mainly from cellSize parameter). However there are use cases which this position needs to be weighted as an average of all points which cluster holds (or encompasses).  I propose to add a parameter called weightedClusterPosition=true/false, default false (to keep the original functionality)

Re: [Geotools-devel] SQL Server: could we have two online builds, one for JTDS, one for microsoft drivers

2016-10-25 Thread Andrea Aime 
Hi,
I have added the second build, so we have one for JTDS, one for Microsoft
driver. Both are blue now:
http://ares.boundlessgeo.com/jenkins/view/testing-online/

Cheers
Andrea



On Mon, Oct 24, 2016 at 3:48 PM, Andrea Aime 
wrote:

> Hi,
> mind one thing, I'm saying JTDS is used because that's what the fixture
> ends up saying to use, but given the
> setup, it seems both JTDS and microsoft drivers are in the classpath
> (probably not a good idea):
>
> #Set up fixtures
> mkdir -p ~/.geotools
> rm -f ~/.geotools/postgis.properties
> rm -f ~/.geotools/mysql.properties
> rm -f ~/.geotools/sqlserver.properties
> rm -f ~/.geotools/oracle.properties
> set +x
>
> #SQLServer
> printf "user=sa\nport=1433\npassword=Boundless78902!\npasswd=
> Boundless78902!\nurl=jdbc\:sqlserver\://sql2014.dev.boundlessgeo.com
> \:1433\nhost=sql2014.dev.boundlessgeo.com\ndatabase=geotoolstest\
> ndriver=com.microsoft.sqlserver.jdbc.SQLServerDriver\nskip.on.failure=false\n"
> > ~/.geotools/sqlserver.properties
>
> #JTDS SQLServer
> printf "user=sa\nport=1433\npassword=Boundless78902!\npasswd=
> Boundless78902!\nurl=jdbc\:jtds\:sqlserver\://sql2014.dev.boundlessgeo.com
> \:1433;DatabaseName=geotoolstest\nhost=sql2014.dev.boundlessgeo.com
> \ndatabase=geotoolstest\ndriver=net.sourceforge.jtds.jdbc.Driver\
> nskip.on.failure=false\ndbtype=jtds-sqlserver\n" > ~/.geotools/sqlserver.
> properties
> set -x
>
> See above, the JTDS setup ends up overwriting the microsoft one, even if
> the build command line puts the microsoft driver in the classpath:
>
> -U clean install -Djava.awt.headless=true -Dtest.maxHeapSize=512M -Dall
> -Djava.io.tmpdir=/var/lib/jenkins/tmp -P online -fae *-Dsqlserver=true*
> -pl modules/library/jdbc -amd
>
> Cheers
> Andrea
>
>
> On Mon, Oct 24, 2016 at 3:45 PM, Andrea Aime  > wrote:
>
>> Hi,
>> the current sql server online builds appears to be using JTDS, which
>> often sports
>> a significantly different behavior than the Microsoft one.
>>
>> If we can have both drivers installed on Ares, would you mind running two
>> parallel
>> builds for the two drivers?
>>
>> 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.
>>
>> ---
>>
>
>
>
> --
> ==
> 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 destina

[Geotools-devel] [JIRA] (GEOT-5556) Updating a reprojecting imagemosaic fails with NPE

2016-10-25 Thread Devon Tucker (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Devon Tucker created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 GeoTools /  GEOT-5556  
 
 
  Updating a reprojecting imagemosaic fails with NPE   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Devon Tucker  
 
 
Components: 
 imagemosaic plugin  
 
 
Created: 
 25/Oct/16 11:48 PM  
 
 
Priority: 
  Medium  
 
 
Reporter: 
 Devon Tucker  
 

  
 
 
 
 

 
 When trying to update a reprojecting image mosaic store the catalog update fails with a null pointer exception inside the ReprojectingGranuleHandler.java. It looks like the MosaicConfiguration isn't properly being propagated during an update.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
 

Re: [Geotools-devel] Cylindrical Equal Area Projection

2016-10-25 Thread Peter Borissow 
Andrea-    I finally found some time to try to push this code to Github. I 
cloned "master" using Netbeans but it looks a little off. Is this the correct 
branch or should I clone one of the other branches (e.g. 16.x)?

Thanks,Peter


  From: Peter Borissow 
 To: Andrea Aime  
Cc: Geotools-Devel list 
 Sent: Friday, May 8, 2015 4:15 PM
 Subject: Re: [Geotools-devel] Cylindrical Equal Area Projection
   
Hello Andrea-    Apologies for the late response. I have been on travel with 
limited access to email. It might be a couple more weeks before I get to my 
computer to submit pull request and complete the assignment papers as you have 
requested. 

In the interim, if you or anyone else wants to submit a pull request, go for 
it! I claim no copyright to the source code since it is a derived product from 
other open source projects. 

Best Regards,
Peter

  From: Andrea Aime 
 To: Peter Borissow  
Cc: Geotools-Devel list  
 Sent: Sunday, April 26, 2015 5:57 AM
 Subject: Re: [Geotools-devel] Cylindrical Equal Area Projection
   
On Tue, Apr 7, 2015 at 12:18 PM, Andrea Aime  
wrote:

The fact they are off after a full roundtrip is normal, precision of floating 
point numbers is limited.
But I don't know about the residual difference between cs2cs and geotools, 
nothing comes to mind right now I'll try to have another look, but it might 
be some days before I have time again
I'd suggest that in the meantime you contribute what you can with a pull 
request, with proper headers, andsend the copyright assignment to OSGeo

Hi Peter, did you manage to make any progress on the pull request and the 
copyright assignment papers?I cannot help you if you don't do at least those 
two (your code would not be merge-able anyways without them).


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

Ing. Andrea Aime 
@geowolfTechnical Lead
GeoSolutions S.A.S.Via Poggio alle Viti 118755054  Massarosa (LU)Italyphone: 
+39 0584 962313fax: +39 0584 1660272mob: +39  339 8844549
http://www.geo-solutions.ithttp://twitter.com/geosolutions_it
AVVERTENZE AI SENSI DEL D.Lgs. 196/2003Le 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.
---

   

   --
The Command Line: Reinvented for Modern Developers
Did the resurgence of CLI tooling catch you by surprise?
Reconnect with the command line and become more productive. 
Learn the new .NET and ASP.NET CLI. Get your free copy!
http://sdm.link/telerik___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

[Geotools-devel] MongoDB complex feature store compatible with app-schema

2016-10-25 Thread Nuno Oliveira 

Hi,

The idea here is to be able to output a MongoDB collection content as 
complex features.


For those wondering, how MongoDB store works right now, it basically 
flats the JSON
elements and ignore collections (geometries are treated as special case 
and properly encoded).


Consider that we have in a MongoDB a collection called stations that 
contains the measurements

of several meteorological stations:

   db.stations.insert({
  "id": "1",
  "geometry": {
  "coordinates": [
  50.0,
  60.0
  ],
  "type": "Point"
  },
  "name": "station 1",
  "contact": {
"mail": "stati...@mail.com"
  },
  "measurements": [
  {
  "name": "temp",
  "unit": "c",
  "value": 35.5
  },
  {
  "name": "wind",
  "unit": "km/h",
  "value": 110.5
  }
  ]
   })

   db.stations.createIndex({
  geometry: "2dsphere"
   })

The current MongoDB store will output something like this for a 
GetFeature request:


   
   http://www.opengis.net/wfs";
   xmlns:gml="http://www.opengis.net/gml"; xmlns:mongo="mongo"
   xmlns:wfs="http://www.opengis.net/wfs";
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
   xsi:schemaLocation="mongo
   
http://localhost:8092/geoserver/mongo/wfs?service=WFS&version=1.0.0&request=DescribeFeatureType&typeName=mongo%3Astations3
   http://www.opengis.net/wfs
   http://schemas.opengis.net/wfs/1.0.0/WFS-basic.xsd";>

unknown




http://www.opengis.net/gml/srs/epsg.xml#4326";>
http://www.opengis.net/gml";>10,60


1
station 1
   stati...@mail.com


   

As you can see the the list of measurements was ignored and the JSON 
attributes were flatted (contact.mail).


If MongoDB stations collection was encoded as complex features the 
result should have been something similar to this instead:


   
   


station 1

stati...@mail.com


temp
c
35.5


wind
km/h
110.5


http://www.opengis.net/gml/srs/epsg.xml#4326";>
   50.0,60.0




   

The associated schema was attached to this mail.

App-schema can work with simple stores creating complex features by 
composing several simple features,
in the case of MongoDB we actually want to be able to map the complete 
JSON tree. This is the main reason
why MongoDB current store will not work with app-schema, we would only 
have access to the flat attributes.


The idea were would be to create a complex MongoDB store capable to 
answer app-schema queries by having
access to all the JSON object, this store will only be usable by 
app-schema and cannot be used in a standalone way.
This way we will reuse all app-schema already implemented machinery and 
avoid to duplicate a lot of complex code.


I already perform some tests and was able to get complex features with 
simple mappings:




data_source
st
st:StationFeature



st:StationFeature


jsonSelect("stations.id")



st:name

jsonSelect("stations.name")



st:contact/st:mail

jsonSelect("stations.contact.mail")

true





In this example I used a filter function for explicitly select the deep 
JSON content.


The most difficult part is the mapping of the JSON lists as nested 
objects through feature
chaining, the way I found to do it right now is to use a filter function 
that tell

explicitly the path of the sub-collection:

   
st:measurement

jsonSelectCollection("stations.id",
   "stations.measurement")
   st:SituationMeasurement
FEATURE_LINK[1]

true
   

When performing a query we visit the filter I to see if we can found the 
explicit sub collection.


With this approach we will have a strange MongoDB complex store that 
only makes sense to use
with app-schema but we will reuse app-schema machinery and all this work 
will be contained in

a single module.

Opinions on this are very welcome, I know that this is a lot to digest 
and the subject is a little bit complex :)


Regards,

Nuno Oliveira

--
==
GeoServer Professional Services from the experts!
Visit http://goo.

[Geotools-devel] GeoTools 16.0 release incoming!

2016-10-25 Thread Jody Garnett 
Is everyone set for release tomorrow? I see a lot of great bug fixes coming
in...
--
Jody Garnett
--
The Command Line: Reinvented for Modern Developers
Did the resurgence of CLI tooling catch you by surprise?
Reconnect with the command line and become more productive. 
Learn the new .NET and ASP.NET CLI. Get your free copy!
http://sdm.link/telerik___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel