On Oct 17, 2011, at 9:22 PM, William Kyngesburye wrote:
> Try looking in config.log for a more detailed explanation why it couldn't
> find GDAL python.
I see stuff like this...
configure:19000: result: TOPOLOGY: Topology support requested
configure:19023: result: RASTER: Raster support reques
-- Forwarded message --
From: vy nguyen
Date: Mon, Oct 17, 2011 at 3:08 PM
Subject: cannot show circle in map use st_buffer
To: postgis-users-requ...@postgis.refractions.net
Hi,
I used ST_BUFFER(geometry, radius) to get a polygon.
I viewed the polygon on Geo server, it is a circl
Try looking in config.log for a more detailed explanation why it couldn't find
GDAL python.
On Oct 17, 2011, at 8:48 PM, Puneet Kishor wrote:
> Any suggestions, anyone? As shown below, I believe I have the Python bindings
> for GDAL installed, yet, I get the following error
>
> RASTER: Raster
Any suggestions, anyone? As shown below, I believe I have the Python bindings
for GDAL installed, yet, I get the following error
RASTER: Raster support requested
checking for GDAL >= 1.6.0... found
checking for GDALFPolygonize in -lgdal... no
checking for GDAL Python bindings... not found
configu
Stephen,
It takes a brave man to admit he is using antiquated technology. I applaud
you :).
I see one major issue here. You are doing a cartesian product before
unioning / collecting.
That means for every new.the_geom you have you are creating n copies of it
where n is the number of boundar
Matthias,
This is a different approach but it might be useful. This is untested,
but hopefully it will give you the idea:
select
floor((st_x(a.the_geom)-b.minx)/1000)::integer as col,
floor((st_y(a.the_geom)-b.miny)/1000)::integer as row,
count(*) as cnt
from
(
select
Hello,
for a statistical analysis I need to create a polygon grid to count the points
inside. The analysis area measures about 15x15km. At the moment I use the code
below. It's functioning but is slow for high point counts(>5000-10 points)
and small polygon sizes (5-20m). Because the points
Hi All,
True confession, I'm running PostGIS 1.3.5, so throw the
tomatoes gently if A) I'm doing a bad query, or B) I'm dredging up old news
on (in)efficiency, and I really should upgrade to 1.5.x, thank you very
much. . Admittedly, it is time for that, but hopefully that's a sepa
> Thanks for the response. A follow up question: what if the yourLongitude,
> yourLatitude values provided in the query are not grid points in that they
> fall
> within a bounding pixel grid. Only values for the intersection points are
> known
> so how does a non-intersecting point get assigne
Thanks for the response. A follow up question: what if the
yourLongitude, yourLatitude values provided in the query are not grid
points in that they fall within a bounding pixel grid. Only values for
the intersection points are known so how does a non-intersecting point
get assigned a value
On Mon, Oct 17, 2011 at 4:08 PM, Pierre Racine
wrote:
>> What i get in my database is a new table with the name of my image with no
>> data inside (only "1" in rid serial) and a row at the raster_columns with
>> all data
>> of the uploaded image except the nodata_values.
>
> You should have one "
> What i get in my database is a new table with the name of my image with no
> data inside (only "1" in rid serial) and a row at the raster_columns with all
> data
> of the uploaded image except the nodata_values.
You should have one "rid" column and one "rast" column. And since you loaded
usin
On Mon, Oct 17, 2011 at 01:11:14PM +0200, José Carlos Martínez Llario wrote:
> I think many people were waiting for a persistent topology model.
Luckly someone also made something about it ! :)
> There is already some performance bechmark comparing the simple
> feature model with the persistent
Il 17/10/2011 13:11, José Carlos Martínez Llario ha scritto:
Congratulations to the PostGIS team.
and to the sponsor of this work: Tuscany Regional Administration.
--
Paolo Cavallini
See: http://www.faunalia.it/pc
___
postgis-users mailing list
pos
Hi Sandro,
This is great news!!
I think many people were waiting for a persistent topology model.
There is already some performance bechmark comparing the simple
feature model with the persistent topology model about quering,
writing topo geometries, etc. specially talking about face primitive
I have set PostGIS 2.0 with Raster (in Windows 7) and tried to upload a .tiff
image, by following the instructions in 3.1 from here:
http://trac.osgeo.org/gdal/wiki/frmts_wtkraster.html (python raster2pgsql.py -r
/path/to/katrina.tif -t katrina -l 1 -k 64x64 -o katrina.sql -s 4326 -I -M and
aft
[http://strk.keybit.net/blog/2011/10/14/postgis-topology-iso-sqlmm-complete/]
PostGIS implementation of the ISO SQL/MM Topology-Geometry model
is finally complete [1].
The SQL/MM model [2] is just a portion of the whole topology support [3],
but an important one, including schema definition and f
On Mon, Oct 17, 2011 at 01:24:43AM -0200, Carlos Andrade wrote:
> I came across this presentation while searching for it:
> http://oslandia.org/postgis_paris_juin_2011/postgis_paris_topology_santilli.pdf
>
> Is anyone aware where can I find the tool used for this presentation or even
> more infor
18 matches
Mail list logo
