<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">I don’t believe these are huge features, its OSM building for the world. Must be the memory constraint since it is a lot of features. This doesn’t happen (i think, am retesting now) if created from the osm pbf file directly but does from the fgb created from the pbf. <div><br></div><div>Do either of the columnar formats (arrow, geoparquet) support spatial access window selections yet (via ogr2ogr) or is that still forthcoming?</div><div><br></div><div>Mike</div><div><br></div><div>Michael Smith</div><div>Remote Sensing / GIS Center</div><div><br><div dir="ltr"><br><blockquote type="cite">On Nov 24, 2022, at 1:12 PM, Even Rouault <even.rouault@spatialys.com> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<p>Mike,<br>
</p>
<div class="moz-cite-prefix">Le 24/11/2022 à 18:56,
<a class="moz-txt-link-abbreviated" href="mailto:michael.smith.erdc@gmail.com">michael.smith.erdc@gmail.com</a> a écrit :<br>
</div>
<blockquote type="cite" cite="mid:06E632AE-15BB-4E38-A4A0-D42D45EB0151@gmail.com">
<p class="MsoNormal">Basically, can one create a spatial index in
a flatgeobuf file if the source does not have one? <br>
</p>
</blockquote>
yes, through ogr2ogr by creating a new file, as you did<br>
<blockquote type="cite" cite="mid:06E632AE-15BB-4E38-A4A0-D42D45EB0151@gmail.com">
<p class="MsoNormal"> </p>
<p class="MsoNormal">Also, when trying to just create a new
flatgeobuf with a spatial index from one without (using
ogr2ogr), I get a lot of</p>
<p class="MsoNormal"><br>
</p>
<p class="MsoNormal">ERROR 2: ICreateFeature: Too big feature</p>
</blockquote>
<p>It could be either a huuuuge feature whose serialized form
exceeds 2GB (unlikely, and even more if you convert from an
existing flatgeobuf file which enforces this limit). Or that you
have lots of features and a modest amount of RAM. The creation of
the spatial index requires an amount of RAM proportional to the
number of features (maybe 80 bytes or so per feature). In this
later case, the error message is misleading currently. I've just
changed it to "ICreateFeature: Memory allocation failure" in
master.</p>
<p>Even</p>
<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>
</div></blockquote></div></body></html>