Not having heard any feedback on this one I have gone ahead and submitted
the pull requests.
https://github.com/geotools/geotools/pull/687
https://github.com/geoserver/geoserver/pull/884
Thanks!
On Sun, Jan 11, 2015 at 11:23 AM, Justin Deoliveira
wrote:
> Here is my first cut at updating th
Here is my first cut at updating the database.
As per Andreas suggestion I also pulled out the change log for all the
versions. I took the liberty of doing some formatting of it.
https://gist.github.com/jdeolive/5e5c304dc741e0ebf24a
(I can make the script I used to generate it available if fol
Cool, thanks for the info guys. I'll work on this over the next few days to
try and get something in for the freeze.
On Thu, Jan 8, 2015 at 12:28 AM, Andrea Aime
wrote:
> On Thu, Jan 8, 2015 at 12:35 AM, Justin Deoliveira
> wrote:
>
>> Hey folks,
>>
>> I was curious as to what our current polic
On Thu, Jan 8, 2015 at 12:35 AM, Justin Deoliveira
wrote:
> Hey folks,
>
> I was curious as to what our current policy for upgrading the internal
> epsg database we ship? Does it just get done when somebody decides to do
> it? Or is there a schedule of some sort?
>
Yep, just like Jody said. The
It is just updated when someone decides to do it. If you are interested
please go ahead.
On Wed, Jan 7, 2015 at 3:36 PM Justin Deoliveira wrote:
> Hey folks,
>
> I was curious as to what our current policy for upgrading the internal
> epsg database we ship? Does it just get done when somebody dec
Hey folks,
I was curious as to what our current policy for upgrading the internal epsg
database we ship? Does it just get done when somebody decides to do it? Or
is there a schedule of some sort?
Anyways, I ask because I am interested in upgrading to the latest 8.6
version of the database. Do fol
