3

I am trying to use ST_ReducePrecision to reduce the number of characters, because of the character limit in power bi cells.

ST_AsText(ST_ReducePrecision(ST_Transform(geom, 4326), 0.000001))

The result that I'm geting is not what I was expecting:

Original WKT: MULTIPOLYGON(((-42.49076772971744 -22.940101731323654,-42.492057937951515 -22.9399517863236,-42.492703038099 -22.93987681565973,...

Using ST_ReducePrecision: MULTIPOLYGON(((-42.492058 -22.939951999999998,-42.492703 -22.939877,-42.493992999999996 -22.939726999999998,...

Expected result: MULTIPOLYGON(((-42.490768 -22.940102,-42.492058 -22.939952,-42.492703 -22.939877,...

1
  • Welcome to GIS SE. As a new user, please take the Tour. Unfortunately, your expectation is incorrect. The precision of the data did change, but that does not change unformatted presentation in ST_AsText.
    – Vince
    Dec 6, 2023 at 12:59

2 Answers 2

5

This is a GEOS bug that was fixed recently in GEOS-956. It's in GEOS 3.12.1, so upgrading might solve this problem.

4

ST_ReducePrecision changes the precision of the numeric values.

Floating point numbers are hard for computers so when you want them as text, weird issues can occur.

Try ST_AsText's maxdecimaldigits parameter in addition to it.

4
  • 1
    ST_ReducePrecision also ensures that reducing the precision of polygonal inputs maintains correct topology so that the output is valid.
    – dr_jts
    Dec 6, 2023 at 20:51
  • Oh nice, i edited my answer. Would st_reduceprecision always lead to st_astext using its precision once the geos bug is fixed? Dec 6, 2023 at 21:49
  • 1
    Yes, it should.
    – dr_jts
    Dec 7, 2023 at 0:45
  • Thank you, I think I solved the problem using ST_AsEWKT: ST_AsText(ST_AsEWKT(ST_Transform(geom, 4326), 6)) Is this ok? Dec 7, 2023 at 12:15

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.