Hi guys, I agree with Bryce, the choice of WGS84 was due to convenience reasons since the vast amjority of time people I have talked to, uses it.
I hope Andrea will be able to give a hand with coverages since there are so many things to do in order to improve things (caching, overviews, better rendering) and so few people working on it. In case Andrea is not aware, me and a few other people, including bryce, are spending some (spare) time on the coverage branch to get coverage plugins and modules to a better shape (see http://svn.geotools.org/geotools/branches/coverages_branch/) but more help would be greatly appreciated, especially from guys with great experience on rasters. Simone. On 2/7/06, Bryce L Nordgren <[EMAIL PROTECTED]> wrote: > Hi. Sorry for the short note, but I'm just on my lunchbreak. Class > occupies a lot of time this week. > > ISO 19123 specifies an EngineeringCRS as the appropriate representation of > gridded data with no known georeferencing info, exactly as you propose. > It's not just a good idea, it's the law. ;) The only kicker is that > current GridCoverage stuff is not based off of 19123. > > The ISO19123 implementation (next week thru end of feb) is going to revamp > the current grid coverage spec. If you've got time, you're welcome to join > in. > > Bryce > > [EMAIL PROTECTED] wrote on 02/07/2006 08:42:54 AM: > > > Hi, > > I'm looking at the grid coverage readers, and found out that > > AbstractGridFormat > > defines WGS84 as the default crs. This is used by the WorldImagePlugin if > not > > .prj file is avaiable to define more precisely the grid coverage format. > > > > Now, this decision seems a little problematic to me. If we load a > coverage > > with wld file but no prj file, and the coverage happens to be in a > projected > > system (say, UTM), there is no correspondance between the grid > coordinates > > (which may be in the range of the millions of meters) and the crs (that > > uses -180/-180 -90/+90). > > > > It seems to me the most sensible choice for an unknown CRS is > > DefaultEngineeringCRS.CARTESIAN_2D, which has special handling to be > > a good default cartesian CRS (in particular, every transformation > > that involves > > it is an identity). > > > > Yet this change may break some of applications that rely on the current > > default. > > > > Opinions? > > Best regards > > Andrea Aime > > > > > > > > ------------------------------------------------------- > > This SF.net email is sponsored by: Splunk Inc. Do you grep through log > files > > for problems? Stop! Download the new AJAX search engine that makes > > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 > > _______________________________________________ > > Geotools-devel mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/geotools-devel > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 > _______________________________________________ > Geotools-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/geotools-devel > ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
