Ciao Jody, let me summarize as you did: 1>I absolutely agree. As Martin pointed out we should NEVER make any assumptions on the axes order but lawys inspect it int the data we are managing and behave coherently.
Having different CRS definitions in different authorities is of course a big problems since at that point, even if you do not tae any assumptions on how the data is organized, you might run into problems since the axis order itself could not match the data organization. Hence we need to have coherent CRS definitions at least in the same field of usage. 2>I agree, and especially for the first one it should be use to do that modifying a bit the OrderedAxisAuthorityFactory we already have. A not on hacks. I personally hate hacks and I really would love to tackle problems once for all and in a coherent way. This is why I started this discussion bugging everybody around. My opinion is that if we want to solve this issue we need to get everydoy who is interested to express his opinion in order to avoid using hacks! I am pretty sure that in the ends putting in place an initial solution will be simple, but again, we need to have everybody knows about the problem and the solution, otherwise nobody will exploit the solution itself. I hope I made my point clearly :-). SImone. On 5/20/06, Jody Garnett <[EMAIL PROTECTED]> wrote:
Jesse Eichar wrote: > Hi Simone, > > I'm in agreement that this issue needs to be resolved. The problem is > that I'm not 100% sure how to solve the problem. Do you have a > suggestion? I apologize if you have put you suggestion in this email, > I must have missed it. If I can be so bold, here is the solution I was aiming for: 1. trust the CRS to be correct when looking at features data or rendering etc... 2. allow the user to specify the CRS unambiguously - produce the two needed authority factories so they can do this: - "EPSG:4326" means "wms style", in the ordinate order ready to draw on the screen (x first, y second) - "http://www.opengis.net/gml/*srs*/*epsg*.xml/#4326"; means EPSG database style, in the ordinate order indicated in the EPSG database Please do not insert hacks through out the code base to cover up from what is really a specification error - make our library good and give users the tools they need to be explicit. Cheers, Jody
-- °°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°° Simone Giannecchini Software Engineer Freelance Consultant http://simboss.wordpress.com/ °°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°° ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642 _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
