Skip to content

Conversation

@MrPowers
Copy link
Collaborator

No description provided.

Copy link
Member

@paleolimbot paleolimbot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like pre-commit has something to say about this.

The example from the release post would be good to include here...the ability to do a partial read of a remote FlatGeoBuf is a great feature ( https://sedona.apache.org/latest/blog/2025/12/01/sedonadb-020-release/#gdalogr-spatial-file-format-read-support ). This won't work for the Microsoft Buildings example (or any of the GeoArrow data fgb files) because they don't contain spatial indexes (I wrote them this way to keep them under the 2GB GitHub releases limit).

Comment on lines +44 to +48
```python
url = "https://github.com/geoarrow/geoarrow-data/releases/download/v0.2.0/microsoft-buildings_point.fgb.zip"
df = sd.read_pyogrio(url)
df.show(3)
```
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm surprised that this loads quickly!

sd = sedona.db.connect()
```

# Read Microsoft Buildings FlatGeobuf data with SedonaDB
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
# Read Microsoft Buildings FlatGeobuf data with SedonaDB
## Read Microsoft Buildings FlatGeobuf data with SedonaDB


Now lets see how to read another FlatGeobuf dataset.

# Read Vermont boundary FlatGeobuf data with SedonaDB
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
# Read Vermont boundary FlatGeobuf data with SedonaDB
## Read Vermont boundary FlatGeobuf data with SedonaDB

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants