You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have verified that I am running the latest version of NetTopologySuite
I have verified if the problem exist in both DEBUG and RELEASE mode
I have searched open and closed issues to ensure it has not already been reported
Description
Before inserting a polygon into a geography column, NTS checks that IsCCW is true. I want to insert an empty polygon, but haven't found a way to create one with IsCCW set to true. Perhaps NTS should not check the orientation for empty geometries? I am able to insert an empty polygon using raw SQL.
Needless to say, both approaches result in the same error: System.ArgumentException : When writing a SQL Server geography value, the shell of a polygon must be oriented counter-clockwise.
System Configuration
Tell us about the environment where you are experiencing the bug:
NetTopologySuite version: 2.3.0
Other NetTopologySuite packages and versions: Microsoft.EntityFrameworkCore.SqlServer.NetTopologySuite 6.0.1
Environment (Operating system, version and so on): Windows 10, MS SQL 15
.NET version: 6.0
The text was updated successfully, but these errors were encountered:
Prerequisites
DEBUG
andRELEASE
modeDescription
Before inserting a polygon into a geography column, NTS checks that IsCCW is true. I want to insert an empty polygon, but haven't found a way to create one with IsCCW set to true. Perhaps NTS should not check the orientation for empty geometries? I am able to insert an empty polygon using raw SQL.
Steps to Reproduce
Approach 1:
Approach 2:
Needless to say, both approaches result in the same error:
System.ArgumentException : When writing a SQL Server geography value, the shell of a polygon must be oriented counter-clockwise.
System Configuration
Tell us about the environment where you are experiencing the bug:
The text was updated successfully, but these errors were encountered: