meta user
network profile
| bio | website | cleverelephant.ca |
|---|---|---|
| location | Victoria, Canada | |
| age | 42 | |
| visits | member for | 2 years, 9 months |
| seen | 4 mins ago | |
| stats | profile views | 494 |
merge keep
|
May 14 |
answered | PostGIS select by lat/long bounding box |
|
May 11 |
comment |
What is the best way to join lots of small polygons to form a larger polygon? You're right, the parenthesis was in the wrong place. Edited. |
|
May 11 |
revised |
What is the best way to join lots of small polygons to form a larger polygon? fix code syntax |
|
May 2 |
comment |
PostGIS not converting GIS data into latitude/longitude values Returns POINT(-119.641455676283 49.3703553898924), which seems to be close to Vancouver. |
|
May 2 |
comment |
PostGIS not converting GIS data into latitude/longitude values So a quick test: SELECT ST_AsText(ST_Transform(ST_SetSRID('POINT(1461547.22664562 504522.034305431)'::geometry,3005), 4326)); |
|
May 2 |
comment |
PostGIS not converting GIS data into latitude/longitude values Although, given your use of the term "PID" and your VanCity nick, I'd be willing to hazard that you actually want SRID = 3005 (BC Albers). |
|
May 2 |
answered | PostGIS not converting GIS data into latitude/longitude values |
|
May 1 |
answered | ST_MakeEnvelope returning too many geos |
|
May 1 |
comment |
What is the maximum number of vertices for polygons & polylines in PostGIS? This is correct, though the npoints counter is a signed integer (oh well), so you can "only" get 2 billion vertices in. |
|
Apr 29 |
answered | Assigning a nearest polygon to a point |
|
Apr 23 |
answered | Public PostGIS Server available? |
|
Apr 23 |
comment |
Identifying Intersections of Geology using PostGIS In these cases, a picture is often useful in describing what it is you're trying to figure. I can't quite get it from your description. |
|
Apr 22 |
answered | How can I check if a multipolygon can be represented as a simple polygon? |
|
Apr 17 |
answered | Problem loading PostGIS (Postgres) View layer in QGIS |
|
Apr 17 |
comment |
PostGIS Better ST_Intersects Query The ST_Intersects() function includes an && test within it, so there's no reason this multi-step approach should be any faster then a straight tests against ST_Intersects() to start with. |
|
Apr 17 |
comment |
PostGIS: Convert meters to arbitrary spatial reference units? If you use ST_DWithin(geom::geography, point, distance) you'll get an index-accelerated distance test in native geographic coordinates, no projections required, performance guaranteed. |
|
Apr 16 |
answered | Aggregate points with same values to polygons |
|
Apr 16 |
comment |
PostGIS: Convert meters to arbitrary spatial reference units? This is bad on many levels: you can perform an exact distance test in meters in geography, so you don't need the buffer step; the buffer in geography actually flips everything back to an automatically chosen geometry SRID, so it's not doing what you think; buffering is really expensive and distance tests are not, so it's a poor performer. Just take the geometry into geography and perform the distance test there. |
|
Apr 15 |
comment |
From a trajectory of GPS points to a multiline segment This seems reasonable. The best approach I think depends to some extent on the shape of your data. You'll have some jitter around the "true path" that a smoothing will take out. You might also have some outliers, which you would rather ignore than add to the average path. These would require some other sort of smarts to handle. |
|
Apr 4 |
comment |
Unable to Import Data Confirm that you actually have PostGIS installed in your target database. Run "Select postgis_full_version()" |
