Exported KML/Z doesn't exactly match the bounds of the original map

zenwalk / mapaction-toolbox

Automatically exported from code.google.com/p/mapaction-toolbox

0 stars 0 forks source link

Exported KML/Z doesn't exactly match the bounds of the original map #37

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago

What steps will reproduce the problem?
1. Create a map with a projected CRS
2. Export it
3. Compare the bounds of the resultant KML with the bounds of the original map.

What is the expected output? What do you see instead?
The bounds differ - even from the bounds of the map when switched to WGS84.

Original issue reported on code.google.com by andrewphilipsmith on 4 Mar 2013 at 8:28

GoogleCodeExporter commented 9 years ago

We have disabled KML export for milestone 3.0 as a quick fix on this.

Original comment by andrewphilipsmith on 21 Jul 2013 at 7:56

Added labels: Priority-Low, Milestone-Release4.0
Removed labels: Priority-Medium

GoogleCodeExporter commented 9 years ago

KML/Z export is an enhancement at this stage.

Original comment by andrewphilipsmith on 17 Aug 2014 at 11:52

Added labels: Type-Enhancement
Removed labels: Type-Defect