Open corranrogue9 opened 2 years ago
This might be a good candidate for a library to move to: https://docs.microsoft.com/en-us/ef/core/modeling/spatial#nettopologysuite
This is a blog post for translating between Microsoft.Spatial and EF: https://devblogs.microsoft.com/odata/customizing-filter-for-spatial-data-in-asp-net-core-odata-8/
URI parsing might be impacted significantly and the impact on WebApi should also be considered.
We should investigate if customers are actually needing to translate between Microsoft.Spatial
types and other types. We might also want to consider that Microsoft.Spatial
is the only ODL project that only depends on .NET; we may think about introducing an additional project to house all of the ".NET only" code that is shared in ODL.
Microsoft.Spatial
is rarely changed and there are other public packages that we could use to replace it. We should investigate replacing it, and if we choose not to, we should not release a new version if nothing has changed.