Hi, yesterday I tried to apply Emily's patch that would upgrade our EPSG database to version 6.18: http://jira.codehaus.org/browse/GEOT-2493
Unfortunately I found a few show stoppers, the EPSG database started using the degree symbol extensively in axis directions, that symbol cannot be represented in ASCII and HSQL 1.8 does not accept unicode escape codes (v1.9 does, but it's alpha). This results in quite a bit of test failures, but also whatever information is extracted from the db that uses non ASCII chars tends to be ruined. I was considering a move to H2, and pushing HSQL to unsupported land for 2.6, and then remove it completely in the next iteration of Geotools. H2 wise I think I would like to support both the current approach of "db in the temp dir" and a "db in the classpath". Both have value, the first is significantly faster and easier to implement, whilst the second is handier in that it does not require to touch the file system of the user. Opinions? I noticed GeoToolkit also ditched HSQL, but in favour of the Derby version that's shipping with the JDK. Opinions, preferences? I for one prefer H2, mostly because we're already using it extensively in GeoServer and GeoWebCache, and we have a JDBC datastore based on it. But that's just me, what do others prefer? Cheers Andrea -- Andrea Aime OpenGeo - http://opengeo.org Expert service straight from the developers. ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
