It should be possible to specially implement the CreateCopy for XYZ format to avoid this. I'll investigate this.
Best regards, On Thu, May 10, 2012 at 8:30 AM, kaarigar <kaari...@gmail.com> wrote: > > Etienne Tourigny-3 wrote >> >> Something that is not apparent is that gdal_translate (via driver's >> GDALCreateCopy()) usually opens the new dataset after creation, and >> the XYZ file loading is slow: >> > That explains it - the XYZ file created is ~4gb in size - it would take it a > very very long time to figure out the details from it. What I don't > understand is why gdal_translate would want to open the created xyz file? Is > there a special build of this utility that doesn't do this? > > -- > View this message in context: > http://osgeo-org.1560.n6.nabble.com/gdal-translate-waits-at-the-end-of-operation-tp4964258p4965947.html > Sent from the GDAL - Dev mailing list archive at Nabble.com. > _______________________________________________ > gdal-dev mailing list > gdal-dev@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/gdal-dev -- ---------------------------------------+-------------------------------------- I set the clouds in motion - turn up | Frank Warmerdam, warmer...@pobox.com light and sound - activate the windows | http://pobox.com/~warmerdam and watch the world go round - Rush | Geospatial Software Developer _______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev