Hi,
Thank you for your quick response.
I try to build the nitfdump utility on windows XP
with the following command executed in $(GDAL_HOME)\frmts\nitf:
nmake -f makefile.vc nitfdump.exe
but I receive some linker erros:
nitfbilevel.obj : error LNK2019: riferimento al simbolo esterno
_TIFFReadE
Thanks to both Frank and Chaitanya this is now resolved.
Adding in the coordinate system to my GeoJSON solved the issue in the
latest versions of GDAL.
Leaving this out did not produce errors using ogrinfo, but it did not
display the feature as WKT until the CRS was added in.
{
"type": "P
Seth,
You can obtain the WKT of the geometries in a vector data source by using
ogrinfo with the -al option.
(http://www.gdal.org/ogrinfo.html)
On Sun, Nov 21, 2010 at 6:20 PM, geographika wrote:
> On 19/11/2010 18:04, Frank Warmerdam wrote:
>
>> geographika wrote:
>>
>>> Hi,
>>>
>>> I have upg
2010/11/21 MarvinCO
>
> Which are the common DLL search locations? Eclipse doesn't give me any clue
> about how its starts the JVM, and which additional locations it may ask the
> JVM to search automatically. Process monitor also doesn't really give me
> any
> clue, it shows me mainly files from
On 19/11/2010 18:04, Frank Warmerdam wrote:
geographika wrote:
Hi,
I have upgraded from GDAL 1.6 (32bit Windows) to 1.7 (64 bit Windows)
and the following command no longer works:
C:\mapserver\bin\gdal\apps\gdalwarp C:\Data\Rasters\MiscSuit.tif
C:\RasterClips\mytest.tif -cutline c:\RasterCl
Which are the common DLL search locations? Eclipse doesn't give me any clue
about how its starts the JVM, and which additional locations it may ask the
JVM to search automatically. Process monitor also doesn't really give me any
clue, it shows me mainly files from the System32 folder, which should
I'm sorry I sent this message to the wrong mailing list
Here goes the reply to your message markus
Hello Markus
I believe it's ok:
projection: 1 (UTM)
zone: -24
datum: wgs84
ellipsoid: wgs84
north: 9305500.0001
south: 9095770.0001
west: 444000
east: 68913
