2009/6/25 Mateusz Loskot <[email protected]> > Jorge Arévalo wrote: > >> I have a question: What's the best way to test a new driver's code? I've >> loaded this TIFF file into PostGIS using gdal2wktraster.py: >> http://rapidfire.sci.gsfc.nasa.gov/subsets/?subset=USA1.2009168.terra.2km, >> and I think that I can simply do gdalinfo PG:.... to test if my driver is >> working. >> > > Possible, but... > > Another option is to create testing code, but gdalinfo is more reliable >> that any code that I can write... >> > > you'll most likely need to debug your driver, so having this in mine, > choose your favourite option. > > Best regards, > -- > Mateusz Loskot, http://mateusz.loskot.net >
OK, maybe I can create my own testing code. I supose that the best place to put this testing code is in the driver's directory. It's only temporary testing code. Yogi Berra <http://www.brainyquote.com/quotes/authors/y/yogi_berra.html> - "I never said most of the things I said."
_______________________________________________ gdal-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/gdal-dev
