I think you don't have enough memory. Atleast thats my first assumption :)
What kind of computer system is this running on? What are the hardware
specs? Do you have oodles of swap/paging memory available? Do you
have enough disk space for Postgresql to create its own temporary
files?
Shane
On
Check out the mailing list archives, there has been a lot of talk
about raster storage in PostGIS tables including links to programming
that may be able to help. This is a huge topic of interest however
the only questions that ever hit the list seem to be "How do I" vs
"Here is my success at doing
e'd expect to see.
>
> ST_Collect() is an in-memory function, so you can't expect to throw
> large numbers of geometries at it and have it be performant.
>
> The moral of the story: always look for ways to take advantage of
> spatial indexing!
>
>
> Shane Spen
strike that.. 1.5ms not 15ms..
I hope this is in line with the original problem.. Scott?
On 10/4/07, Shane Spencer <[EMAIL PROTECTED]> wrote:
> Funny, I actually just used Collect() for my first time today, it had
> a really hard time collecting more than 1 of my polygons. I
>
Funny, I actually just used Collect() for my first time today, it had
a really hard time collecting more than 1 of my polygons. I
noticed every time I added 1000 polygons to the selection limit while
testing Collect() it doubled in time needed. 6000 polygons required a
ton of memory. I event
60,000 polygon objects will be harder to fit into memory than a single
polygon from that set would. I would think doing a query on each
individual polygon would be faster than doing it on one large
multipolygon for the following reason.
Bounding boxes are typically used to see if a point even exi
sounds like you will have a lot of duplicate points. I recommend you
only insert distinct points into a table, then make a reference table with
smaller data types and a primary key referencing the point table. Python
could handle that kind of insert situation pretty easily.
On 9/25/07, Shane Spencer
you would be better off pre-transforming them with ogr2ogr.. dump them to a
shapefile, write a q
On 9/25/07, Stephen Crawford <[EMAIL PROTECTED]> wrote:
>
> All,
>
> I have a table of about 30 million point observations. The geometries are
> stored in lon/lat., with a gist index on the column. F
I figured it out a bit ago.. finally.. because I'm a dweeb..
I assumed buffer was a memory function :) It greatly confused me. I just
started up with PostGIS a few weeks ago and am just now seeing the term
buffer in all the programs I've been using for GIS visualization.
Thanks for the descript
Just dinking around.
select distance(
startpoint(GeomFromText('LINESTRING( 0 0, 1 1 )')),
endpoint(GeomFromText('LINESTRING( 0 0, 1 1 )'))
);
distance
-
1.4142135623731
confirmed via python CLI
>>> math.sqrt(1 + 1)
1.4142135623730951
make
Thats so cool it hurts.. I love offloading processing to the big bad server
while the little wimpy sql clients request the data. Good find!
On 9/14/07, Kevin Neufeld <[EMAIL PROTECTED]> wrote:
>
> Absolutely.
>
> See attached, a simple plpgsql function that adds header info around the
> current a
http://www.bostongis.com/PrinterFriendly.aspx?content_name=ogr_cheatsheet
I use ogr2ogr for doing that.. however sometimes its best to write the KML
using your own structure, descriptions, and element names.
http://www.gdal.org/ogr/drv_kml.html will describe the options that let you
name the KML
you could create a new entry, new srid, then update the geometry columns
table. I'm unsure on if you have to translate your data table to another
data table to update the srid per row/field.
I personally wouldn't modify any row of the spatial_ref_sys for
compatibility reasons.
Can you translate t
Could you reply with a URL to what buffers are and how they would be used in
this context? I'm totally unfamiliar.
On 9/9/07, Nico Mandery <[EMAIL PROTECTED]> wrote:
>
> Hi Rainer,
>
> You could could use a buffer instead of bounding boxes.
> Just an idea
>
> Nico
>
> Am Sonntag 09 September 2007
ST_DWithin(mytable.the_geom, ST_SetSRID(MakePoint($x, $y), $srid),
> $distance);
>
> P.
>
> On 9-Sep-07, at 11:25 AM, Shane Spencer wrote:
>
> > I don't understand how the Distance() and Intersects() and Contains
> > () function wouldn't work for this?
>
I don't understand how the Distance() and Intersects() and Contains()
function wouldn't work for this?
Are X and Y radius the same?
On 9/9/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> what I want to do is finding certain features in some distance around a
> certain point. Those fe
16 matches
Mail list logo
