I looked at the epsg-h2 unsupported module and have an updated EPSG database I can provide.
One thing I've noticed which may be an issue for some programs is that H2 will not automatically upgrade the database (probably a good thing), but instead throws an "invalid database version exception". For a program like uDig which installs the epsg database locally and re-uses it, updating will cause these version exceptions to be thrown unless the local copy is removed & re-generated. Emily On 19/08/2011 7:04 AM, Andrea Aime wrote: > On Fri, Aug 19, 2011 at 12:20 AM, Justin Deoliveira > <[email protected]> wrote: >> Hi Emily, >> I am definitely +1 on upgrading h2. One of the somewhat problematic things >> is that there are a few different components around that have an h2 >> dependency. It sounds like you have tested all the geotools ones. For us in >> geoserver land there are some more dependencies as well. > > uDig is also using h2 as the epsg storage (epsg-h2 is in unsupported land). > I think GWC is also using h2 as the default metastore, and geoserver > for the superoverlays (and maybe as the default target for the db storage?). > > An upgrade would be good, but if h2 updates the db on disk there is no going > back, so it should be made on trunk only. > > Cheers > Andrea > ------------------------------------------------------------------------------ Get a FREE DOWNLOAD! and learn more about uberSVN rich system, user administration capabilities and model configuration. Take the hassle out of deploying and managing Subversion and the tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2 _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
