On Jul 3, 2012, at 2:07 AM, Duarte Carreira (gmail) wrote:
Duarte,
> [...] So there you go. Just my 2 cents... all that being said, I enjoy working
> with arcmap+postgis. [...]
Thanks a lot for you very detailled feedback,
really appreciated !
--
Olivier
___
On 03/07/12 07:14, James Sewell wrote:
Hello,
When I run pgsql2shp like so:
pgsql2shp -u plm25 -g the_geom database table
I get the following output:
Xcolumn number -1 is out of range 0..1
column number -1 is out of range 0..1
column number -1 is out of range 0..1
column number -1 is out
Well, I did some more testing, and found out that the failed query and
subsequent crash of the postgresql client isn't caused by the lat/lng
coordinates... It happens consistently after a certain number of rows (and/or
amount of data) is inserted into the table. Usually close to 300 rows (or 96K
hi,
I have a problem with an intersection with 2 lines that don't return
what I expect:
sample intersection between a line and a substring of the same line:
first line: LINESTRING(675315.7 158956.9,675280 158912.9)
second: st_makeline(geomfromtext('POINT(675315.7 158956.9)'),
ST_Line_Interpolat
Hi all,
We have a layer that contains polygons and another that contains lines
that lie on them. Parts of the lines are laying "inside" the polygons
and I would like to get a sum of all the lengths of lines that lie on
the polygons. What is the easiest way to achieve this?
TIA,
Matej
Hi,
You can use something like
SELECT areas.id, SUM( ST_Length( lines.geometry) ) FROM lines,areas
WHERE ST_Intersects(lines.geometry,areas.geometry) GROUP BY areas.id ;
Greetings,
Denis
On 07/03/2012 01:36 PM, Matej Mailing wrote:
Hi all,
We have a layer that contains polygons and anothe
On 03/07/12 12:34, René Fournier wrote:
Well, I did some more testing, and found out that the failed query and
subsequent crash of the postgresql client isn't caused by the lat/lng
coordinates... It happens consistently after a certain number of rows
(and/or amount of data) is inserted into the
On 2012-07-03, at 1:43 PM, Mark Cave-Ayland wrote:
> On 03/07/12 12:34, René Fournier wrote:
>
>>
>> If I quit and restart psql, same error occurs. Only if I drop the table
>> can I insert more rows — but again, only up to around 300 rows or 100 kb
>> (not sure where the limit is)... So, it's no
So, it seems that the table gets full and corrupted to some extent. After my
import script inserts ~290 rows, and then postgres crashes...
mydb=# select count(*) from addresses;INSERT INTO addresses ( account_id,
territory_id, location ) VALUES ( 1, 75, ST_GeomFromText('POINT(-114.267388
51.089
Hi William,
Thank you for response. It is great that you showed interest in helping me on
this. After playing with the query tool, it was very evident that I need to
pick one single unique identifier field. The problem I am facing happens
despite the fact that I selected one single field as uniq
I haven't seen this behaviour -- being able to see the attributes with
identify but not being able to use the attribute table properly.
Are you 100% certain the unique identifier column you have chosen is unique,
i.e. is it a primary key, or does it have a unique constraint on it?
Duplicate key
On 03/07/12 13:20, René Fournier wrote:
So, it seems that the table gets full and corrupted to some extent.
After my import script inserts ~290 rows, and then postgres crashes...
mydb=# select count(*) from addresses;INSERT INTO addresses (
account_id, territory_id, location ) VALUES (
> I need to do an ordered weighted averaging with the input rasters: assuming
> they all have the same extension and characteristics (like pixel size), for
> position (1,1) I take the value of every raster, the I sort those values to
> assign the weights and finally I compute the average to store i
Yes, it's very important to know your version/platform.
Also, does this point crash the back-end when inserted into an empty
table, or only when inserted after the initial series of points. If
the latter, then the problem isn't the particular point, but how the
index is dealing with your particular
The selected unique identifier column is GID (created by postgis). So, it has
to be unique identifier.
Based on the fact that I could see selected feature attributes or I could see
attributes using identifier tool,
I have to assume that query tool retrieves this information upon user action
(i
Hello,
Ive some problems to make Postgis-1.5.4 compilation On Debian Squeeze.
After the ./configure , make command end like that:
gcc -g -O2 -g -Wall -O2 -fPIC -Wall -Wmissing-prototypes -Wpointer-arith
-Wdeclaration-after-statement -Wendif-labels -fno-strict-aliasing -fwrapv -g
-fpic -I
Can you interact with the postgresql/Postgis data natively (ie via pgAminIII) without error? Can't think of any case where this might not be the case. This smells very much like an ArcGIS/ArcSDE configuration problem. In the old days, when one used the ArcSDE administration command line tools, one
Hi,
Thank you for the answer. However, I don't get the right result. For
example, when there is a line that is long 500 meters and it crosses 5
polygons (on each of them maybe just a meter or few meters, except one
where lies a majority of the line), I get the full length of the lines
for correspo
I think I have just found it out. I just add ST_Intersection to have a
query like:
SELECT areas.id, SUM( ST_Length( ST_Intersection(lines.geometry,
areas.geometry) ) ) FROM lines,areas WHERE
ST_Intersects(lines.geometry,areas.geometry) GROUP BY areas.id ;
Now the numbers seem to be correct :-) Hop
Yes, you're right.
This should solve this problem:
SELECT areas.id, SUM( ST_Length( ST_Intersection( lines.geometry ,
areas.geometry ) ) )
FROM lines,areas
GROUP BY areas.id ;
ST_intersects returns true if there is an intersection and
ST_Intersection returns the share geometry.
Greetings,
Messages crossed, but seems we agree ;)
On 07/04/2012 08:51 AM, Matej Mailing wrote:
I think I have just found it out. I just add ST_Intersection to have a
query like:
SELECT areas.id, SUM( ST_Length( ST_Intersection(lines.geometry,
areas.geometry) ) ) FROM lines,areas WHERE
ST_Intersects(line
21 matches
Mail list logo
