Re: [Geotools-devel] Upgrade to NetCDF-Java 4.6.6

[Ben Caradoc-Davies]

Merged on master, with Daniele's approval.

Any objection to backporting this one to 15.x / 2.9.x?

As this is a new feature and an upgraded dependency, I do not intend to 
backport to 14.x / 2.8.x.

Kind regards,
Ben.

On 14/06/16 23:28, Ben Caradoc-Davies wrote:
> NetCDF-Java 4.6.6 has been built and published, but not yet announced. I
> would like to upgrade GeoTools and GeoServer master and stable to use it
> (master first, then cherry-pick onto stable). GeoTools and GeoServer
> currently use NetCDF-Java 4.6.2.
>
> The main feature I want is improved support for rotated pole projections
> in GRIB2 files (I implemented support for GDS template 32769 in
> NetCDF-Java).
>
> [GEOT-5434] Upgrade to NetCDF-Java 4.6.6
> https://osgeo-org.atlassian.net/browse/GEOT-5434
>
> One change that may impact some users is the intentional removal of
> longitude normalisation in GRIB2 latitude/longitude files, introduced in
> NetCDF-Java 4.6.4 (before my changes). This requires a change in a unit
> test.
>
> [GEOT-5395] Build failure in gt-grib with -Dnetcdf.version=4.6.4 or later
> https://osgeo-org.atlassian.net/browse/GEOT-5395
>
> Pull request for GeoTools master:
> https://github.com/geotools/geotools/pull/1211
>
> Pull request for GeoServer master:
> https://github.com/geoserver/geoserver/pull/1640
>
> Once these PRs are merged, if there are no objections, I will cherry
> pick these changes onto 15.x / 2.9.x .
>
> Kind regards,
>

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

--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports. http://pubads.g.doubleclick.net/gampad/clk?id=1444514421=/41014381
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] GeoTools / GeoServer Meeting 2016-06-14

[Ben Caradoc-Davies]

Or if the March/September cadence is useful to ensure availability, we 
could wait until March (that is have a long 2.9.x cycle).

Or we could choose an October release for 2.10.0, that is one month 
late. We are trying to make up two months, so we could take one from 
2.9.x stable and one from 2.10.x stable. That does seem too short to me. 
2.9.2 would be the last stable 2.9.x before it goes into maintenance.

Kind regards,
Ben.

On 16/06/16 08:20, Jody Garnett wrote:
> I was just updating the schedule, based on what I remembered of the
> discussion. This is why it is in the meeting notes so we can sort this out.
>
> So if we go the other way are we looking at a November release?
>
> On Wed, Jun 15, 2016 at 12:16 PM Simone Giannecchini <
> simone.giannecch...@geo-solutions.it> wrote:
>
>> Hi All,
>> one thing strikes me here:
>> "We are looking at a short release cycle due to release delays of 2.9."
>>
>> Looking as in "yeah, that would be a bad idea"? :)
>>
>> What is the rationale behind making the life of 2.9 shorter? Its birth
>> was difficult hence I would expect extra care before moving to 2.10.
>> The clients I talk to do not usually rush towards new releases so
>> making a release shorter does not help with building more confidence,
>> I am afraid.
>>
>>
>>
>> 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, Jun 14, 2016 at 10:47 PM, Ben Caradoc-Davies 
>> wrote:
>>> GeoTools / GeoServer Meeting 2016-06-14
>>> ===
>>>
>>> Attending
>>> -
>>>
>>> Ben Caradoc-Davies
>>> Jody Garnett
>>> Torben Barsballe
>>>
>>> Apologies
>>> -
>>>
>>> Ian Turton
>>>
>>> Agenda
>>> --
>>>
>>> - GeoServer OSGeo Project Officer
>>> - Release schedule
>>> - OSGeo update
>>> - Upgrade to NetCDF-Java 4.6.6
>>> - ImageMosaic refactoring part 1
>>> - Pull requests
>>>
>>> Actions
>>> ---
>>>
>>> - Jody: encourage updates to docs/jira to record Simone as GeoServer
>>> project officer
>>> - Alessandro and Andrea: release 14.4 / 2.8.4
>>>
>>> Actions from last meeting
>>> -
>>>
>>> - Ben to email list to ask for more PMC votes on OSGeo copyright header
>>> legal advice [DONE]
>>> - Jody: Contact Justin to declare GeoTools copyright header policy
>>> change done, merge in change to developers guide [DONE]
>>>
>>> GeoServer OSGeo Project Officer
>>> ---
>>>
>>> Simone Giannecchini has volunteered:
>>> - OSGeo board updated
>>> - website:
>>> http://www.osgeo.org/content/foundation/board_and_officers.html (done)
>>> - wiki: https://wiki.osgeo.org/wiki/Contacts (done)
>>> - jira: https://osgeo-org.atlassian.net/projects/GEOS (not yet)
>>>
>>> Release schedule
>>> 
>>>
>>> 

