<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;">Travis and Frank,<br><br>Thank you very much for your help!<br><br>My best regards,<br>Pedro<br><br><br><br>--- On <b>Tue, 2/9/10, Frank Warmerdam</b> wrote:<br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"><br><br><div class="plainMail">Pedro Venāncio wrote:<br>> gdalwarp -s_srs */ proj_string1/* -t_srs */ proj_string1/* [-r */ resamplig_method/*] */inputfile.ecw outputfile.ecw/*<br>...<br>> > I noticed that using gdalwarp with ecw, the resulting files are<br>> always<br>> > GTiff, even if the command indicates the creation of an ecw, and the<br>> > resulting file name appear .ecw (gdalinfo shows that they are<br>> GTiffs).<br>> > Is this
behavior a bug or just a requirement of gdalwarp?<br><br>Pedro,<br><br>The default output format is GeoTIFF. There is no autodetection of output<br>format based on filename extensions. If you want to produce another output<br>format you need to specify it with the -of flag. The ECW format does not<br>support simple creation (only CreateCopy()) and is not a selectable output<br>format for gdalwarp.<br><br>Best regards,<br>-- ---------------------------------------+--------------------------------------<br>I set the clouds in motion - turn up | Frank Warmerdam, <a ymailto="mailto:warmerdam@pobox.com" href="/mc/compose?to=warmerdam@pobox.com">warmerdam@pobox.com</a><br>light and sound - activate the windows | <a href="http://pobox.com/%7Ewarmerdam" target="_blank">http://pobox.com/~warmerdam</a><br>and watch the world go round - Rush | Geospatial Programmer for
Rent<br><br></div></blockquote></td></tr></table><br>