Wow. Y'all did a lot of talking while I slept. :) Rather than try and participate in a discussion that's already passed me by, please allow me to briefly summarize some concerns which I feel need to be separated:
1] Data values and their organization into a matrix. (i.e. java.awt.image.Raster) 2] Portrayal (rendering) of data values. (i.e. java.awt.image.ColorModel) 3] Spatial Registration of gridded data (SpatialSensorModel; maps to EPSG proj.) 4] Calibration of data if geophysical (CalibrationSensorModel; yields units, applies transform) ISO 19123 defines the combination of 1&3 into an entity called a ReferencableGrid (complex) or RegisteredGrid (simple). #1 is merely a Grid. java.awt.image.RenderedImage represents the combination of 1, 2, and a little of 3. I know of no analog in the standards, proposed or otherwise. I sense opportunity to make a RenderedCoverage in Geotools, which may combine a Coverage with a ColorModel; Potentially backed by RenderedImage? ISO TC/211 is defining a suite of standard sensor models (e.g. "camera") and associated metadata for 3&4 (ISO 19130). If you "leave room" for 3&4, you may well have a system capable of displaying/processing satellite data products directly, without first resampling onto an EPSG-friendly grid. I know the MODIS fire algorithm will lose all scientific credibility if you "resample first." The point is, each of these concerns is separate. Independent. Unrelated to the others. I suspect we will run into problems very quickly if we collapse these independent concerns into a single Enumeration. Also, as to the matter of generic applications knowing what to do in the absense of metadata, I'd like to suggest that this is perhaps not relevant. GeoServer will only export layers which are manually configured, which includes the specification of applicable styles; in the end it is the responsibility of the website operator to know what data they are offering and how it is most appropriately displayed. Hence, GeoServer needs to be capable of *remembering* an intelligent decision, not *making* one. Udig is even more interactive and should allow users to have full control over how their data are rendered into eye candy. Remember: if you're not displaying it, you don't care how it should be displayed. :) Conversely, a "legend" for display may be generated whether or not the actual calibrated values are known. My $0.02 Bryce ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