Re: [Geotools-devel] [Geoserver-devel] About PSC meeting times

[Ben Caradoc-Davies]

+1 for rotating the meeting.

All voting is already conducted on the mailing lists, as it should be, 
to keep everything open and transparent. Only minor issues are handled 
informally. Nothing else can be formally agreed in a PMC / PSC meeting 
until all voting members have had a chance to vote. If any issue is 
mistakenly treated as minor, anyone can object and require further 
discussion or a vote. This is the purpose of the meeting notes. Nothing 
is binding until an open vote.

-0 on requiring PMS / PSC attendance. This might not be possible for 
some. We can encourage attendance, but in my view only voting is mandatory.

Kind regards,
Ben.

On 15/06/16 21:18, Simone Giannecchini wrote:
> Dear All,
> First of all I apologize for the crossposting.
>
> I wanted to discuss alternatives for PSC meetings in order to be able
> to attend (and same goes for the other people on this side of the
> world).
>
> First thing first, there is no way to find a decent time that would
> fit all the interested parties, we tried to find one and we failed.
>
> The suggestion I have is as follows:
>
> - rotate hours for the meetings, once we keep the current one, once we
> change it to a time where it would fit for EU
> - voting happens only on the mailing list
> - in specific cases we can ask the PSC to participate to one of the meetings
>
> This is of course suboptimal, but I believe it's a starter.
> Looking forward to reading your feedback.
>
> 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.
>
> --
> What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
> patterns at an interface-level. Reveals which users, apps, and protocols are
> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> J-Flow, sFlow and other flows. Make informed decisions using capacity planning
> reports. http://pubads.g.doubleclick.net/gampad/clk?id=1444514421=/41014381
> ___
> Geoserver-devel mailing list
> geoserver-de...@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>

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

--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports. http://pubads.g.doubleclick.net/gampad/clk?id=1444514421=/41014381
___
GeoTools-Devel 

Re: [Geotools-devel] GeoTools / GeoServer Meeting 2016-06-14

[Jody Garnett]

I was just updating the schedule, based on what I remembered of the
discussion. This is why it is in the meeting notes so we can sort this out.

So if we go the other way are we looking at a November release?

On Wed, Jun 15, 2016 at 12:16 PM Simone Giannecchini <
simone.giannecch...@geo-solutions.it> wrote:

