Location boundaries for Duesseldorf is wrong

[GoogleCodeExporter]

What steps will reproduce the problem?
1. call the location function with you key 
http://www.car2go.com/api/v2.1/locations?oauth_consumer_key=consumerkey&format=j
son
2.the interesting part of the answer is this:
{
 "countryCode":"DE",
 "defaultLanguage":"de",
 "locationId":10,
 "locationName":"Duesseldorf",
 "mapSection":{
 "center":{
 "latitude":51.22444,
 "longitude":6.78459
},
"lowerRight":{
"latitude":51.101604,
"longitude":6.521018
},
"upperLeft":{
"latitude":51.16457,
"longitude":6.414036
} [...]
3. draw a box on a map with the upperLeft and loweRight coordinates

What is the expected output? What do you see instead?
The coordinates should build a box around Duesseldorf. I entered this 
coordiantes to Google Maps: http://goo.gl/maps/Y2fj9 and did a navigation from 
lower right via center to upper left. as you can see, lower right and upper 
left are far away from Duesseldorf. Here is, what it looks like in Ulm: 
http://goo.gl/maps/FCQYz. I tried some other Cities like Cologne, Ulm or 
Vancouver. Everything lookes fine there.

Conclusion: the upperLeft and lowerRight-Attributes in Duesseldorf need to be 
fixed. 

Original issue reported on code.google.com by tobias.b...@gmail.com on 8 Aug 2012 at 11:55

[GoogleCodeExporter]

Two more problems with mapSection:

1) In London, the boundary is also wrong.
2) In Miami, lowerRight is actually the lower left corner and vice versa. i.e. 
longitudes are swapped.

Our released app is affected by those issues. Can we get this fixed or should 
we push an update with a workaround?

Original comment by hhochlei...@gmail.com on 18 Dec 2012 at 2:56

[GoogleCodeExporter]

Take a look at the date i opened this issue... Maybe you should do a workaround.

Am 18.12.2012 um 15:56 schrieb "car2go@googlecode.com" <car2go@googlecode.com>:

Original comment by tobias.b...@gmail.com on 18 Dec 2012 at 3:12

[GoogleCodeExporter]

Yeah, Car2Go are you listening? Are you even looking at this tracker, let alone 
use it? If you don't please deactivate it!

Original comment by hhochlei...@gmail.com on 18 Dec 2012 at 3:18