Re: [Geotools-devel] WFS-NG test work

[Ben Caradoc-Davies]

Thanks, Rob. Good to have you back!

Kind regards,
Ben.

On 19/03/15 10:18, Rob Atkinson wrote:
> Hey folks,
>
> I have been lurking watching Geoserver like a fond grandparent now for a
> long time, and now perhaps going to be in a position to use it in anger
> again, so started playing with the latest release.
>
> I just wanted to say how fabulous it is looking, (visually, technically and
> support wise) and how impressed I have been with the ongoing energy,
> commitment, and especially community-minded teamwork you guys have managed
> to sustain.
>
> +1 million.
>
> Rob Atkinson

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

--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] [Geoserver-devel] osgeo maven repo

[Jody Garnett]

That is how I have worked with a few teams - including LocationTech.

When we migrated to maven 2 a webdav folder was the 'best' way to set up a
public maven repository. We could as OSGeo to stand up a Nexus repository
(which may better handle scalability issues).

One part missing in this discussion is *how* to upload to maven central. We
were going to use CodeHaus but they have shut down. I updated the proposal
"tasks" to list this as a research step.

Reading the maven central docs it is clear a project *can* publish modified
artifacts into maven central (example gt-opengis is an older copy of
geoapi) but should do so under a distinct group id.

Compare:

  
org.geotools
gt-opengis
jar
  
  
org.opengis
geoapi
3.0.0
  

That said we have feedback on the user list that package overlap presents a
problem for integrators. Not strictly a maven central issue, more
respecting java package conventions.

I believe our jars that bundle OGC Schemas and EMF model would be fine.


  org.geotools.ogc
  net.opengis.fes
  jar


Even though the artifactId uses net.opengis.fes, the groupId clearly
indicates this is part of the geotools project.

--
Jody Garnett

On 18 March 2015 at 06:15, Chris Snider  wrote:

