> Here are the correct values for the transformed coordinates: > > This is what i get from decode which is correct > POINT(-92.20987681324226 34.048943723335704) --> POINT (572925.1581415016 > 3767864.3268143334) > > This is what i get from parseWKT which is incorrect > POINT(-92.20987681324226 34.048943723335704) --> POINT (1684114.104384322 > 3842326.483685698) > > Does anyone have any ideas for the discrepancy ?
The EPSG database has more information then is present in the WKT representation; and thus can be more accurate. It looks like your original point is very near the pole? I would also check the axis order as getting the two confused is sometimes a good source inaccuracy. Jody > -- > View this message in context: > http://n2.nabble.com/CRS-parseWKT-not-returning-same-values-as-CRS-decode-tp3569089p3569089.html > Sent from the geotools-gt2-users mailing list archive at Nabble.com. > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Geotools-gt2-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users > ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Geotools-gt2-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