> Hi All,
> one thing strikes me here:
> "We are looking at a short release cycle due to release delays of 2.9."
>
> Looking as in "yeah, that would be a bad idea"? :)
>
> What is the rationale behind making the life of 2.9 shorter? Its birth
> was difficult hence I would expect extra care before moving to 2.10.
> The clients I talk to do not usually rush towards new releases so
> making a release shorter does not help with building more confidence,
> I am afraid.
>
>
>
> 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, Jun 14, 2016 at 10:47 PM, Ben Caradoc-Davies 
> wrote:
> > GeoTools / GeoServer Meeting 2016-06-14
> > ===
> >
> > Attending
> > -
> >
> > Ben Caradoc-Davies
> > Jody Garnett
> > Torben Barsballe
> >
> > Apologies
> > -
> >
> > Ian Turton
> >
> > Agenda
> > --
> >
> > - GeoServer OSGeo Project Officer
> > - Release schedule
> > - OSGeo update
> > - Upgrade to NetCDF-Java 4.6.6
> > - ImageMosaic refactoring part 1
> > - Pull requests
> >
> > Actions
> > ---
> >
> > - Jody: encourage updates to docs/jira to record Simone as GeoServer
> > project officer
> > - Alessandro and Andrea: release 14.4 / 2.8.4
> >
> > Actions from last meeting
> > -
> >
> > - Ben to email list to ask for more PMC votes on OSGeo copyright header
> > legal advice [DONE]
> > - Jody: Contact Justin to declare GeoTools copyright header policy
> > change done, merge in change to developers guide [DONE]
> >
> > GeoServer OSGeo Project Officer
> > ---
> >
> > Simone Giannecchini has volunteered:
> > - OSGeo board updated
> > - website:
> > http://www.osgeo.org/content/foundation/board_and_officers.html (done)
> > - wiki: https://wiki.osgeo.org/wiki/Contacts (done)
> > - jira: https://osgeo-org.atlassian.net/projects/GEOS (not yet)
> >
> > Release schedule
> > 
> >
> > Updated the release schedule:
> > https://github.com/geoserver/geoserver/wiki/Release-Schedule
> >
> > We are looking at a short release cycle due to release delays of 2.9.
> >
> > - Alessandro and Andrea have (been) volunteered to release 14.4 / 2.8.4
> >
> > Release priorities/ideas/mad plans for GeoServer 2.10 release timeframe:
> > - Jody and Devon are taking a run at GeoTools codebase prior to foss4g
> > workshop in August. Intend to update library for Java 8 syntax.
> > - Status endpoint is collecting more and more sanity checks (expect GUI
> > 

Re: [Geotools-devel] GeoTools / GeoServer Meeting 2016-06-14

[Simone Giannecchini]

Hi All,
one thing strikes me here:
"We are looking at a short release cycle due to release delays of 2.9."

Looking as in "yeah, that would be a bad idea"? :)

What is the rationale behind making the life of 2.9 shorter? Its birth
was difficult hence I would expect extra care before moving to 2.10.
The clients I talk to do not usually rush towards new releases so
making a release shorter does not help with building more confidence,
I am afraid.



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, Jun 14, 2016 at 10:47 PM, Ben Caradoc-Davies  wrote:
> GeoTools / GeoServer Meeting 2016-06-14
> ===
>
> Attending
> -
>
> Ben Caradoc-Davies
> Jody Garnett
> Torben Barsballe
>
> Apologies
> -
>
> Ian Turton
>
> Agenda
> --
>
> - GeoServer OSGeo Project Officer
> - Release schedule
> - OSGeo update
> - Upgrade to NetCDF-Java 4.6.6
> - ImageMosaic refactoring part 1
> - Pull requests
>
> Actions
> ---
>
> - Jody: encourage updates to docs/jira to record Simone as GeoServer
> project officer
> - Alessandro and Andrea: release 14.4 / 2.8.4
>
> Actions from last meeting
> -
>
> - Ben to email list to ask for more PMC votes on OSGeo copyright header
> legal advice [DONE]
> - Jody: Contact Justin to declare GeoTools copyright header policy
> change done, merge in change to developers guide [DONE]
>
> GeoServer OSGeo Project Officer
> ---
>
> Simone Giannecchini has volunteered:
> - OSGeo board updated
> - website:
> http://www.osgeo.org/content/foundation/board_and_officers.html (done)
> - wiki: https://wiki.osgeo.org/wiki/Contacts (done)
> - jira: https://osgeo-org.atlassian.net/projects/GEOS (not yet)
>
> Release schedule
> 
>
> Updated the release schedule:
> https://github.com/geoserver/geoserver/wiki/Release-Schedule
>
> We are looking at a short release cycle due to release delays of 2.9.
>
> - Alessandro and Andrea have (been) volunteered to release 14.4 / 2.8.4
>
> Release priorities/ideas/mad plans for GeoServer 2.10 release timeframe:
> - Jody and Devon are taking a run at GeoTools codebase prior to foss4g
> workshop in August. Intend to update library for Java 8 syntax.
> - Status endpoint is collecting more and more sanity checks (expect GUI
> during 2.10.x timeframe?) https://osgeo-org.atlassian.net/browse/GEOS-4585
> https://osgeo-org.atlassian.net/browse/GEOS-7567
> - ImageMosaic api refactor ongoing
> - VectorTiles documentation
>
> OSGeo update
> 
>
> Board has been informed of new GeoServer project officer.
>
> Board approved asking for legal advice on GeoTools header policy.
> Ben/Jody are working with Michael Smith on this one
>
> OSGeo Marketing committee has asked how they can help:
> - GeoTools: Encourage committers, always encourage committers
> - GeoServer: Encourage 

