Hello, I learn now:
Wraps is something to eat, so it's better to use warper.
Am 21.06.2013 14:39, schrieb Tim Waters:
Hi folks,
Tim, it's map-warper not map-wraper :-)
However you are not the first in making this mistake and I really like
"MapWrapper" the name, and a few groups in India think that this is a
better way to think about how a map wraps around the world, as opposed
to maps warping.
On 21 June 2013 09:56, Tim Alder <tim.alder(a)s2002.tu-chemnitz.de
<mailto:tim.alder@s2002.tu-chemnitz.de>> wrote:
Hello,
I wondering why the new template support the old KML-overlay.
I think i'm missing the point here, but the warper has a KML output
which works nicely in google earth but the subset of kml support in
google maps is very poor, (and non existent in their new maps offering)
We had 2007 a solution in Commons that use KML and Google Earth for maps
overlay, you can found it at Template:Overlay. But it had lots of
limitation as it supports only positioning,scaling and rotation.
Maps-warpers kml-export is much more flexible because it based on an
transformated/warped image. So I would keep the old kml overlay unchange
but would support for the new system only maps-warper.
With parameters I mean a list of matching points.
Also if I know
that for modern maps that are generated by users in a GIS-system, it
would be nice to support GDAL <http://www.gdal.org/gdalwarp.__html
<http://www.gdal.org/gdalwarp.html>> for transformations. But I
don't believe that maps-wraper support it.
The warper actually only uses GDAL (gdalwarp and gdal_translate) to
do the transformations.
What I mean here was that it would be nice if I could say that my map is
produced in Projection xy and give the coordinates at the border or so,
instead of using tons of matching points. But for the beginning I
believe we can life with matching points.
Greetings Tim alias Kolossos