<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>Conrad,</p>
    <p>Try something like:</p>
    <p>gdal_translate input.tif imagery.vrt -b 3<br>
    </p>
    <p>gdalwarp imagery.vrt imagery_warped.tif -geoloc -to X_DATASET=input.tif
      -to X_BAND=2 -to Y_DATASET=input.tif -to Y_BAND=1 -to PIXEL_OFFSET=0
      -to PIXEL_STEP=1 -to LINE_OFFSET=0 -to LINE_STEP=1 -to
      SRS=EPSG:4326 -a_srs EPSG:4326  -overwrite<br>
    </p>
    <p>Obviously I have most certainly got something wrong in the above,
      but hopefully with a tiny tweaking that should put you on the
      right track.<br>
    </p>
    <p>Reference:
      <a class="moz-txt-link-freetext" href="https://gdal.org/en/latest/development/rfc/rfc4_geolocate.html">https://gdal.org/en/latest/development/rfc/rfc4_geolocate.html</a><br>
    </p>
    <p>Even<br>
    </p>
    <div class="moz-cite-prefix">Le 18/10/2024 à 12:37, Javier Jimenez
      Shaw via gdal-dev a écrit :<br>
    </div>
    <blockquote type="cite"
cite="mid:CADRrdKt0rxOUe+hAKPbEt_NjVtD5VKfmZZwt_G28BuYLsi=GoQ@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <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>
        </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>
        </div>
      </div>
      <br>
      <div class="gmail_quote">
        <div dir="ltr" class="gmail_attr">On Fri, 18 Oct 2024 at 12:20,
          Conrad Bielski via gdal-dev <<a
            href="mailto:gdal-dev@lists.osgeo.org"
            moz-do-not-send="true" class="moz-txt-link-freetext">gdal-dev@lists.osgeo.org</a>>
          wrote:<br>
        </div>
        <blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
          <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>
              </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>
              </div>
              <div dir="ltr">The question I have is how best to
                integrate this information into a reprojection workflow?</div>
              <div dir="ltr"><br>
              </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>
              </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>
              </div>
              <div dir="ltr">Thanks in advance for your help,</div>
              <div dir="ltr">Conrad<br>
              </div>
            </div>
          </div>
          _______________________________________________<br>
          gdal-dev mailing list<br>
          <a href="mailto:gdal-dev@lists.osgeo.org" target="_blank"
            moz-do-not-send="true" class="moz-txt-link-freetext">gdal-dev@lists.osgeo.org</a><br>
          <a href="https://lists.osgeo.org/mailman/listinfo/gdal-dev"
            rel="noreferrer" target="_blank" moz-do-not-send="true"
            class="moz-txt-link-freetext">https://lists.osgeo.org/mailman/listinfo/gdal-dev</a><br>
        </blockquote>
      </div>
      <br>
      <fieldset class="moz-mime-attachment-header"></fieldset>
      <pre class="moz-quote-pre" wrap="">_______________________________________________
gdal-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:gdal-dev@lists.osgeo.org">gdal-dev@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/gdal-dev">https://lists.osgeo.org/mailman/listinfo/gdal-dev</a>
</pre>
    </blockquote>
    <pre class="moz-signature" cols="72">-- 
<a class="moz-txt-link-freetext" href="http://www.spatialys.com">http://www.spatialys.com</a>
My software is free, but my time generally not.
Butcher of all kinds of standards, open or closed formats. At the end, this is just about bytes.</pre>
  </body>
</html>