Re: [Geotools-devel] Proposal: Refactor ImageMosaic index management

[Simone Giannecchini]

Dear Devon,
a few things:

-0- we should really get rid of this CatalogManager as is (a class
with only static methods as its state its spread over N other classes)
-1- we can already mosaick images with different colormodels (to a
certain extent, it does not make sense to mosaick a float raster with
an RGB). RGB, Gray and Palette can be mosaicked as of today
-4- I would add some UML diagrams to your proposal to show what we
have now and what we have afterwards

I noticed that you are half-way through with your refactor and its
probably too early to look into it but I have two things I wanted to
bring up.
First of all, I believe you shuold look at the refactor of the
indexing together with this, I would not split them otherwise your
refactor in this case could be too narrow.
Let me explain, your goal here is to improve the harvesting process
allowing implementors to change how harvested elements are discarded
as well as how they are preprocessed or manipulated and this is not
isolated from the harvesting itself.

I believe catalogmanager (although) the nice name, might go away and
this kind of behavior could be isolated into smaller API likewise we
did with the properties collector so that one can drop them inside the
imagemosaic and ask it through the indexmanager to apply them.
Ideally one could rather write its one harvester and completely
customize how we put things inside the GranuleCatalog.

Let me know what you think about this.


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, Jun 14, 2016 at 8:09 PM, Devon Tucker  wrote:
> Hi all,
>
> After discussions about the ImageMosaic API proposal we have decided to
> break it up into a few smaller pieces that are hopefully both more
> manageable to implement and easier to understand. First up is a proposal to
> refactor the ImageMosaic CatalogManager to allow parts of it to be
> overridden. The first new proposal is here:
>
> https://github.com/geotools/geotools/wiki/Refactor-ImageMosaic-Index-and-Catalog-management-for-improved-extensibility
>
> I've been doing the work on my own branch here:
>
> https://github.com/dvntucker/geotools/tree/im_api_refactor
>
> Further to that, I have another branch where I've been storing R work done
> against that branch. Most of that work was done much earlier, but I've been
> porting my previous test cases to the new branch as I go along for
> verification purposes.
>
> Please take a look and let me know if there's anything that isn't clear.
> This proposal is much simpler than the previous one.
>
> Cheers
>
> --
> What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
> patterns at an interface-level. Reveals which users, apps, and protocols are
> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> J-Flow, sFlow 

[Geotools-devel] [JIRA] (GEOT-5440) Environment variables are not inherited by child threads

