Open otan opened 4 years ago
Was it an oversight that the spheroid
argument to ST_DistanceSpheroid
isn't implemented (if I read your commit correctly)?
I'm seeing unknown signature: st_distancespheroid(geometry, geometry, string)
for a query like:
SELECT ...
FROM "distapp_australiacity"
WHERE ST_DistanceSpheroid(
"distapp_australiacity"."point",
ST_GeomFromEWKB('\x0101000020e6100000c3f5285c8f6a6240f0164850fc7045c0'::bytea),
'SPHEROID["WGS 84",6378137.0,298.257223563]'
) <= ("distapp_australiacity"."radius" * 70)
Oops
Implement
ST_DistanceSpheroid
on arguments {geometry,geometry,spheroid}, which should adopt PostGIS behaviour.Observers: Please react to this issue if you need this functionality.
For Geometry builtins, please do the following:
pkg/geo/geomfn
(parse and output related functions can go inpkg/geo
). Add exhaustive unit tests here - you can run through example test cases and make sure that PostGIS and CRDB return the same result within a degree of accuracy (1cm for geography).pkg/sql/sem/builtins/geo_builtins.go
. Note that we currently do not support optional arguments, so we define functions that have optional arguments once without the optional argument (using the default value in the optional position), and once with the optional argument.pkg/sql/logictest/testdata/logic_test/geospatial
to call this functionality at least once. You can callmake testbaselogic FILES='geospatial' TESTFLAGS='-rewrite'
to regenerate the output. Tests here should just ensure the builtin is linked end to end (your exhaustive unit tests go the above mentioned packages!).make buildshort
. You can also play with it by calling./cockroach demo --empty
afterwards.You can follow #48552 for an example PR.
The following additional guidance has been issued on implementing this function:
use PROJ library to interpret spheroid
:robot: This issue was synced with a spreadsheet by gsheets-to-github-issues by otan on 2023-09-03T23:16:38Z. Changes to titles, body and labels may be overwritten.