> Sorry, I didn't mean to confuse. I'm not familiar with your tables, I
> had no idea how to join the tables, it was example of derived tables,
> not example of what fields to join.
>
> What I mean is, start in the middle and keep wrapping things around it.
> Each derived table is like a temp table
Date: Thu, 11 Jun 2015 16:53:46 -0500
From: a...@squeakycode.net
To: postgis-users@lists.osgeo.org
Subject: Re: [postgis-users] Find unique date and code values before applying
st_intersects
On 6/11/2015 3:36 PM, Gery . wrote:
Hello,
I have two tables, one containing polygons and one with
rder by
cuadro_produce_region.gid,cuadro_produce_region.cod;
> Date: Thu, 11 Jun 2015 16:53:46 -0500
> From: a...@squeakycode.net
> To: postgis-users@lists.osgeo.org
> Subject: Re: [postgis-users] Find unique date and code values before applying
> st_intersect
On 6/11/2015 3:36 PM, Gery . wrote:
Hello,
I have two tables, one containing polygons and one with points:
# polygons
gid | integer | not null default
nextval('cuadro_produce_region_gid_seq'::regclass)
id | character varying(10)|
zona| character varying(10
Sorry, my last email had the hotmail format, hope this one would have a much
better format.
--
Hello,
I have two tables, one containing polygons and one with points:
& polygons
gid | integer | not null default
nextval('cuadro_produce_region_gid_seq'::regclass)
id
Hello,
I have two tables, one containing polygons and one with points:
# polygonsgid | integer | not null default
nextval('cuadro_produce_region_gid_seq'::regclass)id | character
varying(10)| zona| character varying(10)| area | character
varying(10)
