7,594 reputation
1227
bio website cleverelephant.ca
location Victoria, Canada
age 43
visits member for 3 years, 11 months
seen Jul 23 at 18:30

merge keep


Jul
19
reviewed Approve suggested edit on How do I peform a true GIS Clip of polygons layer using a polygon layer in R
Jul
11
reviewed Approve suggested edit on Python query to find records with more than one alpha character in a field
Jul
11
revised How to union polygons and add attribute values of combined output features
deleted 7 characters in body
Jul
11
revised Empty geometries in GEOMETRYCOLLECTION
added 748 characters in body
Jul
11
comment Empty geometries in GEOMETRYCOLLECTION
The most complete discussion of EMPTY is the one we wrote up when moving to 2.0 and more complete EMPTY handlings, trac.osgeo.org/postgis/wiki/DevWikiEmptyGeometry, and it doesn't say much about representation (what you'd care about), it talks more about behavior.
Jul
11
comment Empty geometries in GEOMETRYCOLLECTION
I'll have to check into the parser and see why a collection of empties is not being handled, since naively I'd expect it to just work, but I'm sure there's something in there... it's hard to escape one's history.
Jul
11
comment Empty geometries in GEOMETRYCOLLECTION
The hex you see on the output is itself just another representation format ("extended well-known-binary") which itself has the limitations of WKB, so you're seeing the hack we adopted for POINT EMPTY in WKB. Internally we can and do represent POINT EMPTY as a distinct thing.
Jul
11
comment How to union polygons and add attribute values of combined output features
It probably won't work in practice because I've found the "decompose to lines, rebuild to polygons" step to be inconsistent in regenerating the same areas as were input.
Jul
11
answered How to union polygons and add attribute values of combined output features
Jul
11
reviewed Approve suggested edit on How to define Winkel Tripel in proj 4.8.0?
Jul
11
answered Empty geometries in GEOMETRYCOLLECTION
Jul
10
revised Postgis: Traslate geometry from EPSG:23030 to EPSG:21818, then to lat long
added 1 character in body
Jul
9
revised Postgis: Traslate geometry from EPSG:23030 to EPSG:21818, then to lat long
added 500 characters in body
Jul
9
revised Postgis: Traslate geometry from EPSG:23030 to EPSG:21818, then to lat long
deleted 716 characters in body
Jul
9
comment Postgis: Traslate geometry from EPSG:23030 to EPSG:21818, then to lat long
Well, the second attempt came closer at least (right continent). Any other clues as to what projection the originators thought it was?
Jul
9
answered Postgis: Traslate geometry from EPSG:23030 to EPSG:21818, then to lat long
Jul
8
answered Run PostGIS command line functions in pgAdmin?
Jul
2
answered Can't get SRS from PostGIS using Proj4 text
Jun
30
answered Does PostGIS have separate implementation of GiST index from PostgreSQL?
Jun
22
comment in mapserver, how would i style polygons differently based on a seperated points layer?
For point-in-polygon intersects and contains return identical results. Thanks!