Paul Ramsey
Paul Ramsey
As a PostGIS guy, this leaves me cold. The only win is for use cases where they are wrapping and using things like Area() and Length() and Distance() frequently, which......
@dbaston, is this a go or a no?
Like @dbaston I hate mucking around in the initializers, because the knock-on effects are subtle. I defer to him as usual.
For XY coordinate sequences, imposing an XYZM struct on top would read out of bounds for the last coordinates X and M values. For internally managed buffers we could just...
This seems to be limited to x86_64, I am not seeing it on aarm64. (My timing on selling my old x86 macbook is poor in this case.)
Start by examining your data. It looks like the column metadata does not include an SRID, but does the geometry itself carry an SRID? What does `ST_Srid(the_geom) LIMIT 1` return...
So, it would be nice if the TIGER import correctly set the SRID of the column (@robe2), I wonder why that doesn't happen. Strange that it gets set on tabblock...
You can manually fix your proximate problem just be altering the table definition. ``` ALTER TABLE foo ALTER COLUMN the_geom TYPE Geometry(Point, 4269) ```
Mix in the type you need as necessary :)
What if you use `FID` as the name of your PK?