Re: Accuracy with computing UTM from decimal degrees
Date: Fri, 29 Aug 2008 07:39:05 -0600
Thanks for the reply. This is on an 22.214.171.124 database. When I run the
same query on this version,
select cs_name,srid from mdsys.sdo_cs_srs where cs_name like 'NAD 27%17N%';
I get back 'NAD 27 / UTM zone 17N' and 2032617.
If I change the query to:
select cs_name,srid from mdsys.sdo_cs_srs where srid = 2032614;
Then I recieve 'NAD 27 / UTM zone 14N' and 2032614. So that's at least interesting to note the differences between the versions, for something that you'd think would be the same (though maybe some slight differences within the WKTEXT field). Right off hand, that looks like something that may bite a bunch of Spatial users in the butt when they upgrade to this version of Oracle.
The Oracle Forums finally came back up yesterday, and I was finally able to post the question over there as well, but so far no answers on there.
I'll give it a few more hours and see if somebody notices any glaring errors or something else before I try the SR route. It seems like if this is a real problem with the routines or internal code Oracle uses, somebody else would have noticed it by now, but who knows? This is primarily why I'm starting down the path that I coded something wrong first. I guess I'll also update that post on the forums as well with this new information, and see if maybe somebody will finally reply.
Thanks again for your reply.
- Bill Ferguson -- http://www.freelists.org/webpage/oracle-l