<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><br>
</p>
<div class="moz-cite-prefix">Le 17/02/2023 à 20:28, Regina Obe a
écrit :<br>
</div>
<blockquote type="cite"
cite="mid:001f01d94305$fbfc6560$f3f53020$@pcorp.us">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style>@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;}p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
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;}span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}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]-->
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Would
that be a breaking change for any down the stream apps.
Suddenly mixing multi with singles?<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">That
would be my main concern.</span></p>
</div>
</blockquote>
<p>Yes that would be. Typically GeoPackage has the same
strong/pedantic typing constraints as PostGIS on geometry columns.
So a "ogr2ogr out.gpkg PG:...." scenario would currently break if
a PostGIS multipolygon layer would contain polygons (well, to be
more exact, the GPKG driver would actually accept a mix of
polygons & multipolygons in a multipolygon layer, but would
emit a warning that this is non conformant to the GPKG spec)</p>
<p>GML has also different types for single vs multi.</p>
<p>Shapefile is a bit weird, where it has the same type for
Polygon/MultiPolygon and LineString/MultiLineString, but
distinguishes Point from MultiPoint...<br>
</p>
<p>I agree with Darafei that, in an ideal world, a punctual / linear
/ areal separation, that would encompass single vs multi,
"straight" vs "curvy" variants, would make much more sense. If you
could know for a geometry colum of type "linear", if it actually
contains rows with single, multi, straight or curvy, that could
make the translation to other formats easier, but I guess that
would involve triggers to keep such metadata up-to-date. Changing
the whole ecosystem of formats is tricky.</p>
PostGIS being lax on ingestion and automatically converting single
to multipart however is non breaking.<br>
<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>