Microsoft.SqlServer.Types
a .NET Standard implementation of the spatial types in Microsoft.SqlServer.Types
Difference between v1.x and v2.x
The v1.x and v2.x versions are identical and kept in sync. The only difference is the dependency:
- v1.x : Depends on the legacy
System.Data.SqlClient
package. - v2.x : Depends on updated
Microsoft.Data.SqlClient
package.
Sponsoring
If you like this library and use it a lot, consider sponsoring me. Anything helps and encourages me to keep going.
See here for details: https://github.com/sponsors/dotMorten
NuGet:
Install the package dotMorten.Microsoft.SqlServer.Types
from NuGet.
Examples
Input parameter
Assigning SqlGeometry or SqlGeography to a command parameter:
command.Parameters.AddWithValue("@GeographyColumn", mySqlGeography);
command.Parameters["@GeometryColumn"].UdtTypeName = "Geography";
command.Parameters.AddWithValue("@GeographyColumn", mySqlGeometry);
command.Parameters["@GeometryColumn"].UdtTypeName = "Geometry"
The geometry will automatically be correctly serialized.
Reading geometry and geography
Use the common methods for getting fields of specific types:
var geom1 = reader.GetValue(geomColumn) as SqlGeometry;
var geom2 = reader.GetFieldValue<SqlGeometry>(geomColumn);
var geom3 = SqlGeometry.Deserialize(reader.GetSqlBytes(geomColumn)); //Avoids any potential assembly-redirect issue. See https://docs.microsoft.com/en-us/previous-versions/sql/2014/sql-server/install/warning-about-client-side-usage-of-geometry-geography-and-hierarchyid?view=sql-server-2014#corrective-action
Notes:
The spatial operations like intersection, area etc are not included here. You can perform these as part of your query instead and get them returned in a column.