[Mauro Bartolomeoli (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mauro Bartolomeoli created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 GeoTools /  GEOT-5440  
 
 
  Environment variables are not inherited by child threads   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 15.0  
 
 
Assignee: 
 Mauro Bartolomeoli  
 
 
Components: 
 main  
 
 
Created: 
 15/Jun/16 2:01 PM  
 
 
Priority: 
  Medium  
 
 
Reporter: 
 Mauro Bartolomeoli  
 

  
 
 
 
 

 
 Environment variables are not inherited by child threads. This can make variables unavailable during rendering. See also: https://osgeo-org.atlassian.net/browse/GEOS-7579  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  

Re: [Geotools-devel] ImageMosaic API refactor proposal

[Simone Giannecchini]

I am not too fond on this name but as a general rule of thumb I always
suggest to refrain from the renaming attitude unless the original name
is _really_ bad.

This is also important as we would have in some cases to keep the old
one around if it was a public class or interface.
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, Jun 14, 2016 at 8:20 PM, Devon Tucker  wrote:
> Jody I'm not sure what a good name for the class is. Its chief
> responsibilities (before this proposal) were collecting attributes from the
> incoming granule, creating its new feature and updating the GranuleStore,
> creating the index schema, and instantiating the GranuleCatalog from the
> reader configuration. Now that I type all that out I don't think
> CatalogManager is that bad a name?
>
> On Tue, Jun 14, 2016 at 10:42 AM, Jody Garnett 
> wrote:
>>
>> I note the prior proposal had CatalogManager renamed to
>> GranuleCatalogManager is that still appropriate?
>>
>> Will you be removing the original proposal then?
>>
>> --
>> Jody Garnett
>>
>> On 9 June 2016 at 16:39, Devon Tucker  wrote:
>>>
>>> Thanks for all the feedback. Like Jody said, we're probably going to
>>> break the proposal apart a bit. I've started pulling apart the index/catalog
>>> management into its own proposal:
>>>
>>>
>>> https://github.com/geotools/geotools/wiki/Refactor-ImageMosaic-Index-Catalog-management-for-improved-extensibility
>>>
>>> Still a work in progress. Will work on adding code examples for the
>>> catalog manager part. In the meantime you can take a look at the WIP here:
>>>
>>> https://github.com/dvntucker/geotools/tree/im_api_refactor
>>>
>>> The biggest thing to note is that:
>>>
>>> - A number of methods in CatalogManager have been changed from static to
>>> non-static
>>> - CatalogManager has been added as a field to the
>>> ImageMosaicConfigHandler
>>> - Logic that was in ImageMosaicConfigHandler for checking ColorModel and
>>> CRS has been moved to CatalogManager (see the second part of the proposal)
>>>
>>> Cheers
>>>
>>> On Wed, Jun 8, 2016 at 1:08 PM, Jody Garnett 
>>> wrote:

 Thanks for email feedback Andrea, Daniele. Had a good chat with Simone
 

 Going to try and break this proposal into three small proposals on 1)
 index generation 2) dynamic processing 3) harvest flexibility.

 Some of the functionality (like data prep) is indeed already covered. I
 was not aware, for example, that geoserver importer could be used add
 granules to an existing mosaic (that is not functionality that can be done
 for vector import).

 --
 Jody Garnett

 On 5 April 2016 at 16:44, Devon Tucker  wrote:
>
> Hi all,
>
> Just noticed that there wasn't a dedicated email thread for this

Re: [Geotools-devel] Different time for next meeting?

[Simone Giannecchini]

Dear Ben,
I just sent a separate email for an overlapping topic.

On our side times between 10 a.m. and 7 p.m.CEST would work.
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, Jun 14, 2016 at 10:58 PM, Ben Caradoc-Davies  wrote:
> I will be unable to attend the next meeting, so Jody suggested that the next
> meeting might be scheduled for European working hours to give other PMC /
> PSC members a chance to attend at a more civilised local time.
>
> Europeans, any interest or preferred times?
>
> I am copying Ian, even though he might not be in Europe by then.  ;-)
>
> A different time slot might also work for Brad.
>
> Kind regards,
>
> --
> Ben Caradoc-Davies 
> Director
> Transient Software Limited 
> New Zealand

--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports. http://pubads.g.doubleclick.net/gampad/clk?id=1444514421=/41014381
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

[Geotools-devel] About PSC meeting times

[Simone Giannecchini]

Dear All,
First of all I apologize for the crossposting.

I wanted to discuss alternatives for PSC meetings in order to be able
to attend (and same goes for the other people on this side of the
world).

First thing first, there is no way to find a decent time that would
fit all the interested parties, we tried to find one and we failed.

The suggestion I have is as follows:

- rotate hours for the meetings, once we keep the current one, once we
change it to a time where it would fit for EU
- voting happens only on the mailing list
- in specific cases we can ask the PSC to participate to one of the meetings

This is of course suboptimal, but I believe it's a starter.
Looking forward to reading your feedback.

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.

--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports. http://pubads.g.doubleclick.net/gampad/clk?id=1444514421=/41014381
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel