jiayuasu opened a new pull request, #2802: URL: https://github.com/apache/sedona/pull/2802
## Did you read the Contributor Guide? - Yes, I have read the [Contributor Rules](https://sedona.apache.org/latest/community/rule/) and [Contributor Development Guide](https://sedona.apache.org/latest/community/develop/) ## Is this PR related to a ticket? - Yes, and the PR name follows the format `[GH-XXX] my subject`. Closes #2769 ## What changes were proposed in this PR? Restructure and improve the raster loader, writer, and visualization documentation: - **SQL Overview page**: Added a "Raster function list" section so rasters are discoverable from the main SQL entry point - **Raster tutorial**: Rewrote "Load data" to lead with the `raster` data source for GeoTiff (instead of the deprecated `binaryFile` approach). Moved `binaryFile` to a secondary section for non-GeoTiff formats (NetCDF, Arc Grid). Expanded "Save to permanent storage" with writer options table and step-by-step guide. Clarified that `tileWidth`/`tileHeight` are optional. - **New individual function pages**: Created `RS_AsArcGrid`, `RS_AsGeoTiff`, `RS_AsPNG`, `RS_AsCOG`, and `RS_AsRaster` pages under `Raster-Output/`, consistent with the existing per-function doc pattern - **Raster-Functions.md index**: Added all 5 new functions to the appropriate tables - **Removed `Raster-loader.md` and `Raster-writer.md`**: All content absorbed into the tutorial and individual function pages - **mkdocs.yml**: Removed the two deleted nav entries - **Fixed cross-links**: Updated all references (including in the Jupyter notebook) to point to new locations ## How was this patch tested? Ran `mkdocs serve` locally and verified: - All pages render correctly with no new warnings - All cross-links resolve - Nav structure is clean ## Did this PR include necessary documentation updates? - Yes, I have updated the documentation. -- 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]
