Add spatialdata-experimental-writer Python package - #76
Conversation
- Added `pyproject.toml` for package configuration, including dependencies and build system. - Created `README.md` with an overview of the experimental vector optimization writers for SpatialData. - Implemented core functionality in `src/spatialdata_experimental_writer`, including Morton sorting and multiscale Parquet writing. - Developed command-line interface in `cli.py` for various operations on SpatialData. - Introduced Zarr integration for reading and writing points data. - Added tests for key functionalities in `tests/test_points.py` and `tests/test_zarr.py`. - Established package structure with necessary modules and scripts.
- Updated README.md to include detailed installation instructions and command usage for the experimental writer. - Added a new script for benchmarking points index permutations, allowing users to evaluate performance based on index-manifest.json. - Implemented a new CLI command for writing derivative Zarr stores with transcript index sort permutations. - Introduced consolidated metadata registration for points elements in Zarr stores. - Enhanced morton sorting functionality to support custom sort orders and ensure uint columns are not persisted in output Parquet files. - Added integration tests to validate new features and ensure correct functionality across the package.
- Added a new Textual User Interface (TUI) for an interactive workflow, allowing users to execute commands in a guided manner. - Updated `pyproject.toml` to include `textual` as a dependency for TUI functionality. - Update the README with instructions for using the TUI, including command execution and verification checks. - Refactored CLI commands to utilize new runner functions for improved organization and maintainability. - Introduced verification checks for Morton and multiscale parquet outputs to ensure data integrity. - Added unit tests for verification functions to validate their correctness and reliability.
Add InputFormScreen and refactor Existing Screens - Introduced InputFormScreen as a base class for form handling, enabling consistent input navigation and submission across multiple screens. - Refactored ZarrPathScreen, MortonFromZarrScreen, MortonFileScreen, MultiscaleScreen, and IndexPermutationsScreen to inherit from InputFormScreen, streamlining input management. - Implemented action handling for back navigation and primary button submission in the new InputFormScreen. - Enhanced user experience by ensuring focus transitions between input fields based on user input submission.
|
Warning Review limit reached
Next review available in: 59 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (19)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Harvested from the larger points-loading branch as a self-contained slice. This package does not touch the TS render path and main never referenced it, so it applied as 8 clean cherry-picks off
main.New Python package
python/spatialdata-experimental-writer(note that we will follow-up at some point by merging image codec writing into this, possibly with a different name, and publish to pypi):morton_code_2d,{feature_key}_codes, controlled row groups, sentinel bbox rows). See ADR 0002.write-index-permutationsbenchmark tooling for comparing sort strategies (spatial Morton vs. feature-primary vs. compound) on a derivative Zarr store.Notes:
uvenv); it was green on the source branch.🤖 Generated with Claude Code