SQLite \ .Net Topology Suite \ Distance() units?
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
Start by comparing EF Core 5.0.1's SQLite spatial translation for Distance() with the SQL Server STDistance() translation and the Spatialite distance functions described in the issue. Reproduce the WGS-84 three-point example using the two SQL queries shown; done means determining and implementing the correct meter-based behavior, with provider tests covering the result.
Written by the indexing model from the issue text.
Description
Is it possible to match up the functionality between SQLite and SQL Server regarding the spatial distance function?
WGS-84 Coord System, added 3 points: (1,1), (1, 2), (2, 2).
SQL Server
Calculating distances from first point - EF Core translates into spatial query using proper function STDistance()
Results are in meters, and are correct.
Sqlite
Calculating distances from first point - EF Core translates into spatial query to not the proper function.
See http://www.gaia-gis.it/gaia-sins/spatialite-sql-4.2.0.html SQL functions for distance relationships
It calls the first, which returns in angles.
There is a function underneath, that returns in meters.
I can replicate it directly in SQL browser by typing two different queries:
SELECT Distance(XXX, (SELECT YYY FROM XXX LIMIT 1)) FROM XXX;
and
SELECT Distance(XXX, (SELECT YYY FROM XXX LIMIT 1), 1) FROM XXX;
Include provider and version information
EF Core version: 5.0.1
Database provider: Microsoft.EntityFrameworkCore.Sqlite
Target framework: net5.0
Operating system: Version 16.9.6
- Dominant language
- C#
- Stars
- 14.8k
- Forks
- 3.4k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 134
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dotnet/efcore
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
-
customer-reported
Difficulty 5/5 Over a week Newbie friendliness 38/100
-
area-cosmos area-vector-search
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
area-cosmos
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
area-tools needs-design
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
:watch: Not Triaged 11.0 fundamentals/subsvc
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
dotnet/AspNetCore.Docs#37699 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
SubtitleEdit/subtitleedit#15108 · 1 comment ·
-
area/docs-content Bug pulumi/docs
Difficulty 1/5 1-3 hours Newbie friendliness 94/100
-
agentic-workflows untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 76/100