[QUESTION] Make internal model public for SQLServerSpatialDatatype class
See original GitHub issueQuestion
I am working on a project where I need to translate a Geometry
object into another spatial class that implement a standard other than WKT/WKB.
I created a class that inherits from Geometry
in the same package as the Geometry
object. and I can access to figureList
field. But the mssql-jdbc jar is signed, I got an error. Is that possible to retrieve figures information with an another way ?
Issue Analytics
- State:
- Created 4 years ago
- Comments:14 (7 by maintainers)
Top Results From Across the Web
Spatial Data Types Overview - SQL Server - Microsoft Learn
SQL Server spatial tools is a Microsoft sponsored open-source collection of tools for use with the spatial types in SQL Server. This project ......
Read more >Use strong spatial types option in model designer locked?
I'm targeting SQL Server Express 2012, if this is an issue i can switch to another edition as i'm not doing anything versions...
Read more >How to Make Sense of SQL Server Geography Data Type
To make sense of something new, we need to answer three fundamental questions: • What problems does it solve? The answer lies in...
Read more >Investigating the new Spatial Types in SQL Server 2008 - Part 1
In this post we take a look at the new spatial data type support in SQL server 2008. First, I will make a...
Read more >Spatial data types in SQL Server - SQLShack
We can understand the Spatial SQL data types in SQL Server along with its uses scenario by following this article.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@ulvii The Geometry class should not be an opaque container, but at least allow read access to the underlying geometry points and properties. As a result a user will be able to read the geometry and process it without turning it into a WKT format, which leaves out the SRID and Z/M-values of the coordinates according to your source code.
PR has been merged, closing issue.