>  Hi,
>
>
>
> Not sure if my company business practice is relevant to other development
> groups, and is surely irrelevant to the single/home/hobbyist developer, but
> we use our own hosted maven nexus.  Company policy is to generate a
> settings.xml for new employees that point all maven requests at the company
> maven nexus.  When we need to pull jars from maven source other than maven
> central, we put a help desk ticket with local IT department and the
> appropriate links.  Usually within a couple hours we have access to those
> repositories.
>
>
>
> Chris Snider
>
> Senior Software Engineer
>
> *Intelligent Software Solutions, Inc.*
>
> [image: Description: Description: Description:
> cid:image001.png@01CA1F1F.CBC93990]
>
>
>
> *From:* Chris Bennight [mailto:ch...@slowcar.net]
> *Sent:* Tuesday, March 17, 2015 10:16 PM
> *To:* Ben Caradoc-Davies
> *Cc:* Geoserver-devel; Andrea Aime; Geotools-Devel list
> *Subject:* Re: [Geoserver-devel] [Geotools-devel] osgeo maven repo
>
>
>
> The motivation to get into maven central probably isn't so much a "how
> does this make geotools/geoserver we have right now immediately better" - I
> agree, there are some awkward hoops to jump through.
>
>
>
> I think the payout is longer term in making the artifacts easier to use
> and more accessible for the *non* geospatial community out there.  Someone
> who is working on another project and has a need for geospatial
> capabilities is (in my opinion) much more likely to show a preference for
> projects that are in maven central.
>
>
>
> Some of the projects we are looking to work with (spark, hadoop, hbase,
> etc.) are all pretty centralized around maven central.
>
>
>
> I totally agree that, in reality, it's not a huge issue to add another
> repo to the POM.  But at the same time, that initial cusp of getting
> peoples attention, getting them to spend time and come to understand a
> project, is lots of times made on quick decisions (what's already
> available, that I don't have to add repositories for etc.)
>
>  are looking for other libraries or projects;  absent anything better that's
> turns out to be a pretty significant criteria - but it's admittedly both
> anecdotal and an opinion>.
>
>
>
> Would it be fair to say there's three separate high level concerns going
> around here?
>
>
>
> (1) The impact on people who do the traditional clone/build  - with the
> caveat that the POM should just work without jumping through any hoops.
>
>
>
> (2) The extra overhead/maintenance required to deploy a "different"
> profile to maven central.
>
>
>
> (3) The overall viability (how I interpret Ben's point) - will we actually
> be able to move enough of the artifacts over to make people using maven
> central viable (because otherwise the whole effort is futile)
>
>
>
>
>
> 1 - I think this is a hard requirement (shouldn't break anything that
> already works), and here I believe Rich's intent (though correct me if I'm
> wrong) is to ensure that this is not impacted at all.  People should be
> able to clone and build from git exactly as they do now.
>
>
>
>
>
> 2 - I think it would turn into one extra deploy step (with a separate POM
> I believe).  The other overhead I can think of
>
> - Managing GPG keys for signing (might already be done)
>
> - Managing accounts with Sonatype, Bintray, or someone else  (typical way
> I'm familiar with;  leverging OSgeo there may be a way to mirror directly)
>
>
>
>
>
> 3 - I have to admit I'm not as familiar with this.  Are these things
> people need if they want to use geotools, write a geoserver plugin, or are
> these things needed for GeoServer integration/verification tests?  That
> said, as long as the group has redistribution rights I don't see any reason
> why those couldn

Re: [Geotools-devel] WFS-NG test work

[Rob Atkinson]

Hey folks,

I have been lurking watching Geoserver like a fond grandparent now for a
long time, and now perhaps going to be in a position to use it in anger
again, so started playing with the latest release.

I just wanted to say how fabulous it is looking, (visually, technically and
support wise) and how impressed I have been with the ongoing energy,
commitment, and especially community-minded teamwork you guys have managed
to sustain.

+1 million.

Rob Atkinson

On 19 March 2015 at 08:08, Jody Garnett  wrote:

> Managed to review, had a couple questions about ResourceInfo.getName()
> API. I am on IRC if you want to quickly blast through this...
>
> --
> Jody Garnett
>
> On 18 March 2015 at 13:47, Niels Charlier  wrote:
>
>>  Yeah definitely.
>>
>>
>> On 18-03-15 20:04, Jody Garnett wrote:
>>
>> Thanks Niels/Sampo - I had an action item to review the changes but did
>> not get to it.
>>
>>  I assume this change is of benefit to geoserver wfs cascade (and would
>> like to be included in the release?)
>>
>>--
>> Jody Garnett
>>
>> On 18 March 2015 at 08:18, Niels Charlier  wrote:
>>
>>>  Hello Sampo,
>>>
>>> Thank you for your review and your comments, I have responded to them.
>>>
>>> I hope we can push this commit through asap.
>>>
>>> Kind Regards
>>> Niels
>>>
>>>
>>> On 13-03-15 15:01, Sampo Savolainen wrote:
>>>
>>> Hi,
>>>
>>>  Sorry about the radio silence. I've been working on an unrelated big
>>> project and I haven't had a chance to focus on this. I agree that the
>>> testing in wfs-ng has not been up to spec and I appreciate your effort in
>>> getting that house in order. I had a quick look and found nothing really
>>> wrong with it but I didn't have a chance to actually try it out. Comments
>>> are in github.
>>>
>>>  Which version would this be included in? 13.1?
>>>
>>>
>>>   Sampo
>>>
>>> On Fri, Mar 13, 2015 at 11:54 AM, Niels Charlier 
>>> wrote:
>>>
 Sampo,

 Would you have the time to have a look at that? Or anyone else?

 Kind Regards
 Niels


 On 28-02-15 19:16, Niels Charlier wrote:

>  Hi,
>
> I have a new patch ready to improve the wfs-ng tests. All of this was
> done with the purpose of creating test cases for the new WFS 2.0
> functionality.
> I thought the test directory in wfs-ng was such a terrible mess it
> needed serious work first.
> A summary of what happened in this commit:
>
>1. Removed a bunch of duplicated test support reference data xml
> files,
>   and put all of them in one single directory structure instead of
> being spread around.
>2. WFFTestData and DataTestSupport were almost duplicates from each
> other,
>   removed the older one and converted all tests to use the newer
> one.
>3. There were two separate geoserveronlinetests, one for wfs1.0 and
> one for both wfs1.0 and wfs1.1
>made one abstract online test class and one derived test class
> per
> server/version combination.
>4. Enabled all of the disabled online test methods and made them
> work
> with the geoserver tests (release data dir).
>5. Enabled most of the disabled test methods in the integration test
> and made them work for the wfs1.1 geoserver
>   integration test case.
>6. Fixed issues with axis order implementation so the offline and
> online axis order tests work.
>7. Created a very clear package/directory structure for all tests so
> that you can very easily see
>   which server/wfs-version combinations have tests and which don't,
> offline and online.
>8. Renamed some confusing class names and removed unnecessary
> duplicated stuff
>   for example there was both a TestHttpClient and TestHTTPClient.
>9. Added pullparser test which tests the new parser (that works with
> GML3.2).
>
> TODO
>1. make online and offline WFS 2.0 tests. THis should now be rather
> easy with the existing abstract integration and online
>   test classes available which only require you to insert the right
> reference data info.
>2. verify the existing online tests for other servers than geoserver
>
> https://github.com/geotools/geotools/pull/757
>
> Regards
> Niels
>
>
> --
> Dive into the World of Parallel Programming The Go Parallel Website,
> sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub
> for all
> things parallel software development, from weekly thought leadership
> blogs to
> news, videos, case studies, tutorials and more. Take a look and join
> the
> conversation now. http://goparallel.sourceforge.net/
> ___
> GeoTools-Devel mailing list
> GeoTools-Devel@lists.sourceforge.net
>

Re: [Geotools-devel] [Geoserver-devel] osgeo maven repo

[Jody Garnett]

It is not really that important, the OGC intends for these schemas to be
distributed - it just there license is confusing and not clearly compatible
with open source (they ask for a different version number if you change it
or something sensible from a standards viewpoint).

OGC / Debian are working through it - I do not view it as a long term
concern. I even asked OSGeo to write a letter.

--
Jody Garnett

On 18 March 2015 at 02:15, Ian Turton  wrote:

> Seeing Ben's mention of the OGC schemas reminded me of a similar
> discussion on the osgeo-standards list where one of the linux distros
> (debian?) was rejecting Tiny OWS because of the license on the OGC schemas.
> I'll see if I can find the thread as it is probably relevant to this
> discussion too.
>
> Ian
>
> On Wed, Mar 18, 2015 at 5:50 AM Ben Caradoc-Davies 
> wrote:
>
>> The schema and refdataset jars are only used in GeoTools and GeoServer
>> tests. These artifacts are not deployed as part of a GeoTools or
>> GeoServer release and have version numbers governed elsewhere (plus a
>> packager suffix) and are unrelated to GeoTools release numbers.
>> Deployment is a manual process. I agree that migrating refdataset would
>> require cleaning up its governance; this would be a good thing.
>>
>> The refdataset SQL has been contributed to OSGeo. The provenance is
>> clean: origin was DPI Victoria (state of Australia), the only licence
>> requirement was mandatory modification. This was performed by Victor Tey
>> of CSIRO, the originator of refdataset and the corresponding tests in
>> GeoServer app-schema-test. CSIRO contributed this content as a corporate
>> osgeo contributor. The SQL *could* go into git, but *should* it? It is a
>> big chunk of data.
>>
>> The app-schema-packages artifacts are more problematic, and have IP
>> issues:
>> https://github.com/geotools/geotools/tree/master/modules/
>> extension/app-schema/app-schema-packages
>>
>> These poms build unmodified copies of public documents that are used
>> only for testing. I argue that this is a caching mechanism (but I am not
>> a lawyer). Most are OGC and IUGS-CGI schemas. These organisations are
>> all for interoperability; our use is testing our software for
>> compatibility with their schemas. However, an example IUGS-CGI copyright
>> statement is: "Copyright (c) Commission for the Management and
>> Application of Geoscience Information 2013. All rights reserved." These
>> documents are AFAICT incompatible with the LGPL. I do not see how we can
>> check these into git. The OGC licence is much more permissive.
>>
>> Some mention of the more ancient schemas here as well (app-schema IP
>> review):
>> http://jira.codehaus.org/browse/GEOT-3623
>>
>> See also (legality of caching content provided for free):
>> http://en.wikipedia.org/wiki/Field_v._Google,_Inc.
>> http://www.theregister.co.uk/2006/01/27/google_cache_
>> copyright_breach_ruling/
>>
>> Kind regards,
>> Ben.
>>
>> On 18/03/15 17:15, Chris Bennight wrote:
>> > 3 - I have to admit I'm not as familiar with this.  Are these things
>> people
>> > need if they want to use geotools, write a geoserver plugin, or are
>> these
>> > things needed for GeoServer integration/verification tests?  That said,
>> as
>> > long as the group has redistribution rights I don't see any reason why
>> > those couldn't be uploaded.  (Other than the work you mentioned that
>> would
>> > have to be done to pomify/version control the refdataset jar, which
>> could
>> > be added to this proposal)
>>
>> --
>> Ben Caradoc-Davies 
>> Director
>> Transient Software Limited 
>> New Zealand
>>
>> 
>> --
>> Dive into the World of Parallel Programming The Go Parallel Website,
>> sponsored
>> by Intel and developed in partnership with Slashdot Media, is your hub
>> for all
>> things parallel software development, from weekly thought leadership
>> blogs to
>> news, videos, case studies, tutorials and more. Take a look and join the
>> conversation now. http://goparallel.sourceforge.net/
>> ___
>> GeoTools-Devel mailing list
>> GeoTools-Devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>>
>
>
> --
> Dive into the World of Parallel Programming The Go Parallel Website,
> sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for
> all
> things parallel software development, from weekly thought leadership blogs
> to
> news, videos, case studies, tutorials and more. Take a look and join the
> conversation now. http://goparallel.sourceforge.net/
> ___
> GeoTools-Devel mailing list
> GeoTools-Devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>
>
--

Re: [Geotools-devel] WFS-NG test work

[Jody Garnett]

Managed to review, had a couple questions about ResourceInfo.getName() API.
I am on IRC if you want to quickly blast through this...

--
Jody Garnett

On 18 March 2015 at 13:47, Niels Charlier  wrote:

>  Yeah definitely.
>
>
> On 18-03-15 20:04, Jody Garnett wrote:
>
> Thanks Niels/Sampo - I had an action item to review the changes but did
> not get to it.
>
>  I assume this change is of benefit to geoserver wfs cascade (and would
> like to be included in the release?)
>
>--
> Jody Garnett
>
> On 18 March 2015 at 08:18, Niels Charlier  wrote:
>
>>  Hello Sampo,
>>
>> Thank you for your review and your comments, I have responded to them.
>>
>> I hope we can push this commit through asap.
>>
>> Kind Regards
>> Niels
>>
>>
>> On 13-03-15 15:01, Sampo Savolainen wrote:
>>
>> Hi,
>>
>>  Sorry about the radio silence. I've been working on an unrelated big
>> project and I haven't had a chance to focus on this. I agree that the
>> testing in wfs-ng has not been up to spec and I appreciate your effort in
>> getting that house in order. I had a quick look and found nothing really
>> wrong with it but I didn't have a chance to actually try it out. Comments
>> are in github.
>>
>>  Which version would this be included in? 13.1?
>>
>>
>>   Sampo
>>
>> On Fri, Mar 13, 2015 at 11:54 AM, Niels Charlier  wrote:
>>
>>> Sampo,
>>>
>>> Would you have the time to have a look at that? Or anyone else?
>>>
>>> Kind Regards
>>> Niels
>>>
>>>
>>> On 28-02-15 19:16, Niels Charlier wrote:
>>>
  Hi,

 I have a new patch ready to improve the wfs-ng tests. All of this was
 done with the purpose of creating test cases for the new WFS 2.0
 functionality.
 I thought the test directory in wfs-ng was such a terrible mess it
 needed serious work first.
 A summary of what happened in this commit:

1. Removed a bunch of duplicated test support reference data xml
 files,
   and put all of them in one single directory structure instead of
 being spread around.
2. WFFTestData and DataTestSupport were almost duplicates from each
 other,
   removed the older one and converted all tests to use the newer
 one.
3. There were two separate geoserveronlinetests, one for wfs1.0 and
 one for both wfs1.0 and wfs1.1
made one abstract online test class and one derived test class
 per
 server/version combination.
4. Enabled all of the disabled online test methods and made them work
 with the geoserver tests (release data dir).
5. Enabled most of the disabled test methods in the integration test
 and made them work for the wfs1.1 geoserver
   integration test case.
6. Fixed issues with axis order implementation so the offline and
 online axis order tests work.
7. Created a very clear package/directory structure for all tests so
 that you can very easily see
   which server/wfs-version combinations have tests and which don't,
 offline and online.
8. Renamed some confusing class names and removed unnecessary
 duplicated stuff
   for example there was both a TestHttpClient and TestHTTPClient.
9. Added pullparser test which tests the new parser (that works with
 GML3.2).

 TODO
1. make online and offline WFS 2.0 tests. THis should now be rather
 easy with the existing abstract integration and online
   test classes available which only require you to insert the right
 reference data info.
2. verify the existing online tests for other servers than geoserver

 https://github.com/geotools/geotools/pull/757

 Regards
 Niels


 --
 Dive into the World of Parallel Programming The Go Parallel Website,
 sponsored
 by Intel and developed in partnership with Slashdot Media, is your hub
 for all
 things parallel software development, from weekly thought leadership
 blogs to
 news, videos, case studies, tutorials and more. Take a look and join the
 conversation now. http://goparallel.sourceforge.net/
 ___
 GeoTools-Devel mailing list
 GeoTools-Devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/geotools-devel

>>>
>>>
>>
>>
>>  --
>>  Sampo Savolainen
>> R&D Director, Spatineo Oy
>> sampo.savolai...@spatineo.com
>> +358-407555649
>> Linnankoskenkatu 16 A 17, 00250 Helsinki, Finland
>> www.spatineo.com, twitter.com/#!/spatineo
>> 
>> www.linkedin.com/company/spatineo-inc
>>
>>  This message may contain privileged and/or confidential information. If
>> you
>> have received this e-mail in error or are not the intended recipient, you
>> may not use, copy, disseminate, or distribute it; do not open any
>> attachments, delete it immediately from your system and notify the

Re: [Geotools-devel] WFS-NG test work

[Niels Charlier]

Yeah definitely.

On 18-03-15 20:04, Jody Garnett wrote:
Thanks Niels/Sampo - I had an action item to review the changes but 
did not get to it.


I assume this change is of benefit to geoserver wfs cascade (and would 
like to be included in the release?)


--
Jody Garnett

On 18 March 2015 at 08:18, Niels Charlier > wrote:


Hello Sampo,

Thank you for your review and your comments, I have responded to them.

I hope we can push this commit through asap.

Kind Regards
Niels


On 13-03-15 15:01, Sampo Savolainen wrote:

Hi,

Sorry about the radio silence. I've been working on an unrelated
big project and I haven't had a chance to focus on this. I agree
that the testing in wfs-ng has not been up to spec and I
appreciate your effort in getting that house in order. I had a
quick look and found nothing really wrong with it but I didn't
have a chance to actually try it out. Comments are in github.

Which version would this be included in? 13.1?


 Sampo

On Fri, Mar 13, 2015 at 11:54 AM, Niels Charlier mailto:ni...@scitus.be>> wrote:

Sampo,

Would you have the time to have a look at that? Or anyone else?

Kind Regards
Niels


On 28-02-15 19:16, Niels Charlier wrote:

Hi,

I have a new patch ready to improve the wfs-ng tests. All
of this was
done with the purpose of creating test cases for the new
WFS 2.0
functionality.
I thought the test directory in wfs-ng was such a
terrible mess it
needed serious work first.
A summary of what happened in this commit:

   1. Removed a bunch of duplicated test support
reference data xml files,
  and put all of them in one single directory
structure instead of
being spread around.
   2. WFFTestData and DataTestSupport were almost
duplicates from each
other,
  removed the older one and converted all tests to
use the newer one.
   3. There were two separate geoserveronlinetests, one
for wfs1.0 and
one for both wfs1.0 and wfs1.1
   made one abstract online test class and one
derived test class per
server/version combination.
   4. Enabled all of the disabled online test methods and
made them work
with the geoserver tests (release data dir).
   5. Enabled most of the disabled test methods in the
integration test
and made them work for the wfs1.1 geoserver
  integration test case.
   6. Fixed issues with axis order implementation so the
offline and
online axis order tests work.
   7. Created a very clear package/directory structure
for all tests so
that you can very easily see
  which server/wfs-version combinations have tests
and which don't,
offline and online.
   8. Renamed some confusing class names and removed
unnecessary
duplicated stuff
  for example there was both a TestHttpClient and
TestHTTPClient.
   9. Added pullparser test which tests the new parser
(that works with
GML3.2).

TODO
   1. make online and offline WFS 2.0 tests. THis should
now be rather
easy with the existing abstract integration and online
  test classes available which only require you to
insert the right
reference data info.
   2. verify the existing online tests for other servers
than geoserver

https://github.com/geotools/geotools/pull/757

Regards
Niels


--
Dive into the World of Parallel Programming The Go
Parallel Website, sponsored
by Intel and developed in partnership with Slashdot
Media, is your hub for all
things parallel software development, from weekly thought
leadership blogs to
news, videos, case studies, tutorials and more. Take a
look and join the
conversation now. http://goparallel.sourceforge.net/
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/geotools-devel





-- 
Sampo Savolainen

R&D Director, Spatineo Oy
sampo.savolai...@spatineo.com 
  

Re: [Geotools-devel] Variable substitution for ColorMapEntry attributes

[Simone Giannecchini]

Ciao Mauro,
a couple of things:

-1- I would advise talking to Daniele about the Dynamic ColorMaps
-2- It would be good if we could take coverage statistics into account
somehow in order to have styles that adapt to the coverage dynamic
itself.

Let me know your toughts about this.

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

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
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 Wed, Mar 18, 2015 at 5:41 PM, Mauro Bartolomeoli
 wrote:
> Hi Andrea,
>
>>
>> Oh, but I see what you mean, you want to keep it as a string, and if it's
>> a string instead of a number,
>> do CQL parsing of it inside SLDColorMapBuilder.
>>
>> Hum... well, it's similar to what we did for the dynamic symbolizers, as
>> the sld syntax does not really
>> allow for a full ogc expression there anyways
>
>
> Yes, that's exactly my approach.
>
> Mauro
>
> --
> ==
> GeoServer Professional Services from the experts! Visit
> http://goo.gl/NWWaa2 for more information.
> ==
>
> Dott. Mauro Bartolomeoli
> @mauro_bart
> Senior Software Engineer
>
> GeoSolutions S.A.S.
> Via Poggio alle Viti 1187
> 55054  Massarosa (LU)
> Italy
> phone: +39 0584 962313
> fax: +39 0584 1660272
>
> http://www.geo-solutions.it
> http://twitter.com/geosolutions_it
>
> ---
>
> AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
>
> Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i
> file/s allegato/i sono da considerarsi strettamente riservate. Il loro
> utilizzo è consentito esclusivamente al destinatario del messaggio, per le
> finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio
> senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia
> via e-mail e di procedere alla distruzione del messaggio stesso,
> cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo
> anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per
> finalità diverse, costituisce comportamento contrario ai principi dettati
> dal D.Lgs. 196/2003.
>
>
>
> The information in this message and/or attachments, is intended solely for
> the attention and use of the named addressee(s) and may be confidential or
> proprietary in nature or covered by the provisions of privacy act
> (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
> Code).Any use not in accord with its purpose, any disclosure, reproduction,
> copying, distribution, or either dissemination, either whole or partial, is
> strictly forbidden except previous formal approval of the named
> addressee(s). If you are not the intended recipient, please contact
> immediately the sender by telephone, fax or e-mail and delete the
> information in this message that has been received in error. The sender does
> not give any warranty or accept liability as the content, accuracy or
> completeness of sent messages and accepts no responsibility  for changes
> made after they

Re: [Geotools-devel] WFS-NG test work

[Jody Garnett]

Thanks Niels/Sampo - I had an action item to review the changes but did not
get to it.

I assume this change is of benefit to geoserver wfs cascade (and would like
to be included in the release?)

--
Jody Garnett

On 18 March 2015 at 08:18, Niels Charlier  wrote:

>  Hello Sampo,
>
> Thank you for your review and your comments, I have responded to them.
>
> I hope we can push this commit through asap.
>
> Kind Regards
> Niels
>
>
> On 13-03-15 15:01, Sampo Savolainen wrote:
>
> Hi,
>
>  Sorry about the radio silence. I've been working on an unrelated big
> project and I haven't had a chance to focus on this. I agree that the
> testing in wfs-ng has not been up to spec and I appreciate your effort in
> getting that house in order. I had a quick look and found nothing really
> wrong with it but I didn't have a chance to actually try it out. Comments
> are in github.
>
>  Which version would this be included in? 13.1?
>
>
>   Sampo
>
> On Fri, Mar 13, 2015 at 11:54 AM, Niels Charlier  wrote:
>
>> Sampo,
>>
>> Would you have the time to have a look at that? Or anyone else?
>>
>> Kind Regards
>> Niels
>>
>>
>> On 28-02-15 19:16, Niels Charlier wrote:
>>
>>>  Hi,
>>>
>>> I have a new patch ready to improve the wfs-ng tests. All of this was
>>> done with the purpose of creating test cases for the new WFS 2.0
>>> functionality.
>>> I thought the test directory in wfs-ng was such a terrible mess it
>>> needed serious work first.
>>> A summary of what happened in this commit:
>>>
>>>1. Removed a bunch of duplicated test support reference data xml
>>> files,
>>>   and put all of them in one single directory structure instead of
>>> being spread around.
>>>2. WFFTestData and DataTestSupport were almost duplicates from each
>>> other,
>>>   removed the older one and converted all tests to use the newer one.
>>>3. There were two separate geoserveronlinetests, one for wfs1.0 and
>>> one for both wfs1.0 and wfs1.1
>>>made one abstract online test class and one derived test class per
>>> server/version combination.
>>>4. Enabled all of the disabled online test methods and made them work
>>> with the geoserver tests (release data dir).
>>>5. Enabled most of the disabled test methods in the integration test
>>> and made them work for the wfs1.1 geoserver
>>>   integration test case.
>>>6. Fixed issues with axis order implementation so the offline and
>>> online axis order tests work.
>>>7. Created a very clear package/directory structure for all tests so
>>> that you can very easily see
>>>   which server/wfs-version combinations have tests and which don't,
>>> offline and online.
>>>8. Renamed some confusing class names and removed unnecessary
>>> duplicated stuff
>>>   for example there was both a TestHttpClient and TestHTTPClient.
>>>9. Added pullparser test which tests the new parser (that works with
>>> GML3.2).
>>>
>>> TODO
>>>1. make online and offline WFS 2.0 tests. THis should now be rather
>>> easy with the existing abstract integration and online
>>>   test classes available which only require you to insert the right
>>> reference data info.
>>>2. verify the existing online tests for other servers than geoserver
>>>
>>> https://github.com/geotools/geotools/pull/757
>>>
>>> Regards
>>> Niels
>>>
>>>
>>> --
>>> Dive into the World of Parallel Programming The Go Parallel Website,
>>> sponsored
>>> by Intel and developed in partnership with Slashdot Media, is your hub
>>> for all
>>> things parallel software development, from weekly thought leadership
>>> blogs to
>>> news, videos, case studies, tutorials and more. Take a look and join the
>>> conversation now. http://goparallel.sourceforge.net/
>>> ___
>>> GeoTools-Devel mailing list
>>> GeoTools-Devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>>>
>>
>>
>
>
>  --
>  Sampo Savolainen
> R&D Director, Spatineo Oy
> sampo.savolai...@spatineo.com
> +358-407555649
> Linnankoskenkatu 16 A 17, 00250 Helsinki, Finland
> www.spatineo.com, twitter.com/#!/spatineo
> 
> www.linkedin.com/company/spatineo-inc
>
>  This message may contain privileged and/or confidential information. If
> you
> have received this e-mail in error or are not the intended recipient, you
> may not use, copy, disseminate, or distribute it; do not open any
> attachments, delete it immediately from your system and notify the sender
> promptly by e-mail that you have done so.
>
>
>
>
> --
> Dive into the World of Parallel Programming The Go Parallel Website,
> sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for
> all
> things parallel software development, from weekly thought leadership blogs
> to
> news, videos, case studies, tut

Re: [Geotools-devel] GeoTools 13 Release

[Jody Garnett]

Thanks Travis,

We have a blocker on the geoserver side (and a few pull requests highlight
on tuesdays meeting to get in). I will ping geotools-devel with the
revision when we get one out of cite tests.

So stay tuned ...
--
Jody

--
Jody Garnett

On 18 March 2015 at 09:45, Travis Brundage 
wrote:

> Hey all,
>
> I should have sent this out last week, but it looks like we have hit our
> GeoTools 13 release date. This will be the first stable release of GeoTools
> 13. Jody and I will be working together on getting this release out.
>
> Cheers,
> Travis
>
> --
> Travis Brundage
> Software Engineer | Boundless
> tbrund...@boundlessgeo.com
> 250.888.2820
> @boundlessgeo
>
>
>
> --
> Dive into the World of Parallel Programming The Go Parallel Website,
> sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for
> all
> things parallel software development, from weekly thought leadership blogs
> to
> news, videos, case studies, tutorials and more. Take a look and join the
> conversation now. http://goparallel.sourceforge.net/
> ___
> GeoTools-Devel mailing list
> GeoTools-Devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>
>
--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

[Geotools-devel] GeoTools 13 Release

[Travis Brundage]

Hey all,

I should have sent this out last week, but it looks like we have hit our
GeoTools 13 release date. This will be the first stable release of GeoTools
13. Jody and I will be working together on getting this release out.

Cheers,
Travis

-- 
Travis Brundage
Software Engineer | Boundless
tbrund...@boundlessgeo.com
250.888.2820
@boundlessgeo
--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] Variable substitution for ColorMapEntry attributes

