<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    Andrew,<br>
    <blockquote type="cite"
cite="mid:CACJ51z1FeDpaqXmXPeMNXDGxJo+QU7yvLuGAJ2z+hh90+8MEng@mail.gmail.com">
      <div dir="ltr"><br>
        Not sure I understand this. Do you have an example?<br>
      </div>
    </blockquote>
    <p>The vector C++ API involves including typically ogrsf_frmts.h. So
      the question is whether gdal_cpp.h should include it or not
      (currently it doesn't)<br>
    </p>
    <blockquote type="cite"
cite="mid:CACJ51z1FeDpaqXmXPeMNXDGxJo+QU7yvLuGAJ2z+hh90+8MEng@mail.gmail.com">
      <div dir="ltr"><br>
        "Does the content of :file:`gdal_cpp.h` must target only the
        GDAL "classic 2D" and<br>
          multidimensional C++ API, or also the C++ vector API ?</div>
      <br>
      <div class="gmail_quote gmail_quote_container">
        <div dir="ltr" class="gmail_attr">On Mon, Sep 15, 2025 at
          3:20 PM Even Rouault 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">Hi,<br>
          <br>
          Please review <a
            href="https://github.com/OSGeo/gdal/pull/13071"
            rel="noreferrer" target="_blank" moz-do-not-send="true"
            class="moz-txt-link-freetext">https://github.com/OSGeo/gdal/pull/13071</a>
          : Split of <br>
          gdal_priv.h and addition of gdal_cpp.h header<br>
          <br>
          Summary:<br>
          <br>
          This RFC splits the content of gdal_priv.h, the installed
          header <br>
          containing declaration for GDAL (raster) C++ classes, into
          finer grain <br>
          exported headers. It also adds a new gdal_cpp.h exported
          header, which <br>
          is essentially the content of current gdal_priv.h header, but
          with a <br>
          more engaging name. Those changes are done in a fully backward
          <br>
          compatible way: current external users of gdal_priv.h will not
          have any <br>
          change to do in their source code.<br>
          <br>
          Even<br>
          <br>
          -- <br>
          <a href="http://www.spatialys.com" rel="noreferrer"
            target="_blank" moz-do-not-send="true"
            class="moz-txt-link-freetext">http://www.spatialys.com</a><br>
          My software is free, but my time generally not.<br>
          <br>
          _______________________________________________<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>
      <div><br clear="all">
      </div>
      <div><br>
      </div>
      <span class="gmail_signature_prefix">-- </span><br>
      <div dir="ltr" class="gmail_signature">
        <div dir="ltr">
          <div>Andrew Bell</div>
          <a href="mailto:andrew.bell.ia@gmail.com" target="_blank"
            moz-do-not-send="true" class="moz-txt-link-freetext">andrew.bell.ia@gmail.com</a></div>
      </div>
    </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.</pre>
  </body>
</html>