[EMAIL PROTECTED] wrote on 05/22/2006 05:18:00 PM:
> Openned a JIRA task > > http://jira.codehaus.org/browse/GEOT-854 > > > Comments welcome (especially any implication that may come to your mind). > > Martin. Done. Key points: 1] Addressing an encoding issue with an authority factory is now, and forever will be, a hack. Many hacks, actually. Everywhere in the code. 2] Distinguishing between reversed and correct encoding cannot be accomplished with software. This problem will never be solved programmatically. 3] GT should not be assuming _anything_ for the human who can _see_ that the axes are reversed. However, GT should make it easy for application writers to offer humans a minimum-effort way to adapt to well-understood broken data. 4] Address encoding issues with a polymorphic DataStore decorator which can substitute the incorrect CRS definition from the file with a correct definition of our choice. This constrains the modifications to a particular well defined class, forces application writers to take an action to "disbelieve" data, and makes it easy to do the "disbelieving" once it has been deemed necessary. All other modules, all other code, all other assumptions are specified according to ISO 19111/OGC Topic 2. 5] Invert #4 for writing broken data to be used with other broken (inferior) applications. ------------------------------------------------------- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
