Hi Martin, Thanks for the info. Maybe the tradeoff is to be able to load a few EPGSs in memory for something like a Map process in Hadoop. 17-18MB seems small to me, maybe I am wrong... but a possible alternative is to load the data into a java datastructure that can be quickly loaded using a HashMap-like object where the key is the EPSG code.
On Fri, Aug 30, 2013 at 4:30 AM, Martin Desruisseaux <[email protected]> wrote: > Le 30/08/13 02:30, Travis L Pinney a écrit : > >> How large would the database be? > > > Hard to said, since it depends a lot on the internal of the database engine. > Looking on the space used on disk for EPSG 7.09, I have 17 Mb for Derby and > 18 Mb for HSQL. > > The EPSG database defines about 5000 referencing systems, but applications > will typically used only very few them, maybe 5. This is 0.1% of the > database content (problem is that everyone may use a different 0.1%). I > think it would be unfortunate to load such a big database in memory for > using only 0.1% of it, which is why a tend to prefer disk-based solution in > the particular case of EPSG. Of course, other kind of data would benefit > more from memory-based solution. > > Martin >
