dependabot[bot] opened a new pull request, #744:
URL: https://github.com/apache/sedona-db/pull/744

   Bumps [geoarrow-schema](https://github.com/geoarrow/geoarrow-rs) from 0.7.0 
to 0.8.0.
   <details>
   <summary>Release notes</summary>
   <p><em>Sourced from <a 
href="https://github.com/geoarrow/geoarrow-rs/releases";>geoarrow-schema's 
releases</a>.</em></p>
   <blockquote>
   <h2>rust-v0.8.0</h2>
   <h2>What's Changed</h2>
   <ul>
   <li>docs: Add Geoparquet Example by <a 
href="https://github.com/C-Loftus";><code>@​C-Loftus</code></a> in <a 
href="https://redirect.github.com/geoarrow/geoarrow-rs/pull/1411";>geoarrow/geoarrow-rs#1411</a></li>
   <li>feat: Use <code>LazyLock</code> for constructing coordinate 
<code>DataType</code> instances by <a 
href="https://github.com/nuts-rice";><code>@​nuts-rice</code></a> in <a 
href="https://redirect.github.com/geoarrow/geoarrow-rs/pull/1420";>geoarrow/geoarrow-rs#1420</a></li>
   <li>chore: update to arrow v58 by <a 
href="https://github.com/gadomski";><code>@​gadomski</code></a> in <a 
href="https://redirect.github.com/geoarrow/geoarrow-rs/pull/1424";>geoarrow/geoarrow-rs#1424</a></li>
   <li>ci: Set up rust trusted publishing by <a 
href="https://github.com/kylebarron";><code>@​kylebarron</code></a> in <a 
href="https://redirect.github.com/geoarrow/geoarrow-rs/pull/1426";>geoarrow/geoarrow-rs#1426</a></li>
   <li>chore: Bump to 0.8 by <a 
href="https://github.com/kylebarron";><code>@​kylebarron</code></a> in <a 
href="https://redirect.github.com/geoarrow/geoarrow-rs/pull/1428";>geoarrow/geoarrow-rs#1428</a></li>
   <li>ci: Install GEOS as dev dependency in publish script by <a 
href="https://github.com/kylebarron";><code>@​kylebarron</code></a> in <a 
href="https://redirect.github.com/geoarrow/geoarrow-rs/pull/1429";>geoarrow/geoarrow-rs#1429</a></li>
   </ul>
   <h2>New Contributors</h2>
   <ul>
   <li><a href="https://github.com/C-Loftus";><code>@​C-Loftus</code></a> made 
their first contribution in <a 
href="https://redirect.github.com/geoarrow/geoarrow-rs/pull/1411";>geoarrow/geoarrow-rs#1411</a></li>
   </ul>
   <p><strong>Full Changelog</strong>: <a 
href="https://github.com/geoarrow/geoarrow-rs/compare/rust-v0.7.0...rust-v0.8.0";>https://github.com/geoarrow/geoarrow-rs/compare/rust-v0.7.0...rust-v0.8.0</a></p>
   </blockquote>
   </details>
   <details>
   <summary>Changelog</summary>
   <p><em>Sourced from <a 
href="https://github.com/geoarrow/geoarrow-rs/blob/main/CHANGELOG.md";>geoarrow-schema's
 changelog</a>.</em></p>
   <blockquote>
   <h2>0.8.0 - 2025-07-08</h2>
   <h2>What's Changed</h2>
   <ul>
   <li>docs: Add Geoparquet Example by <a 
href="https://github.com/C-Loftus";><code>@​C-Loftus</code></a> in <a 
href="https://redirect.github.com/geoarrow/geoarrow-rs/pull/1411";>geoarrow/geoarrow-rs#1411</a></li>
   <li>feat: Use <code>LazyLock</code> for constructing coordinate 
<code>DataType</code> instances by <a 
href="https://github.com/nuts-rice";><code>@​nuts-rice</code></a> in <a 
href="https://redirect.github.com/geoarrow/geoarrow-rs/pull/1420";>geoarrow/geoarrow-rs#1420</a></li>
   <li>chore: update to arrow v58 by <a 
href="https://github.com/gadomski";><code>@​gadomski</code></a> in <a 
href="https://redirect.github.com/geoarrow/geoarrow-rs/pull/1424";>geoarrow/geoarrow-rs#1424</a></li>
   <li>ci: Set up rust trusted publishing by <a 
href="https://github.com/kylebarron";><code>@​kylebarron</code></a> in <a 
href="https://redirect.github.com/geoarrow/geoarrow-rs/pull/1426";>geoarrow/geoarrow-rs#1426</a></li>
   </ul>
   <h2>New Contributors</h2>
   <ul>
   <li><a href="https://github.com/C-Loftus";><code>@​C-Loftus</code></a> made 
their first contribution in <a 
href="https://redirect.github.com/geoarrow/geoarrow-rs/pull/1411";>geoarrow/geoarrow-rs#1411</a></li>
   </ul>
   <p><strong>Full Changelog</strong>: <a 
href="https://github.com/geoarrow/geoarrow-rs/compare/rust-v0.7.0...rust-v0.8.0";>https://github.com/geoarrow/geoarrow-rs/compare/rust-v0.7.0...rust-v0.8.0</a></p>
   <hr />
   <p><strong>(Previously, changelogs were per-crate, but exploring reverting 
to one global changelog).</strong></p>
   <h2>0.4.0 (<code>geoparquet</code> crate) - 2025-07-08</h2>
   <p>New standalone <code>geoparquet</code> crate!</p>
   <h3>New Features :magic_wand:</h3>
   <ul>
   <li>GeoParquet reader refactor to avoid making duplicate wrappers of 
upstream structs <a 
href="https://redirect.github.com/geoarrow/geoarrow-rs/issues/1089";>#1089</a>
   <ul>
   <li>
   <p>Removes wrapper structs for builders. So we no longer have a 
<code>GeoParquetRecordBatchReaderBuilder</code> or a 
<code>GeoParquetRecordBatchStreamBuilder</code>. Users will use upstream 
<code>parquet</code> sync/async <code>Builder</code> structs directly. Means a 
significantly lower maintenance overhead here, and we don't need to do anything 
to support new upstream functionality.</p>
   </li>
   <li>
   <p>Adds <code>GeoParquetReaderBuilder</code> <strong>trait</strong> that 
extends the upstream <a 
href="https://docs.rs/parquet/latest/parquet/arrow/arrow_reader/struct.ArrowReaderBuilder.html";><code>ArrowReaderBuilder</code></a>.
 This allows users to implement a spatial <a 
href="https://docs.rs/parquet/latest/parquet/arrow/arrow_reader/struct.RowFilter.html";><code>RowFilter</code></a>
 directly on an upstream builder instance. It also allows low-level access, so 
that if a user wanted a spatial filter <em>plus</em> something else, that would 
be doable.</p>
   </li>
   <li>
   <p>Allows user to choose when the WKB column should be parsed to a native 
GeoArrow type or not in the <code>geoarrow_schema</code> method. (the 
<code>parse_to_native</code> parameter)</p>
   </li>
   <li>
   <p><strong>Keeps wrapper structs for readers</strong>. So we still have a 
<code>GeoParquetRecordBatchReader</code> and a 
<code>GeoParquetRecordBatchStream</code>, but these are <em>very 
lightweight</em> wrappers.</p>
   <p>The benefit of having these wrapper structs is that we can ensure 
GeoArrow metadata is always applied onto the emitted 
<code>RecordBatch</code>es.</p>
   </li>
   </ul>
   </li>
   <li>Refactor of GeoParquetReaderMetadata and GeoParquetDatasetMetadata <a 
href="https://redirect.github.com/geoarrow/geoarrow-rs/issues/1172";>#1172</a>
   <ul>
   <li>Remove <code>Option</code> for the geospatial metadata of each 
<code>GeoParquetReaderMetadata</code> and 
<code>GeoParquetDatasetMetadata</code>. We assume that if the user is using the 
<code>geoparquet</code> crate, all files will have valid GeoParquet 
metadata.</li>
   </ul>
   </li>
   <li>Remove GeoParquet writer wrappers and just expose encoder <a 
href="https://redirect.github.com/geoarrow/geoarrow-rs/issues/1214";>#1214</a>
   <ul>
   <li>Similar to how we refactored the read side (<a 
href="https://redirect.github.com/geoarrow/geoarrow-rs/pull/1089";>geoarrow/geoarrow-rs#1089</a>,
 <a 
href="https://redirect.github.com/geoarrow/geoarrow-rs/pull/1172";>geoarrow/geoarrow-rs#1172</a>),
 this PR changes the writing APIs of the <code>geoparquet</code> crate to only 
provide <em>additive</em> APIs to the upstream <code>parquet</code> crate. So 
this is now intended to be used <em>in conjunction with</em> the upstream 
<code>parquet</code> crate, not exclusively of it.</li>
   </ul>
   </li>
   <li>Add support for writing covering column to GeoParquet <a 
href="https://redirect.github.com/geoarrow/geoarrow-rs/issues/1216";>#1216</a>
   <ul>
   <li>Add support for generating the a bounding box covering column while 
writing data.</li>
   <li>Reconfigure writer properties generation. This takes inspiration from 
the upstream <code>parquet</code> properties generation, and has both 
<em>column</em> specific properties and <em>default</em> properties. So you can 
set the encoding for <em>all</em> columns but you can also override the 
encodings for specific columns.</li>
   </ul>
   </li>
   <li>Allow passing primary column to parquet writer <a 
href="https://redirect.github.com/geoarrow/geoarrow-rs/issues/1159";>#1159</a></li>
   <li>Correctly set geometry types in GeoParquet metadata when writing <a 
href="https://redirect.github.com/geoarrow/geoarrow-rs/issues/1218";>#1218</a></li>
   </ul>
   <h2>[0.4.0] - 2025-05-28</h2>
   <p>This release contains more or less a <strong>full rewrite</strong> of the 
GeoArrow Rust library.</p>
   <blockquote>
   <p>The <code>geoarrow-rs</code> project is about 3 years old. Early 
prototyping started inside the <a 
href="https://github.com/geopolars/geopolars";><code>geopolars</code></a> repo 
before deciding I needed something more general (not tied to Polars) and 
creating first <a 
href="https://github.com/geopolars/geoarrow";><code>geopolars/geoarrow</code></a>
 and then lastly <a 
href="https://github.com/geoarrow/geoarrow-rs";><code>geoarrow/geoarrow-rs</code></a>.</p>
   <p>However despite its age, the <code>geoarrow</code> crate suffers from a 
couple issues. For one, it took a while to figure out the right abstractions. 
And learning Rust at the same time didn't help. The <code>geoarrow</code> crate 
is also too monolithic. Some parts of <code>geoarrow</code> are production 
ready, but there's decidedly a <em>lot</em> of code in <code>geoarrow</code> 
that is <em>not</em> production ready. And it's very much not clear which parts 
of <code>geoarrow</code> are production ready or not.</p>
   <p>But I think <code>geoarrow-rs</code> has potential to form part of the 
core geospatial data engineering stack in Rust. And as part of that, we need a 
better delineation of which parts of the code are stable or not. As such, the 
<code>geoarrow-rs</code> repo is <strong>currently ongoing a large refactor 
from a single crate to a monorepo of smaller crates, each with a more 
well-defined scope</strong>.</p>
   </blockquote>
   <!-- raw HTML omitted -->
   </blockquote>
   <p>... (truncated)</p>
   </details>
   <details>
   <summary>Commits</summary>
   <ul>
   <li><a 
href="https://github.com/geoarrow/geoarrow-rs/commit/9118a435095bef58f7067bc5a94d8dd1a01b1cd6";><code>9118a43</code></a>
 ci: Install GEOS as dev dependency in publish script (<a 
href="https://redirect.github.com/geoarrow/geoarrow-rs/issues/1429";>#1429</a>)</li>
   <li><a 
href="https://github.com/geoarrow/geoarrow-rs/commit/44be55b2a4625c8ab43808d9d07dfdd927415afb";><code>44be55b</code></a>
 chore: Bump to 0.8 (<a 
href="https://redirect.github.com/geoarrow/geoarrow-rs/issues/1428";>#1428</a>)</li>
   <li><a 
href="https://github.com/geoarrow/geoarrow-rs/commit/c85fa7bcca19719f62b560cd53c2a950ee58e52d";><code>c85fa7b</code></a>
 ci: Set up rust trusted publishing (<a 
href="https://redirect.github.com/geoarrow/geoarrow-rs/issues/1426";>#1426</a>)</li>
   <li><a 
href="https://github.com/geoarrow/geoarrow-rs/commit/234c7bd287b3e3caaa9ece9e67e81259347121f8";><code>234c7bd</code></a>
 chore: update to arrow v58 (<a 
href="https://redirect.github.com/geoarrow/geoarrow-rs/issues/1424";>#1424</a>)</li>
   <li><a 
href="https://github.com/geoarrow/geoarrow-rs/commit/b3e473e142b30d2ba97276c9813c1fa41fc6a53a";><code>b3e473e</code></a>
 feat: Use <code>LazyLock</code> for constructing coordinate 
<code>DataType</code> instances (<a 
href="https://redirect.github.com/geoarrow/geoarrow-rs/issues/1420";>#1420</a>)</li>
   <li><a 
href="https://github.com/geoarrow/geoarrow-rs/commit/c5a8378e2ae425d7e015057264406d0fd2b8b63f";><code>c5a8378</code></a>
 docs: Add Geoparquet Example (<a 
href="https://redirect.github.com/geoarrow/geoarrow-rs/issues/1411";>#1411</a>)</li>
   <li>See full diff in <a 
href="https://github.com/geoarrow/geoarrow-rs/compare/rust-v0.7.0...rust-v0.8.0";>compare
 view</a></li>
   </ul>
   </details>
   <br />
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=geoarrow-schema&package-manager=cargo&previous-version=0.7.0&new-version=0.8.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
   
   Dependabot will resolve any conflicts with this PR as long as you don't 
alter it yourself. You can also trigger a rebase manually by commenting 
`@dependabot rebase`.
   
   [//]: # (dependabot-automerge-start)
   [//]: # (dependabot-automerge-end)
   
   ---
   
   <details>
   <summary>Dependabot commands and options</summary>
   <br />
   
   You can trigger Dependabot actions by commenting on this PR:
   - `@dependabot rebase` will rebase this PR
   - `@dependabot recreate` will recreate this PR, overwriting any edits that 
have been made to it
   - `@dependabot show <dependency name> ignore conditions` will show all of 
the ignore conditions of the specified dependency
   - `@dependabot ignore this major version` will close this PR and stop 
Dependabot creating any more for this major version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this minor version` will close this PR and stop 
Dependabot creating any more for this minor version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this dependency` will close this PR and stop 
Dependabot creating any more for this dependency (unless you reopen the PR or 
upgrade to it yourself)
   
   
   </details>


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to