[Mauro Bartolomeoli]

Hi Andrea,


> Oh, but I see what you mean, you want to keep it as a string, and if it's
> a string instead of a number,
> do CQL parsing of it inside SLDColorMapBuilder.
>
> Hum... well, it's similar to what we did for the dynamic symbolizers, as
> the sld syntax does not really
> allow for a full ogc expression there anyways
>

Yes, that's exactly my approach.

Mauro

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

Dott. Mauro Bartolomeoli
@mauro_bart
Senior Software Engineer

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054  Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272

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

---

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

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



The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility  for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.
--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] Variable substitution for ColorMapEntry attributes

[Andrea Aime]

On Wed, Mar 18, 2015 at 4:05 PM, Mauro Bartolomeoli <
mauro.bartolome...@geo-solutions.it> wrote:

> Hi,
>
>>
>>> Seems to be it's well aligned with other changes we made in the past
>> where OGC restrictions were lifted/relaxed to that
>> we could use expression instead of Literal or PropertyName.
>> I beleive this is going to break the raster symbolizer interfaces
>> (backwards incompatible change), can you confirm?
>>
>
> No, I don't think it's needed, I am only going to change the
> SLDColorMapBuilder class, where it's extracting the attribute values, to
> enable recognition / parsing / evaluation of an eventual cql filter.
>
>
Oh ok, se ColorMapEntry already supports expression for Quantity but we
are parsing it as a literal, e.g., from the sldparser:

