Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for Curve types / v2 support #9

Open
dotMorten opened this issue Oct 16, 2018 · 3 comments
Open

Add support for Curve types / v2 support #9

dotMorten opened this issue Oct 16, 2018 · 3 comments
Labels
enhancement New feature or request

Comments

@dotMorten
Copy link
Owner

dotMorten commented Oct 16, 2018

v2 adds an optional segments part:
image

Segments (optional) (1 * Number of Segments bytes) (variable): In version 2 of the serialization format, a sequence of segment structures

image

This was referenced Oct 8, 2020
@dotMorten dotMorten changed the title Add support for Curve types Add support for Curve types / v2 support Oct 8, 2020
@dotMorten dotMorten added the enhancement New feature or request label Oct 8, 2020
@alexpantyukhin
Copy link

Is there any news with this issue?

@dotMorten
Copy link
Owner Author

Issue still open and no one has submitted a PR to address it 🤷

@alexpantyukhin
Copy link

alexpantyukhin commented May 23, 2022

@dotMorten

I try the following approach:

on the SQL side:

    SELECT 
          geography_field.STAsText() geography_field
    FROM mytable

on the code side:

   var strValue = ((SqlDataReader)reader).GetSqlString(geographyFieldPosition);
   var sqlGeographyFromReader = SqlGeography.Parse(binvalue);

I found that in this case the georaphy is restored. Also I found that there is no soe flags which related with version in text when call STAsText(). Could it be the correct approach?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants