Microsoft.Spatial vs. NetTopologySuite vs. OData - which combination to use for 8.0.0?
@gathogojr is already working on this.
Since Dec 9, 2025.
- Dominant language
- C#
- Stars
- 505
- Forks
- 186
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
Currently we are using the NetToplogySuite library with EF Core and everything works fine, except we cannot use OData with these properties. We simply want to be able to query for objects which contain points and polygons and successfully retrieve them. If we could use OData to spatially query that would be great, but a bonus for now.
A typical property on a model looks like
public Geometry Position { get; set; }
I have opened another issue about serializing the Geometry object, but I want to be sure we are doing things the "right way". I see the Microsoft.Spatial library is brought in by the OData stuff, is this an alternative to NetTopology we should be using? Does it offer the same functionality but in a way that works with OData?
The Microsoft docs (and a blog post by @xuzhg) seem to use Microsoft.Spatial, but the documents are all targeting the older libraries and do not appear to be relevant.
Any help greatly required!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.