Ticket #3278 (closed defect: invalid)

Opened 3 years ago

Last modified 3 years ago

gdal_proximity.py give an error when tries to replace an existent output file with different band

Reported by: brushtyler Owned by: warmerdam
Priority: low Milestone:
Component: GDAL_Raster Version: 1.6.2
Severity: normal Keywords: gdal_proximity
Cc:

Description

gdal_proximity.py give an error when tries to replace an existent output file with different band.

If the output already exists and was created by a different band input file, this error is displayed: ERROR 1: Source and proximity bands are not the same size.

If you remove the existent file, it works fine.

Change History

Changed 3 years ago by warmerdam

  • keywords gdal_proximity added; proximity removed
  • status changed from new to closed
  • resolution set to invalid

This is the correct behavior.

gdal_proximity.py supports writing to an existing file but only if it is of a compatible size and configuration. gdal_proximity.py does not delete a file if the output file is pre-existing.

Changed 3 years ago by brushtyler

Is the correct behaviour? I refer to the online help, it quote:
"dstfile The destination raster file to which the proximity map will be written."
I think it's not explained so well.

Changed 3 years ago by warmerdam

I agree, I have tried to clarify someone in the documentation in trunk (r18282).

Note: See TracTickets for help on using tickets.