if (atts.getNamedItem(colorMapQuantityString) != null) {
symbol

.setQuantity(ff.literal(atts.getNamedItem(colorMapQuantityString)
.getNodeValue()));
}

Oh, but I see what you mean, you want to keep it as a string, and if it's a
string instead of a number,
do CQL parsing of it inside SLDColorMapBuilder.

Hum... well, it's similar to what we did for the dynamic symbolizers, as
the sld syntax does not really
allow for a full ogc expression there anyways

Cheers
Andrea

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

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054  Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39  339 8844549

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

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

Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi 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.

---
--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

[Geotools-devel] [jira] (GEOT-5055) Expose DecimantionPolicy parameter and allows for additional values

[Daniele Romagnoli (JIRA)]

Title: Message Title










 

 Daniele Romagnoli created an issue











 






 GeoTools /  GEOT-5055



  Expose DecimantionPolicy parameter and allows for additional values 










Issue Type:

  Improvement




Affects Versions:


 14-beta




Assignee:

 Simone Giannecchini




Components:


 coverage




Created:


 18/Mar/15 10:37 AM




Priority:

  Minor




Reporter:

 Daniele Romagnoli










When rendering data on clients such as OpenLayers, imageProcessing operations are performed to fit the requested windows with data coming from the underlying datasets. You may think about having a huge dataset with a resolution of 50cm and the current rendering is asking for data at 1 km.  When overviews have been properly computed as part of preprocessing before configuring the layers, the rendering results are visually good. 
When overviews are unavailable, the default logic does a huge subsampling (skip pixels when reading data from disk) before applying the final scaling. The quality of the output isn't good in that case, the rendering is very pixellated.
We should expose the imageMosaic DecimationPolicy parameter in the configuration layer as well as add some more values to that enum and update the decimation code accordingly.
This will allow to do less aggressive subsampling in order to get better quality results.


 

