[Geotools-devel] [JIRA] (GEOT-5423) Optimize vector rendering mode for dense hatches and large target geometries

2016-05-20 Thread Andrea Aime [Administrator] (JIRA)
Title: Message Title Andrea Aime [Administ

Re: [Geotools-devel] Copyright header policy

2016-05-20 Thread Justin Deoliveira
Thanks Ben. I am going to go ahead with this and update the proposal. Thanks for the input everyone. On Thu, May 19, 2016 at 5:19 PM Ben Caradoc-Davies wrote: > A fixed date might imply that this was the last time the file changed. > Could we write this to start with the file creation year but m

[Geotools-devel] Working with 16-bit sample models in geotools?

2016-05-20 Thread Rich Fecher
I had tracked an issue with GeoWave's implementation of AbstractGridFormat in which it seems the AbstractGridCoverage2DReader was storing and retrieving source images that had a single 16-bit band from landsat8 (so the data type for this sample model is unsigned short). The GridCoverage2D tiles th

Re: [Geotools-devel] Copyright header policy

2016-05-20 Thread Jody Garnett
I think I did that yesterday while waiting for a build. -- Jody Garnett On 20 May 2016 at 06:48, Justin Deoliveira wrote: > Thanks Ben. I am going to go ahead with this and update the proposal. > Thanks for the input everyone. > > On Thu, May 19, 2016 at 5:19 PM Ben Caradoc-Davies > wrote: > >

Re: [Geotools-devel] Copyright header policy

2016-05-20 Thread Jonathan Moules
I can see the appeal of having "2011-present" or similar, but I'm not sure it is valid. I believe the point of the date is to establish when a version was published for copyright law purposes. This means if a file isn't touched for several years, it will have an invalid publication date ("presen

Re: [Geotools-devel] Copyright header policy

2016-05-20 Thread Ben Caradoc-Davies
Many stackexchange comments on common law copyright and registration relate to the US prior its accession to the Berne convention (1989). Please see later comments and this: https://www.law.cornell.edu/wex/copyright Furthermore, and I am not a lawyer, can you copyright an individual source code

Re: [Geotools-devel] Copyright header policy

2016-05-20 Thread Justin Deoliveira
We keep on going in circles on this one. No OSGeo doesn’t have any rules to follow here, if they did we would be following them. If we want to “follow OSGeo rules” the best thing we can do is look at what the other established projects do. I looked at both MapServer and GDAL/OGR and they appear to

Re: [Geotools-devel] Copyright header policy

2016-05-20 Thread Ben Caradoc-Davies
Justin, I appreciate the work you have put into this one, especially your examination of other OSGeo projects, but in my view, copying the practices of other projects is another form of circling. Many of these practices trace their origin to the US pre-Berne. The first GPL licence was written

Re: [Geotools-devel] ImageMosaic API refactor proposal

2016-05-20 Thread Devon Tucker
Hi all, I've been working on fleshing this proposal out and adding a bit to it. See the conversation on on-the-fly reprojection in ImageMosaic. My updated API proposal is on my own Wiki for now, I can update the master one but I wanted to solicit early feedback. Please let me know if something doe

Re: [Geotools-devel] Copyright header policy

2016-05-20 Thread Jody Garnett
OSGeo is able to obtain legal advice, as PMC representative I can make that request on behalf of our project. As one of the early projects in OSGeo other projects will be following our lead. To close this one out I would be content to update our policy to be file creation/contribution date - and i

Re: [Geotools-devel] Copyright header policy

2016-05-20 Thread Ben Caradoc-Davies
Jody, I am happy to proceed with file creation/contribution date despite my small reservations. I think that file creation/contribution date is the option that has consensus at this time; it will solve the date maintenance overhead problem that is the reason for this change. I move that you as

Re: [Geotools-devel] Copyright header policy

2016-05-20 Thread Justin Deoliveira
While my personal preference is the same as yours Ben (going with no date in the header) I think this is the best middle ground. And anything that moves us away from the constant burden on committers and contributors to update the headers when it has no tangible benefit is a win. So what is still