Dave,
The reason you have lat/lon values for each pixel is because they may not
be aligned exactly.
Even though it is not very 'efficient', you have to define the GCPs for
each pixel with the lat/lon values of that pixel. Then you use gdalwarp
while forcing use of these GCPs to combine all the
Chaitanya,
I attempted a few small examples with GCPs and gdalwarp told me:
ERROR 1: Failed to compute GCP transform: Transform is not solvable
I tried it with 2 GCPs at the sides from a 1x15 image array and another
with every point's GCP defined, both failed with that error. Sorry I
forgot
Sure, pixels were probably not the best word to use. I have 15
points(elements) per scan line per variable directly from an aircraft
instrument. So I might have a 15 element array of brightness
temperatures, a 15 element array of latitudes corresponding to those
points in the BT array, and
Dave,
You said that you have lat/lon values for each pixel. Can you explain?
On Fri, Jul 20, 2012 at 8:44 PM, David Hoese dho...@gmail.com wrote:
I'm attempting to put aircraft scan data into geotiffs (1-3 scanlines
each) and then use gdal_merge.py to combine them into one large geotiff
I'm attempting to put aircraft scan data into geotiffs (1-3 scanlines
each) and then use gdal_merge.py to combine them into one large geotiff
that has the entire aircraft's path. The scan lines are 15 pixels wide
and taken every 10 seconds, the geotiffs are wgs84 lat/lon, and I have
lat/lon
