search

CROAugmensys / osmdroid

Automatically exported from code.google.com/p/osmdroid
0 stars 0 forks source link

Bug in BoundingBoxE6.fromGeoPoints() method #24

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Calling the method with a valid ArrayList of GeoPoints

What is the expected output? What do you see instead?
Expected output is a BoundingBoxE6 instance with LatNorth, LatSouth,
LatEast and LatWest attributes correctly set.
Instead: LatNorth and LatSouth values are swapped.
This is due to incorrect order of minLat and maxLat parameters passed to
the BoundingBoxE6 constructor - appears to be swapped

What version of the product are you using? On what operating system?
Latest from trunk, as of time of issue submission

Please provide any additional information below.

Original issue reported on code.google.com by CedricS...@gmail.com on 17 Mar 2010 at 3:15

GoogleCodeExporter commented 9 years ago

Original comment by neilboyd on 18 Mar 2010 at 9:31

GoogleCodeExporter commented 9 years ago 
This issue was closed by revision r118.

Original comment by neilboyd on 18 Mar 2010 at 7:32