Well I think it would be easy enough to add a entry to the user projections file that we ship with the data directory. We would have to add some notes to people upgrading though using a previous data dir, that they should update the file.
Another alternative might be to add the definition directly in code in during the initialization of the referencing sub system. Arne Kepp wrote: > //I am aware that a proper EPSG database upgrade hinges on a new db > engine for GeoTools etc etc...[1] > > But I am wondering whether we, in time for GS 2.0, should create an > alias (EPSG:3785) for EPSG:900913 ? > > Just so that we can update our docs with the correct code and not > encourage further use of EPSG:900913. > > -Arne > /// > 1: http://jira.codehaus.org/browse/GEOT-2493 > > / > -- Justin Deoliveira OpenGeo - http://opengeo.org Enterprise support for open source geospatial. ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
