-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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: SpatialObjectToWKT() omits empty shapes in collections #53632
Comments
Hello, I am Blathers. I am here to help you get the issue triaged. Hoot - a bug! Though bugs are the bane of my existence, rest assured the wretched thing will get the best of care here. I have CC'd a few people who may be able to assist you:
If we have not gotten back to your issue within a few business days, you can try the following:
🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is otan. |
It's this if condition in go-geom -- https://github.com/twpayne/go-geom/blob/master/encoding/wkt/encode.go#L96 -- it should be changed to Feel free to change it, if not I'll get to it on Monday. |
Opened a go-geom PR here: twpayne/go-geom#184 |
53556: builtins: add in unimplemented spatial builtins r=sumeerbhola a=otan This adds telemetry to remaining unused functions, as well as displaying the issue number when someone attempts to use an unimplemented function. Also changed the wording of the error message to be a little more friendly. Release justification: low risk, high benefit changes Release note: None 53600: build: fix TESTS env variable in roachtest nightly script r=jlinder a=adityamaru AWS TC nightly fails with `unbound variable TESTS`. This change initializes it outside the if condition. Release justification: non-production code changes 53604: telemetry: fix the integer quantization r=irfansharif a=knz The code was previously quantizing 100 to 10, and only 101 and higher to 100. This patch fixes it. Additionally, this code ensures that negative values also get quantized. This change does not impact any caller for now (there is no caller that expects negative value) but will be used in an upcoming setting telemetry change. Release justification: low risk, high benefit changes to existing functionality Release note: None 53643: builtins: implement ST_ForceCollection r=otan a=erikgrinaker Some test cases deviate from PostGIS due to a bug in the WKT encoder (see #53632). The behavior of `ST_ForceCollection` is correct, but the WKT output does not accurately represent the resulting geometry. Not sure if we should wait for the upstream fix or merge this as-is. Release justification: low risk, high benefit changes to existing functionality Release note (sql change): Implement the geometry builtin `ST_ForceCollection`. Closes #48934. 53656: roachtest: ignore version upgrade no inbound stream connection error r=irfansharif a=asubiotto Release justification: non-production code change This error is fixed in 20.2, but may occur on earlier versions because version upgrade is a mixed-version test. Release note: None (testing change) Closes #53393 Co-authored-by: Oliver Tan <[email protected]> Co-authored-by: Aditya Maru <[email protected]> Co-authored-by: Raphael 'kena' Poss <[email protected]> Co-authored-by: Erik Grinaker <[email protected]> Co-authored-by: Alfonso Subiotto Marques <[email protected]>
Describe the problem
While implementing
ST_ForceCollection
, I have a test case which generates a geometry collection with an empty point. However, callinggeo.SpatialObjectToWKT
omits the empty point from the output.To Reproduce
This yields a test failure:
PostGIS can represent this just fine:
Environment:
master
at8b91062f93
cockroach demo
CC @otan
The text was updated successfully, but these errors were encountered: