<div dir="ltr"><div><div><div>Hi again!<br><br></div>Hermann: thanks for your explanation.<br><br></div>José: yes. I tried with the <i>4326</i> epsg code using the api, but it stills gives me a different result than using cs2cs. Using cs2cs with 4326, gives a correct result, as expected.<br><br></div>Thanks and cheers!<br></div><div class="gmail_extra"><br><div class="gmail_quote">On 12 February 2015 at 13:22, Adri CS <span dir="ltr"><<a href="mailto:acsantome@gmail.com" target="_blank">acsantome@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Hi!<br><br></div><div>You're right, Hermann. The codes are different because I made a mistake when copy/pasting. The correct EPSG codes are the ones I use with the api: <i>32723 </i>for the source and <i>31983</i> for the target.<br><br></div><div>The input coordinates are from the Rodovida dos Tamoios. which falls in the UTM zone 23 S. Since they're in lat/long format, I just googled <i>"WGS84 utm 23s" </i>in Google and found <a href="http://www.spatialreference.org/ref/epsg/wgs-84-utm-zone-23s/" target="_blank">THIS</a>.<br><br></div><div>I'm using <i>"+init=epsg:32723 +proj=latlong"</i> beacuse I thought this would initialize the projPJ var with the SIRGAS 2000 system (ellipsoid and so.) and then, with the <i>latlong</i> string, I would made the system aware that the input coords will be in the lat/long form.<br><br></div><div>As you suggest, using <i>epsg:4326 </i>for the source system works fine. May I ask you what has this code of special?<br><br>/********************************************************************/<br><br></div><div>José, so supposing that I got the projection systems right (see Hermann's answer), should I expect this little differences due to rounding?<br></div><div><br></div>Thanks and cheers!<span class="HOEnZb"><font color="#888888"><br>Adri.<br></font></span></div>
</blockquote></div><br></div>