<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
pre
{mso-style-priority:99;
mso-style-link:"HTML con formato previo Car";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.HTMLconformatoprevioCar
{mso-style-name:"HTML con formato previo Car";
mso-style-priority:99;
mso-style-link:"HTML con formato previo";
font-family:Consolas;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EstiloCorreo21
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="CA" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">Good morning, <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<pre style="mso-margin-top-alt:0cm;margin-right:36.0pt;margin-bottom:0cm;margin-left:36.0pt;margin-bottom:.0001pt">>> It has just crossed my mind that "gdal convert in.shp out.tif" could do a rasterization behind the scenes, but that's probably pushing syntax sugar too far...<o:p></o:p></pre>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">something like "gdal convert in.shp out.gpkg" could be confusing. At least should be an specifier to force vector or raster output, shouldn’t be?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="ES" style="font-size:11.0pt;font-family:"Calibri",sans-serif">De:</span></b><span lang="ES" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> gdal-dev <gdal-dev-bounces@lists.osgeo.org>
<b>En nombre de </b>Even Rouault via gdal-dev<br>
<b>Enviado el:</b> dilluns, 18 de novembre de 2024 22:44<br>
<b>Para:</b> Andrew Bell <andrew.bell.ia@gmail.com><br>
<b>CC:</b> gdal-dev@lists.osgeo.org<br>
<b>Asunto:</b> Re: [gdal-dev] Call for review on RFC 104: Adding a "gdal" front-end command line interface<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p><o:p> </o:p></p>
<div>
<p class="MsoNormal">Le 18/11/2024 à 22:27, Andrew Bell a écrit :<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre>My biggest question is why you would mix vector and raster operations<o:p></o:p></pre>
<pre>in the CLI.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>And since we're taking on changing things, I would wonder why those<o:p></o:p></pre>
<pre>two parts of the codebase are commingled. Is there a strong reason not<o:p></o:p></pre>
<pre>to have an OGR project that does vector operations and a GDAL project<o:p></o:p></pre>
<pre>that does raster operations? It seems like mostly an historical<o:p></o:p></pre>
<pre>artifact.<o:p></o:p></pre>
</blockquote>
<p>At the beginning of times, GDAL and OGR were separate sub-projects, and it was thought in
<a href="https://gdal.org/en/latest/development/rfc/rfc46_gdal_ogr_unification.html">
https://gdal.org/en/latest/development/rfc/rfc46_gdal_ogr_unification.html</a> (almost 10 years ago) that they should be unified, at least as some aspects, driver management, dataset structure and metadata handling, were common between both. Not to mention
formats that can contain vector and raster metadata in the same container. Admittedly, some aspects of the unification could still be perfected, like converting a dataset with both types at once. Mostly an implementation detail at the driver level...<o:p></o:p></p>
<p>In practice there are operations like rasterization, gridding, contouring, polygonization that mix both data types. So considering them as fully separate is not so obvious. I believe that having "gdal convert in.shp out.parquet" and "gdal convert in.tif
out.nc" work in an identical way would be big progress compared to "ogr2ogr out.parquet in.shp" and "gdal_translate in.tif out.nc" . It has just crossed my mind that "gdal convert in.shp out.tif" could do a rasterization behind the scenes, but that's probably
pushing syntax sugar too far...<o:p></o:p></p>
<pre>-- <o:p></o:p></pre>
<pre><a href="http://www.spatialys.com">http://www.spatialys.com</a><o:p></o:p></pre>
<pre>My software is free, but my time generally not.<o:p></o:p></pre>
<pre>Butcher of all kinds of standards, open or closed formats. At the end, this is just about bytes.<o:p></o:p></pre>
</div>
</body>
</html>