When you say that the coordsys header is wrong, are you looking at it in
MapInfo or in a text editor? If you look at the MIF file coordinates in a
text editor do they look like they have been correctly transformed, and it
is just the header that is wrong?
On Mon, May 8, 2017 at 7:39 AM, Jonathan
Nice to see that I'm only 3 weeks behind the curve!
> On May 8, 2017, at 2:58 PM, Kurt Schwehr wrote:
>
> Yup... https://lists.osgeo.org/pipermail/gdal-dev/2017-April/046495.html
>
> I'd be happy if anyone else wanted to take lead on it.
>
> I've created
Yup... https://lists.osgeo.org/pipermail/gdal-dev/2017-April/046495.html
I'd be happy if anyone else wanted to take lead on it.
I've created https://trac.osgeo.org/gdal/ticket/6883
Since I'm internal to google, I've been running some fuzzer targets against
gdal behind the scenes and used the
I think the gdal suite would be a perfect candidate for this project from
google. Is anyone interested in trying to integrate gdal into it?
https://opensource.googleblog.com/2017/05/oss-fuzz-five-months-later-and.html?m=1
___
gdal-dev mailing list
Hello everyone,
I struggle to reproject GeoJSON file to TAB (or MIF) file.
The source projection is EPSG:4326 and the destination projection is
EPSG:31370 (Belge 1972 / Belgian Lambert 72 Belgium :
http://epsg.io/31370)
I searched forums and mailing lists and saw that there was some
Hi Howard,
Yep. It is a license issue but I am not going to get into the details.
But apart from that, lets think about other scenarios:
An application is using GDAL and Proj4 and someone decide to update GDAL to get
some bug fixes.
But GDAL is build *without* static Proj4 and therefore
Ari,
I had similar problems. The problem is that an old version of gdal is
installed by travis by default (!)
adding
before-install:
- sudo apt-get remove -y libgdal1
fixed this for me on trusty (and on precise, but you will still not
get the latest version).
Kind Regards,
Johan
On Tue, Apr