Repository navigation
Improve provider and format compatibility across vectors, terrain and imagery - #8
Merged
Merged
Conversation
PascalNun
changed the base branch from
codex/medium-source-compatibility
to
main
November 2, 2026 08:13
PascalNun
marked this pull request as ready for review
November 2, 2026 08:13
PascalNun
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes
Improve provider and format compatibility through the existing Grasshopper components and shared Spatial Context. This integration contains all three completed compatibility batches:
Save implementation plans, how-to guides, public URLs/test bounds and reproducible fixtures. Correct GDAL ASCII NoData parsing and add explicit WGS84 UTM transformations required by the live imagery source.
Validation
The exact integrated head
55eae6fpassed Release build and all nine suites on macOS and Windows, including 26 source-compatibility, 27 medium-priority and 43 low-priority cases. Live provider/file probes, component identity/parameter checks, source-catalogue validation and package/dependency/license inspection are recorded in the plans and examples.Native Rhino/Grasshopper visuals, materials/bake, saved definitions and installed-package assembly resolution remain manual checks in
examples/VALIDATION.md; sandbox CI does not prove those surfaces.Compatibility
Main was fast-forwarded to the tested commit, preserving the three original commits and automatically merging #6, #7 and this PR. This PR was retargeted to main for that integration and its final diff includes all three batches.
Component names/GUIDs/input-output order, normal connections, shared localization, elevation baseline and metadata-only reference behavior are retained. Managed image/SQLite dependencies and platform providers have package notices; no new native SQLite library is bundled. Unsupported formats/extensions and size limits fail explicitly.
No public version bump, release publication, Food4Rhino change or installed-plugin replacement. Public/installed 0.4.0 remains unchanged. See the three compatibility plans and example guides for workflows and limitations.