Re: [Geotools-devel] WFS-NG test work

[Niels Charlier]

Hello Sampo,

Thank you for your review and your comments, I have responded to them.

I hope we can push this commit through asap.

Kind Regards
Niels

On 13-03-15 15:01, Sampo Savolainen wrote:

Hi,

Sorry about the radio silence. I've been working on an unrelated big 
project and I haven't had a chance to focus on this. I agree that the 
testing in wfs-ng has not been up to spec and I appreciate your effort 
in getting that house in order. I had a quick look and found nothing 
really wrong with it but I didn't have a chance to actually try it 
out. Comments are in github.


Which version would this be included in? 13.1?


 Sampo

On Fri, Mar 13, 2015 at 11:54 AM, Niels Charlier > wrote:


Sampo,

Would you have the time to have a look at that? Or anyone else?

Kind Regards
Niels


On 28-02-15 19:16, Niels Charlier wrote:

Hi,

I have a new patch ready to improve the wfs-ng tests. All of
this was
done with the purpose of creating test cases for the new WFS 2.0
functionality.
I thought the test directory in wfs-ng was such a terrible mess it
needed serious work first.
A summary of what happened in this commit:

   1. Removed a bunch of duplicated test support reference
data xml files,
  and put all of them in one single directory structure
instead of
being spread around.
   2. WFFTestData and DataTestSupport were almost duplicates
