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

geo/geomfn: implement ST_FlipCoordinates({geometry}) #48932

Closed
otan opened this issue May 14, 2020 · 4 comments · Fixed by #53296
Closed

geo/geomfn: implement ST_FlipCoordinates({geometry}) #48932

otan opened this issue May 14, 2020 · 4 comments · Fixed by #53296
Labels
A-geometry-builtins Builtins which have geometry as args. C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) E-easy Easy issue to tackle, requires little or no CockroachDB experience X-nostale Marks an issue/pr that should be ignored by the stale bot

Comments

@otan
Copy link
Contributor

otan commented May 14, 2020

Implement ST_FlipCoordinates on arguments {geometry}, which should adopt PostGIS behaviour.

Observers: Please react to this issue if you need this functionality.

For Geometry builtins, please do the following:

  • Ideally add a relevant helper function in pkg/geo/geomfn (parse and output related functions can go in pkg/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).
    • When using GEOS, you can reference the C API for which functions are available. Unfortunately, Windows is not currently supported when using GEOS.
  • Create a new builtin that references this function in 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.
  • Modify the tests in pkg/sql/logictest/testdata/logic_test/geospatial to call this functionality at least once. You can call make 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!).
  • Ensure the documentation is regenerated by calling make buildshort. You can also play with it by calling ./cockroach demo --empty afterwards.
  • Submit your PR - make sure to follow the guidelines from creating your first PR.

You can follow #48552 for an example PR.

🤖 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.

@otan otan added A-geometry-builtins Builtins which have geometry as args. C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) labels May 14, 2020
@otan otan changed the title geo/geomfn: implement ST_Flipcoordinates({geometry}) geo/geomfn: implement ST_FlipCoordinates({geometry}) May 14, 2020
@otan otan added the E-easy Easy issue to tackle, requires little or no CockroachDB experience label May 14, 2020
@themistoklik
Copy link
Contributor

Can I work on this?

@otan
Copy link
Contributor Author

otan commented Aug 22, 2020 via email

@themistoklik
Copy link
Contributor

themistoklik commented Aug 23, 2020

Used reverse as a guide to compensate for no Go/GIS experience.

Linters + Local unit/logic tests pass but getting timeouts on the big ones that ran with make check or make pre-push so I'm not gonna open a PR just yet, since I got no idea why the fails occur.

  1. My change is here temporarily. I wanted to check if you think I should PR nonetheless or you wanted to take a quick scan at my change first.
  2. PostGIS doc mentions support for M/Z indices and various surfaces that I do not immediately see supported in the codebase. In the unit test for reverse I only saw 2d geometries being tested, so I went ahead and did the same for my command. Combine that with this, I thought 2d is supported only, still wanted the assumption validated. Is the 2d testing only OK?

@otan
Copy link
Contributor Author

otan commented Aug 23, 2020 via email

@craig craig bot closed this as completed in 62214d5 Aug 25, 2020
@otan otan added the X-nostale Marks an issue/pr that should be ignored by the stale bot label Sep 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-geometry-builtins Builtins which have geometry as args. C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) E-easy Easy issue to tackle, requires little or no CockroachDB experience X-nostale Marks an issue/pr that should be ignored by the stale bot
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants