Index, srcDataType, 0, &srcValue,
> GDT_Byte,
> 0, 1 );
I did think to try that not long after posting my message, and it's working
nicely now. The pixel offset values are more like stride values than offsets,
to my mind anyway. Thanks for confirmin
the calculations for
srcPixelIndex are correct.
Regards,
Jo Meder
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev
between the orthophoto and the DEM. There is one set of shadows from the
orthophotos and one from the rendering.
Anyway, thanks for putting me on the right track.
Regards,
Jo Meder
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev
doing is reprojecting all the data to a
custom projection for our world. The reprojection would handle the cases like
this NLCD data.
Regards,
Jo Meder
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev
le code in the ReadBlock() docs, very helpful
as a start :-).
Regards,
Jo Meder
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev
oints.
Regards,
Jo Meder
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev
blocks? I would just try it but it will
take some rearranging of code so I thought I would ask if anyone has
experienced this same performance problem and had any insights on a solution.
Thanks,
Jo Meder
___
gdal-dev mailing list
gdal-dev@lists
