Opened 15 years ago

Closed 15 years ago

#2749 closed defect (invalid)

gdal_rasterize ERROR 6 on converting polygon shape file to tif

Reported by: bala Owned by: warmerdam
Priority: normal Milestone:
Component: default Version: 1.6.0
Severity: normal Keywords: gdal_rasterize adrg driver
Cc:

Description

I have installed gdal160.zip on Suse Linux 10 and compiled it. When I tried to use this command I get the following error:

gdal_rasterize -b 1 -b 2 -b 3 -burn 0 -burn 0 -burn 0 -l mask mask.shp work.tif

ERROR 6: The ADRG driver does not support update access to existing datasets.

Please help.

Thanks, Bala

Change History (3)

comment:1 by Even Rouault, 15 years ago

Strange... This is an issue that existed in the ADRG driver in GDAL 1.5.0, but that has been fixed during GDAL 1.6.0 development, as well as in GDAL 1.5.3. See #2465

Are you really sure you are running the right GDAL version ?

Please do : "gdal_rasterize --utility_version" and check that you get : "gdal_rasterize was compiled against GDAL 1.6.0 and is running against GDAL 1.6.0"

comment:2 by bala, 15 years ago

I have both gdal16 and gdal152 directories. It seems earlier it referencing 1.5.2

gdal_rasterize was compiled against GDAL 1.6.0 and is running against GDAL 1.5.2

Now I have removed 1.5.2 and removed 1.5.2 references from PATH and LIBRARY PATH variables. And recompiled gdal 1.6.0. Now I get a different error message.

$gdal_rasterize --utility_version gdal_rasterize was compiled against GDAL 1.6.0 and is running against GDAL 1.6.0

$gdal_rasterize -b 1 -b 2 -b 3 -burn 0 -burn 0 -burn 0 -l mask mask.shp work.tif ERROR 4: `work.tif' does not exist in the file system, and is not recognised as a supported dataset name.

Thanks, Bala

comment:3 by Even Rouault, 15 years ago

Resolution: invalid
Status: newclosed

That's fine now. The error you get is expected. The destination GDAL dataset must exist *before* you run gdal_rasterize. See http://www.gdal.org/gdal_rasterize.html

I'm pretty sure this has been discussed on the mailing list before. I believe there's an enhancement request in the trac database about that.

Note: See TracTickets for help on using tickets.