Add support for Point, LineString, and Polygon geospatial types#2283
Merged
Conversation
The Coordinate type has been superseded by Point, LineString, and Polygon from Cratis.Geospatial. Remove all Coordinate-related serializers, specs, and documentation to simplify the codebase.
Implement BSON serializers for geospatial types following GeoJSON format: - PointSerializer: Single geographic coordinates - LineStringSerializer: Routes and paths as ordered point sequences - PolygonSerializer: Geographic areas with optional interior boundaries All serializers support MongoDB's geospatial query operators via 2dsphere indexes.
Support Point, LineString, and Polygon in Entity Framework Core with: - PointColumn, LineStringColumn, PolygonColumn extension methods for migrations - AsPoint, AsLineString, AsPolygon extension methods for property configuration - Cross-database compatibility (PostgreSQL jsonb, SQL Server/SQLite text) - JSON serialization for all geospatial types
Create dedicated documentation structure for geospatial support: - Entity Framework: Point, LineString, Polygon conversion guides - MongoDB: Dedicated geospatial folder with Point, LineString, Polygon serializers - Includes usage patterns, storage formats, querying examples, and best practices - Organized navigation with clear cross-references
- Update ProxyGenerator TypeExtensions to recognize Point as known type - Promote single-outcome spec files for Point (formerly nested in folders) - Update package versions in Directory.Packages.props - Update Arc package.json version
![github-code-quality[bot]](https://avatars.githubusercontent.com/u/9919?s=60&v=4){kind=small}
Comment on lines
+86
to
+88
| catch (EndOfStreamException) | ||
| { | ||
| } |
Comment on lines
+103
to
+105
| catch (EndOfStreamException) | ||
| { | ||
| } |
Comment on lines
+126
to
+128
| catch (EndOfStreamException) | ||
| { | ||
| } |
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
1 participant
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.
Summary
Replace the deprecated Coordinate type with comprehensive support for Point, LineString, and Polygon geospatial types across MongoDB and Entity Framework Core. All types follow the GeoJSON standard for compatibility with MongoDB spatial queries and external GIS tools.
Added
Changed
Fixed
Breaking Changes
None — Coordinate type removal was of an experimental type with no stable API.