from each
other,
  removed the older one and converted all tests to use the
newer one.
   3. There were two separate geoserveronlinetests, one for
wfs1.0 and
one for both wfs1.0 and wfs1.1
   made one abstract online test class and one derived
test class per
server/version combination.
   4. Enabled all of the disabled online test methods and made
them work
with the geoserver tests (release data dir).
   5. Enabled most of the disabled test methods in the
integration test
and made them work for the wfs1.1 geoserver
  integration test case.
   6. Fixed issues with axis order implementation so the
offline and
online axis order tests work.
   7. Created a very clear package/directory structure for all
tests so
that you can very easily see
  which server/wfs-version combinations have tests and
which don't,
offline and online.
   8. Renamed some confusing class names and removed unnecessary
duplicated stuff
  for example there was both a TestHttpClient and
TestHTTPClient.
   9. Added pullparser test which tests the new parser (that
works with
GML3.2).

TODO
   1. make online and offline WFS 2.0 tests. THis should now
be rather
easy with the existing abstract integration and online
  test classes available which only require you to insert
the right
reference data info.
   2. verify the existing online tests for other servers than
geoserver

https://github.com/geotools/geotools/pull/757

Regards
Niels


--
Dive into the World of Parallel Programming The Go Parallel
Website, sponsored
by Intel and developed in partnership with Slashdot Media, is
your hub for all
things parallel software development, from weekly thought
leadership blogs to
news, videos, case studies, tutorials and more. Take a look
and join the
conversation now. http://goparallel.sourceforge.net/
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/geotools-devel





--
Sampo Savolainen
R&D Director, Spatineo Oy
sampo.savolai...@spatineo.com 
+358-407555649
Linnankoskenkatu 16 A 17, 00250 Helsinki, Finland
www.spatineo.com , twitter.com/#!/spatineo 

www.linkedin.com/company/spatineo-inc 



This message may contain privileged and/or confidential information. 
If you

have received this e-mail in error or are not the intended recipient, you
may not use, copy, disseminate, or distribute it; do not open any
attachments, delete it immediately from your system and notify the sender
promptly by e-mail that you have done so.


--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in part

[Geotools-devel] [jira] (GEOT-5054) Error painting LegendGraphic with negative scale

[Steve Ikeoka (JIRA)]

Title: Message Title










 

 Steve Ikeoka created an issue











 






 GeoTools /  GEOT-5054



  Error painting LegendGraphic with negative scale 










Issue Type:

  Bug




Affects Versions:


 13-RC1, 12.2




Assignee:

 Andrea Aime




Attachments:


 paint_legend_graphic_negative_scale.patch




Components:


 render




Created:


 18/Mar/15 10:15 AM




Priority:

  Major




Reporter:

 Steve Ikeoka










Calling StyleShapePainter.paint for an SLD LegendGraphic element with a negative scale will result in an IllegalArgumentException. This is a problem because GeoServer GetLegendGraphic requests use -1 as the default scale.
A patch with a junit test is attached.
Stack Trace:
java.lang.IllegalArgumentException: Width (-20) and height (-20) must be > 0 at java.awt.image.SampleModel.(SampleModel.java:126) [rt.jar:1.7.0_72] at java.awt.image.ComponentSampleModel.(ComponentSampleModel.java:146) [rt.jar:1.7.0_72] at java.awt.image.PixelInterleavedSampleModel.(PixelInterleavedSampleModel.java:87) [rt.jar:1.7.0_72] at java.awt.image.Raster.createInterleavedRaster(Raster.java:641) [rt.jar:1.7.0_72] at j

Re: [Geotools-devel] Variable substitution for ColorMapEntry attributes

[Mauro Bartolomeoli]

Hi,

>
>> Seems to be it's well aligned with other changes we made in the past
> where OGC restrictions were lifted/relaxed to that
> we could use expression instead of Literal or PropertyName.
> I beleive this is going to break the raster symbolizer interfaces
> (backwards incompatible change), can you confirm?
>

No, I don't think it's needed, I am only going to change the
SLDColorMapBuilder class, where it's extracting the attribute values, to
enable recognition / parsing / evaluation of an eventual cql filter.

After that I am going to do a similar change to support this syntax for
GetLegendGraphic calls.

Thanks
Mauro



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

Dott. Mauro Bartolomeoli
@mauro_bart
Senior Software Engineer

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054  Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272

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

---

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

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



The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility  for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.
--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] Variable substitution for ColorMapEntry attributes

[Andrea Aime]

On Wed, Mar 18, 2015 at 1:46 PM, Mauro Bartolomeoli <
mauro.bartolome...@geo-solutions.it> wrote:

> Hi,
> I would like to introduce the possibility to use CQL expressions to
> specify the value of some attributes of ColorMapEntry SLD tags in raster
> symbolizers.
> My purpose is to be able to use values from WMS requests (specifically
> variables in the ENV parameter) to dynamically specify those entries
> attributes in each request.
>
> I would use the already used ${...expression...} syntax for expressions:
>
> An example:
>
> 
>  opacity="0"/>
>  opacity="1"/>
>  label="Medium" opacity="1"/>
>  label="High" opacity="1"/>
> 
>
> In the WMS request I would specify the env parameter as:
>
> env=low:10;medium:100;high:1000
>
> For my use case, the expression support is needed only for the quantity
> attribute, but since I am working on it, I would extend it to all the
> ColorMapEntry attributes, for completeness.
>
> What do you think?
>
>
Seems to be it's well aligned with other changes we made in the past where
OGC restrictions were lifted/relaxed to that
we could use expression instead of Literal or PropertyName.
I beleive this is going to break the raster symbolizer interfaces
(backwards incompatible change), can you confirm?
If so we need a proposal

