marek-sezemsky / coreemu

Automatically exported from code.google.com/p/coreemu
BSD 2-Clause "Simplified" License
0 stars 0 forks source link

incorrect distance with received EMANE location events #196

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Report from user:
location event NEM 1 (46.9038622222, -71.2007911111, 9144) -> (118, 92, 18)
location event NEM 2 (46.7335377778, -64.8892266667, 9144) -> (164, 131, 18)

The distance between longitudes (x coord) should be 480 km

The canvas setting is 100 pixels = 50,000 meters (or 1 pixel = 500 meters)

480 km should be 960 pixel difference on x axis but showing as 46

Using Python 2.6, EMANE 0.8.1, and a recent version of the CORE SVN snapshot.

Original issue reported on code.google.com by ahrenh...@gmail.com on 27 Mar 2013 at 7:52

GoogleCodeExporter commented 9 years ago
problem occurs when traversing UTM zones

the zone information is discarded by CORE -- only the reference point zone is 
considered

Original comment by ahrenh...@gmail.com on 29 Mar 2013 at 5:55

GoogleCodeExporter commented 9 years ago

Original comment by ahrenh...@gmail.com on 2 Apr 2013 at 8:31

GoogleCodeExporter commented 9 years ago
fixed in r835

- use utm 0.3.0 library from https://pypi.python.org/pypi/utm
  (cleaner interface and improved performance over LatLongUTMconversion.py)
- when converting lat/lon to UTM, account for different UTM zones by shifting
  reference point and easting/northing values
- when converting x,y,z to lat/lon, estimate zone difference and use
  different UTM zones for easting; account for refpt in opposite hemisphere
  for northing
- there is still some slight distortion near UTM zone boundaries

Original comment by ahrenh...@gmail.com on 7 Aug 2013 at 10:14