James-
another optionis to use rasdaman [1] which runs on top of PostgreSQL. It is
genuinely multi-dimensional, so it can handle image timeseries as one compact
object and access/process it efficiently. Addtionally, you can tune storage
layout for time series access patterns. We have just
Hi All,
Is there a simpler test I can do? I am quite sure that I am probably not
using the right
function in my SQL, or not doing the intersection test correctly. Is there
any simpler
way to test this 3D intersection? Am waiting on the postgis gurus to come
along and
give me some ideas, coz I am
Hi,
Just to add more information, in case someone has time later on to check it
out.
I tried intersecting just ONE triangle with the faces in my vfaces table,
and what I
get back from the st_intersection is the triangle back itself repeated 4
times! I don't
get it. Is there a way to get around
Hi,
st_intersection is only suitable for 2D operations. Third dimension is not
taken into account.
Nicolas
On 30 October 2012 09:44, Ed Linde edoli...@gmail.com wrote:
Hi All,
Is there a simpler test I can do? I am quite sure that I am probably not
using the right
function in my SQL, or
Ah drat! Ok then I have to basically do edge intersection tests by myself.
Ah well. bad news! :(
On Tue, Oct 30, 2012 at 10:44 AM, Nicolas Ribot nicolas.ri...@gmail.comwrote:
Hi,
st_intersection is only suitable for 2D operations. Third dimension is not
taken into account.
Nicolas
On 30
Ok, for a polygon, is there a good postgis function that can return the
edges to me in the
right sequence? Or at least the points that constitute the polygon in the
right order, so I can
generate the edges in a script?
Thanks,
Ed
On Tue, Oct 30, 2012 at 10:46 AM, Ed Linde edoli...@gmail.com
st_dumpRings will return the rings (closed linestrings) composing the
polygon (exterior first, then interiors)
and st_dumpPoints will return all the points forming the rings, in the
right order.
Nicolas
On 30 October 2012 10:56, Ed Linde edoli...@gmail.com wrote:
Ok, for a polygon, is there a
Ok thanks!
On Tue, Oct 30, 2012 at 11:04 AM, Nicolas Ribot nicolas.ri...@gmail.comwrote:
st_dumpRings will return the rings (closed linestrings) composing the
polygon (exterior first, then interiors)
and st_dumpPoints will return all the points forming the rings, in the
right order.
Hi Nicolas,
Not quite sure what to make of the output from ST_DumpPoints, how do I
transform it to just raw x,y,z coordinates?
select st_astext(geomtext) from small_tris where id=0;
st_astext
---
POLYGON Z ((10 10 805,20
Maybe ST_X, ST_Y and ST_Z ?
Hugues.
De : postgis-users-boun...@postgis.refractions.net
[mailto:postgis-users-boun...@postgis.refractions.net] De la part de Ed Linde
Envoyé : mardi 30 octobre 2012 11:14
À : PostGIS Users Discussion
Objet : Re: [postgis-users]
Got it working
SELECT gen_id,
ST_X((dp).geom),
ST_Y((dp).geom),
ST_Z((dp).geom)
FROM (
SELECT gen_id, ST_dumpPoints(geomtext) as dp
from vfaces
) As foo;
On Tue, Oct 30, 2012 at 11:19 AM, Francois Hugues hugues.franc...@irstea.fr
wrote:
**
Maybe ST_X,
Date: Fri, 26 Oct 2012 12:10:59 -0400
From: lee.hachadooria...@gmail.com
To: postgis-users@postgis.refractions.net
Subject: Re: [postgis-users] Pg_wrapper error
On Fri, Oct 26, 2012 at 11:27 AM, José Pedro Santos
zpsant...@hotmail.com wrote:
I have the executables. When I try that
Thank you very much for the prompt response. Do you have at least a rough
estimate for when the next patch release is going to be?
Radu Ilie
-Original Message-
From: postgis-users-boun...@postgis.refractions.net
[mailto:postgis-users-boun...@postgis.refractions.net] On Behalf Of Paul
Hello,
I am still trying to figure out query layers and ArcGIS, I am getting an error
when I try to open up a table: Error reading OID from Table OID Column
has null value. I noticed that when the table opens (blank) that there is an
additional column called ESRI_OID. How can I add
Thanks for the version info. I'll have to poke around.
Nope. No other limitations to out-db.
-bborie
On Mon, Oct 29, 2012 at 5:25 PM, James Hiebert hieb...@uvic.ca wrote:
= select version(), postgis_full_version(), postgis_raster_lib_version();
PostgreSQL 9.1.5 on x86_64-pc-linux-gnu,
Fixed the ST_Intersects not permitting out-db bands in r10590 for 2.0.2.
On Tue, Oct 30, 2012 at 7:33 AM, Bborie Park bkp...@ucdavis.edu wrote:
Thanks for the version info. I'll have to poke around.
Nope. No other limitations to out-db.
-bborie
On Mon, Oct 29, 2012 at 5:25 PM, James
No, we don't have a calendrical release schedule, but the backlog of
fixes complete for 1.5.6 is actually a pretty impressive nest of
crashers and improvements, so I'm sure we could be poked into it...
- Bug Fixes
- #547, ST_Contains memory problems, the remake
- #1957, ST_Distance to a
On Tue, Oct 30, 2012 at 09:45:24AM -0700, Paul Ramsey wrote:
No, we don't have a calendrical release schedule, but the backlog of
fixes complete for 1.5.6 is actually a pretty impressive nest of
crashers and improvements, so I'm sure we could be poked into it...
- Bug Fixes
- #547,
Happy Halowe'en, it's online.
http://postgis.org/download
P.
On Tue, Oct 30, 2012 at 9:47 AM, Sandro Santilli s...@keybit.net wrote:
On Tue, Oct 30, 2012 at 09:45:24AM -0700, Paul Ramsey wrote:
No, we don't have a calendrical release schedule, but the backlog of
fixes complete for 1.5.6 is
Friends,
geocode_intersection returns nothing. I'm a newbie!...So, I'd like some ideas.
First, the postgis (2.0.1) and PostgreSQL 9.1.6 versions:
POSTGIS=2.0.1 r9979 GEOS=3.3.3-CAPI-1.7.4 PROJ=Rel. 4.7.1, 23
September 2009 GDAL=GDAL 1.9.1, released 2012/05/15 LIBXML=2.7.8
LIBJSON=UNKNOWN
20 matches
Mail list logo
