[gdal-dev] GDAL python tools and batch files

Jonathan Moules jonathanmoules at warwickshire.gov.uk
Mon Dec 2 04:13:48 PST 2013


Thanks Paul, that did it. I guess it's a python/batch file interaction
thing.

Cheers,
Jonathan



On 2 December 2013 11:51, Paul Meems <p.meems at topx-group.nl> wrote:

> I think you should add 'call' at the begining of the command:
>
> http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/call.mspx?mfr=true
>
>
>
> Met vriendelijke groet,
>
>
> Paul Meems
>
>
> *Paul Meems*Senior GIS consultant
>
> 06-53989481
> TopX Geo-ICT <http://www.topx-geo-ict.nl>
>
>  <http://topx-group.nl/topx-geo-ict>Wij bieden ondersteuning
>
> voor MapWindow GIS <http://www.mapwindow.org/>
>
>
>
> 2013/12/2 Jonathan Moules <jonathanmoules at warwickshire.gov.uk>
>
>>  Hi List,
>> I'm trying to batch (Windows) a fairly simple task - mosaic and then
>> pyramid some rasters.
>>
>> While testing, I've simplified my batch file down to two lines:
>>
>> gdal_merge -o %THIS_DIR%.tif -of GTiff -co TILED=YES -co BIGTIFF=YES -co
>>> COMPRESS=JPEG -co JPEG_QUALITY=80 -co BLOCKXSIZE=512 -co BLOCKYSIZE=512
>>> --optfile tiff_list.txt -co
>>> PHOTOMETRIC=YCBCR
>>>
>>
>>
>>> pause
>>
>>
>>
>> The problem is that once gdal_merge has finished processing, rather than
>> continue onward the batch file ends, so in this case the "pause" is never
>> triggered. Doesn't matter what comes next, the batch ends as soon as the
>> merge is complete.
>>
>> However the same simple batch file but with a gdaladdo command instead
>> works fine. Is this a python thing?
>>
>> Anyone know why that is? Should it be doing this? Using the OSGeo GDAL
>> 1.10.1 build, but it happened with FWTools too (thought it was a FWTools
>> bug at the time).
>>
>> Tested on Windows 7 and Server 2008.
>>
>> Cheers,
>> Jonathan
>>
>> This transmission is intended for the named addressee(s) only and may
>> contain sensitive or protectively marked material up to RESTRICTED and
>> should be handled accordingly. Unless you are the named addressee (or
>> authorised to receive it for the addressee) you may not copy or use it, or
>> disclose it to anyone else. If you have received this transmission in error
>> please notify the sender immediately. All email traffic sent to or from us,
>> including without limitation all GCSX traffic, may be subject to recording
>> and/or monitoring in accordance with relevant legislation.
>> _______________________________________________
>> gdal-dev mailing list
>> gdal-dev at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/gdal-dev
>>
>
>

-- 
This transmission is intended for the named addressee(s) only and may 
contain sensitive or protectively marked material up to RESTRICTED and 
should be handled accordingly. Unless you are the named addressee (or 
authorised to receive it for the addressee) you may not copy or use it, or 
disclose it to anyone else. If you have received this transmission in error 
please notify the sender immediately. All email traffic sent to or from us, 
including without limitation all GCSX traffic, may be subject to recording 
and/or monitoring in accordance with relevant legislation.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20131202/2c0fc39a/attachment-0001.html>


More information about the gdal-dev mailing list