Cheers
Andrea

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

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054  Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39  339 8844549

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

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

Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi 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.

---
--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

[Geotools-devel] [jira] (GEOT-5053) FeatureTypeStyleImpl copying constructor does not copy some properties

[Mauro Bartolomeoli (JIRA)]

Title: Message Title










 

 Mauro Bartolomeoli created an issue











 






 GeoTools /  GEOT-5053



  FeatureTypeStyleImpl copying constructor does not copy some properties 










Issue Type:

  Bug




Affects Versions:


 13-RC1




Assignee:

 Jody Garnett




Components:


 main




Created:


 18/Mar/15 8:14 AM




Priority:

  Minor




Reporter:

 Mauro Bartolomeoli










Transformation and OnlineResource are not copied.












   

 Add Comment











 





   

[Geotools-devel] Variable substitution for ColorMapEntry attributes

[Mauro Bartolomeoli]

Hi,
I would like to introduce the possibility to use CQL expressions to specify
the value of some attributes of ColorMapEntry SLD tags in raster
symbolizers.
My purpose is to be able to use values from WMS requests (specifically
variables in the ENV parameter) to dynamically specify those entries
attributes in each request.

I would use the already used ${...expression...} syntax for expressions:

An example:








In the WMS request I would specify the env parameter as:

env=low:10;medium:100;high:1000

For my use case, the expression support is needed only for the quantity
attribute, but since I am working on it, I would extend it to all the
ColorMapEntry attributes, for completeness.

What do you think?

Regards,
Mauro

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

Dott. Mauro Bartolomeoli
@mauro_bart
Senior Software Engineer

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054  Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272

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

---

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

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



The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility  for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.
--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

[Geotools-devel] [jira] (GEOT-5052) Add CQL expressions support in ColorMap entry attributes (quantity, color, ...)

[Mauro Bartolomeoli (JIRA)]

Title: Message Title










 

 Mauro Bartolomeoli created an issue











 






 GeoTools /  GEOT-5052



  Add CQL expressions support in ColorMap entry attributes (quantity, color, ...) 










Issue Type:

  Improvement




Assignee:

 Mauro Bartolomeoli




Components:


 render




Created:


 18/Mar/15 7:37 AM




Fix Versions:


 14-beta




Priority:

  Minor




Reporter:

 Mauro Bartolomeoli










The requirement here is to be able to dynamically set ColorMap entries properties such as color, quantity, etc. using env variables specified in the request.












   

 Add Comment

Re: [Geotools-devel] [Geoserver-devel] osgeo maven repo

[Ian Turton]

Here's the links: Apparently Jody started it with
http://www.how2map.com/2015/02/a-good-test-for-ogc-and-osgeo.html and then
discussion followed here
http://lists.osgeo.org/pipermail/standards/2015-February/000834.html

Ian

On Wed, Mar 18, 2015 at 9:16 AM Ian Turton  wrote:

> Seeing Ben's mention of the OGC schemas reminded me of a similar
> discussion on the osgeo-standards list where one of the linux distros
> (debian?) was rejecting Tiny OWS because of the license on the OGC schemas.
> I'll see if I can find the thread as it is probably relevant to this
> discussion too.
>
>
> Ian
>
> On Wed, Mar 18, 2015 at 5:50 AM Ben Caradoc-Davies 
> wrote:
>
>> The schema and refdataset jars are only used in GeoTools and GeoServer
>> tests. These artifacts are not deployed as part of a GeoTools or
>> GeoServer release and have version numbers governed elsewhere (plus a
>> packager suffix) and are unrelated to GeoTools release numbers.
>> Deployment is a manual process. I agree that migrating refdataset would
>> require cleaning up its governance; this would be a good thing.
>>
>> The refdataset SQL has been contributed to OSGeo. The provenance is
>> clean: origin was DPI Victoria (state of Australia), the only licence
>> requirement was mandatory modification. This was performed by Victor Tey
>> of CSIRO, the originator of refdataset and the corresponding tests in
>> GeoServer app-schema-test. CSIRO contributed this content as a corporate
>> osgeo contributor. The SQL *could* go into git, but *should* it? It is a
>> big chunk of data.
>>
>> The app-schema-packages artifacts are more problematic, and have IP
>> issues:
>> https://github.com/geotools/geotools/tree/master/modules/ext
>> ension/app-schema/app-schema-packages
>>
>> These poms build unmodified copies of public documents that are used
>> only for testing. I argue that this is a caching mechanism (but I am not
>> a lawyer). Most are OGC and IUGS-CGI schemas. These organisations are
>> all for interoperability; our use is testing our software for
>> compatibility with their schemas. However, an example IUGS-CGI copyright
>> statement is: "Copyright (c) Commission for the Management and
>> Application of Geoscience Information 2013. All rights reserved." These
>> documents are AFAICT incompatible with the LGPL. I do not see how we can
>> check these into git. The OGC licence is much more permissive.
>>
>> Some mention of the more ancient schemas here as well (app-schema IP
>> review):
>> http://jira.codehaus.org/browse/GEOT-3623
>>
>> See also (legality of caching content provided for free):
>> http://en.wikipedia.org/wiki/Field_v._Google,_Inc.
>> http://www.theregister.co.uk/2006/01/27/google_cache_copyrig
>> ht_breach_ruling/
>>
>> Kind regards,
>> Ben.
>>
>> On 18/03/15 17:15, Chris Bennight wrote:
>> > 3 - I have to admit I'm not as familiar with this.  Are these things
>> people
>> > need if they want to use geotools, write a geoserver plugin, or are
>> these
>> > things needed for GeoServer integration/verification tests?  That said,
>> as
>> > long as the group has redistribution rights I don't see any reason why
>> > those couldn't be uploaded.  (Other than the work you mentioned that
>> would
>> > have to be done to pomify/version control the refdataset jar, which
>> could
>> > be added to this proposal)
>>
>> --
>> Ben Caradoc-Davies 
>> Director
>> Transient Software Limited 
>> New Zealand
>>
>> 
>> --
>> Dive into the World of Parallel Programming The Go Parallel Website,
>> sponsored
>> by Intel and developed in partnership with Slashdot Media, is your hub
>> for all
>> things parallel software development, from weekly thought leadership
>> blogs to
>> news, videos, case studies, tutorials and more. Take a look and join the
>> conversation now. http://goparallel.sourceforge.net/
>> ___
>> GeoTools-Devel mailing list
>> GeoTools-Devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>>
>
--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] [Geoserver-devel] osgeo maven repo

[Ian Turton]

Seeing Ben's mention of the OGC schemas reminded me of a similar discussion
on the osgeo-standards list where one of the linux distros (debian?) was
rejecting Tiny OWS because of the license on the OGC schemas. I'll see if I
can find the thread as it is probably relevant to this discussion too.

Ian

