<html><head></head><body><div class="ydp9b020408yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;"><div></div>
<div dir="ltr" data-setdir="false">Hi Javier,</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">it is not a grid. So each raster pixel is assigned the geolocation. Yes - if I was to extract it, that's what it could be considered.</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">Conrad<br></div><div><br></div>
</div><div id="ydp220a3229yahoo_quoted_0210211694" class="ydp220a3229yahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Friday, October 18, 2024 at 11:37:28 AM GMT+1, Javier Jimenez Shaw <j1@jimenezshaw.com> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div id="ydp220a3229yiv9165000355"><div><div dir="ltr"><div>Is it an actual grid? in the meaning of having constant step size in X and Y.</div><div>In that case the geolocation is just the corner and the x and y sizes. You can convert to a georeference raster, and warp it.<br clear="none"></div><div>If it is not the case, you have something more like a 2D pointcloud, or a bunch of poins in a strange vector format.<br clear="none"></div></div><br clear="none"><div class="ydp220a3229yiv9165000355gmail_quote"><div id="ydp220a3229yiv9165000355yqt52586" class="ydp220a3229yiv9165000355yqt2657179841"><div dir="ltr" class="ydp220a3229yiv9165000355gmail_attr">On Fri, 18 Oct 2024 at 12:20, Conrad Bielski via gdal-dev <<a shape="rect" href="mailto:gdal-dev@lists.osgeo.org" rel="nofollow" target="_blank">gdal-dev@lists.osgeo.org</a>> wrote:<br clear="none"></div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex;" class="ydp220a3229yiv9165000355gmail_quote"><div><div style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;"><div dir="ltr">Hello GDAL-experts,</div><div dir="ltr"><br clear="none"></div><div dir="ltr">normally when I use GDAL for reprojecting imagery, the projection information that I use is the source spatial reference (SRS) associated with the imagery. However, now I have imagery which is lat/lon geographic and I have two separate bands which also carry the pixel geographic information. So the following raster inputs all the same size:</div><div dir="ltr">1. Band 1 = latitude</div><div dir="ltr">2. Band 2 = longitude</div><div dir="ltr">3. Band 3 = imagery</div><div dir="ltr"><br clear="none"></div><div dir="ltr">The question I have is how best to integrate this information into a reprojection workflow?</div><div dir="ltr"><br clear="none"></div><div dir="ltr">I presume that gdalwarp is the best option here, but how can I take advantage of the individual pixel location information (rather than just the extents for example)? I know that I can mosaic into an existing file that I have already created in the target projection. Is this the best way to apply gdalwarp in this context?</div><div dir="ltr"><br clear="none"></div><div dir="ltr">I'm just wondering what is the best way to integrate the lat/lon pixel information into my warping using gdalwarp.</div><div dir="ltr"><br clear="none"></div><div dir="ltr">Thanks in advance for your help,</div><div dir="ltr">Conrad<br clear="none"></div></div></div>_______________________________________________<br clear="none">
gdal-dev mailing list<br clear="none">
<a shape="rect" href="mailto:gdal-dev@lists.osgeo.org" rel="nofollow" target="_blank">gdal-dev@lists.osgeo.org</a><br clear="none">
<a shape="rect" href="https://lists.osgeo.org/mailman/listinfo/gdal-dev" rel="nofollow" target="_blank">https://lists.osgeo.org/mailman/listinfo/gdal-dev</a><br clear="none">
</blockquote></div></div>
</div></div></div>
</div>
</div></body></html>