epic: new docs pages

[MrPowers]

We aim to create documentation pages that showcase the capabilities of the SedonaDB engine, assist LLMs in providing more accurate answers, and educate users on the engine's interoperability.

Here are the different categories and docs pages to add:

Integrations:

• geopandas
• unity-catalog

Storage:

• geoparquet
• deltalake
• iceberg
• flatgeobuf
• postgis

Compute platforms:

• google-colab (ref: docs: SedonaDB + Google Colab doc instructions #118)
• aws-lambda (ref: docs: SedonaDB + AWS Lambda #119)
• aws-sagemaker
• databricks

[aritracodes-69]

I would like to contribute

[MrPowers]

@aritracodes-69 - any pages you'd like to write in particular?

[Mehak3010]

Hi There,

I’m interested in contributing to this issue and would like to clarify a few things before starting.

From the description, I understand this issue focuses on adding new documentation pages for different integrations and platforms. However, I’m not fully clear about:

1. Which folder/path should be used for adding these new docs pages
2. Whether there is a preferred structure or template to follow
3. If it’s okay to start with a single page (for example, GeoPandas or Delta Lake) instead of covering multiple pages in one PR

Could you please point me to an existing documentation page that would be a good reference
and the recommended page to start with this contribution.

I want to make sure my work aligns with the expected structure before opening a PR.

[paleolimbot]

I’m interested in contributing to this issue

Great!

Which folder/path should be used for adding these new docs pages

https://github.com/apache/sedona-db/tree/main/docs should do it!

Whether there is a preferred structure or template to follow

You can see the previous work in that folder. These pages are written as Jupyter notebooks (.ipynb) and are rendered automatically into .md files when you run ci/scripts/build-docs.sh. A good reference is https://github.com/apache/sedona-db/blob/main/docs/README.md .

If it’s okay to start with a single page

Yes, one page at a time is preferred. GeoPandas and DeltaLake are already complete and PostGIS + GeoParquet would be the next two highest priority! There is an older PR for PostGIS ( #459 ) that you can feel free to copy and modify.

[Mehak3010]

I’ve opened a new PR that addresses this issue by adding a PostGIS integration guide for SedonaDB.

The guide covers both:

1. a GeoPandas-based workflow for simplicity and exploratory use, and
2. a high-performance ADBC-based workflow using adbc_ingest() and fetch_arrow() for more efficient data transfer.

This work builds on the intent of #459, updates it to the current documentation structure, and extends it with the ADBC approach.

Happy to adjust or refine things based on feedback.