On Wed, Mar 18, 2015 at 5:50 AM Ben Caradoc-Davies  wrote:

> The schema and refdataset jars are only used in GeoTools and GeoServer
> tests. These artifacts are not deployed as part of a GeoTools or
> GeoServer release and have version numbers governed elsewhere (plus a
> packager suffix) and are unrelated to GeoTools release numbers.
> Deployment is a manual process. I agree that migrating refdataset would
> require cleaning up its governance; this would be a good thing.
>
> The refdataset SQL has been contributed to OSGeo. The provenance is
> clean: origin was DPI Victoria (state of Australia), the only licence
> requirement was mandatory modification. This was performed by Victor Tey
> of CSIRO, the originator of refdataset and the corresponding tests in
> GeoServer app-schema-test. CSIRO contributed this content as a corporate
> osgeo contributor. The SQL *could* go into git, but *should* it? It is a
> big chunk of data.
>
> The app-schema-packages artifacts are more problematic, and have IP issues:
> https://github.com/geotools/geotools/tree/master/modules/
> extension/app-schema/app-schema-packages
>
> These poms build unmodified copies of public documents that are used
> only for testing. I argue that this is a caching mechanism (but I am not
> a lawyer). Most are OGC and IUGS-CGI schemas. These organisations are
> all for interoperability; our use is testing our software for
> compatibility with their schemas. However, an example IUGS-CGI copyright
> statement is: "Copyright (c) Commission for the Management and
> Application of Geoscience Information 2013. All rights reserved." These
> documents are AFAICT incompatible with the LGPL. I do not see how we can
> check these into git. The OGC licence is much more permissive.
>
> Some mention of the more ancient schemas here as well (app-schema IP
> review):
> http://jira.codehaus.org/browse/GEOT-3623
>
> See also (legality of caching content provided for free):
> http://en.wikipedia.org/wiki/Field_v._Google,_Inc.
> http://www.theregister.co.uk/2006/01/27/google_cache_
> copyright_breach_ruling/
>
> Kind regards,
> Ben.
>
> On 18/03/15 17:15, Chris Bennight wrote:
> > 3 - I have to admit I'm not as familiar with this.  Are these things
> people
> > need if they want to use geotools, write a geoserver plugin, or are these
> > things needed for GeoServer integration/verification tests?  That said,
> as
> > long as the group has redistribution rights I don't see any reason why
> > those couldn't be uploaded.  (Other than the work you mentioned that
> would
> > have to be done to pomify/version control the refdataset jar, which could
> > be added to this proposal)
>
> --
> Ben Caradoc-Davies 
> Director
> Transient Software Limited 
> New Zealand
>
> 
> --
> Dive into the World of Parallel Programming The Go Parallel Website,
> sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for
> all
> things parallel software development, from weekly thought leadership blogs
> to
> news, videos, case studies, tutorials and more. Take a look and join the
> conversation now. http://goparallel.sourceforge.net/
> ___
> GeoTools-Devel mailing list
> GeoTools-Devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>
--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] motion: move wiki to github

[Simone Giannecchini]

+1

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

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
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 Wed, Mar 18, 2015 at 8:41 AM, Christian Mueller
 wrote:
> +1
>
> Christian
>
> On Tue, Mar 17, 2015 at 7:19 PM, Ian Turton  wrote:
>>
>> +1
>>
>>
>> On 17:38, Tue, 17 Mar 2015 Andrea Aime 
>> wrote:
>>>
>>> On Tue, Mar 17, 2015 at 6:31 PM, Jody Garnett 
>>> wrote:

 With CodeHaus being shut down I would like to formally move our wiki to
 github.
>>>
>>>
>>> +1
>>>
>>> Cheers
>>> Andrea
>>>
>>> --
>>> ==
>>> GeoServer Professional Services from the experts! Visit
>>> http://goo.gl/NWWaa2 for more information.
>>> ==
>>>
>>> Ing. Andrea Aime
>>> @geowolf
>>> Technical Lead
>>>
>>> GeoSolutions S.A.S.
>>> Via Poggio alle Viti 1187
>>> 55054  Massarosa (LU)
>>> Italy
>>> phone: +39 0584 962313
>>> fax: +39 0584 1660272
>>> mob: +39  339 8844549
>>>
>>> http://www.geo-solutions.it
>>> http://twitter.com/geosolutions_it
>>>
>>> AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
>>>
>>> Le informazioni contenute in questo messaggio di posta elettronica e/o
>>> nel/i file/s allegato/i sono da considerarsi 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.
>>>
>>>
>>> ---
>>>
>>> --
>>> Dive into the World of Parallel 

Re: [Geotools-devel] motion: move wiki to github

[Christian Mueller]

+1

Christian

On Tue, Mar 17, 2015 at 7:19 PM, Ian Turton  wrote:

> +1
>
> On 17:38, Tue, 17 Mar 2015 Andrea Aime 
> wrote:
>
>> On Tue, Mar 17, 2015 at 6:31 PM, Jody Garnett 
>> wrote:
>>
>>> With CodeHaus being shut down I would like to formally move our wiki to
>>> github.
>>>
>>
>> +1
>>
>> Cheers
>> Andrea
>>
>> --
>> ==
>> GeoServer Professional Services from the experts! Visit
>> http://goo.gl/NWWaa2 for more information.
>> ==
>>
>> Ing. Andrea Aime
>> @geowolf
>> Technical Lead
>>
>> GeoSolutions S.A.S.
>> Via Poggio alle Viti 1187
>> 55054  Massarosa (LU)
>> Italy
>> phone: +39 0584 962313
>> fax: +39 0584 1660272
>> mob: +39  339 8844549
>>
>> http://www.geo-solutions.it
>> http://twitter.com/geosolutions_it
>>
>> *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*
>>
>> Le informazioni contenute in questo messaggio di posta elettronica e/o
>> nel/i file/s allegato/i sono da considerarsi 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.
>>
>> ---
>>  
>> --
>> Dive into the World of Parallel Programming The Go Parallel Website,
>> sponsored
>> by Intel and developed in partnership with Slashdot Media, is your hub
>> for all
>> things parallel software development, from weekly thought leadership
>> blogs to
>> news, videos, case studies, tutorials and more. Take a look and join the
>> conversation now. http://goparallel.sourceforge.net/
>> ___
>> GeoTools-Devel mailing list
>> GeoTools-Devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>>
>
>
> --
> Dive into the World of Parallel Programming The Go Parallel Website,
> sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for
> all
> things parallel software development, from weekly thought leadership blogs
> to
> news, videos, case studies, tutorials and more. Take a look and join the
> conversation now. http://goparallel.sourceforge.net/
> ___
> GeoTools-Devel mailing list
> GeoTools-Devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>
>


-- 
DI Christian Mueller MSc (GIS), MSc (IT-Security)
OSS Open Source Solutions GmbH
--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel