[postgis-devel] collect()
strk at refractions.net
strk at refractions.net
Tue Sep 28 02:35:48 PDT 2004
Another issue tight to flattening.
Flattening might require a 'depth' argument
a geometry of this type:
COLLECTION -+-- COLLECTION --+-- MULTIPOINT
| |
+-- MULTIPOINT +-- POINT
-might become:
MULTIPOINT
-might become:
COLLECTION -+-- MULTIPOINT
|
+-- MULTIPOINT
-might become:
COLLECTION -+-- MULTIPOINT
-might become:
COLLECTION -+-- POINT
|
+-- POINT
|
...
The 'flattening' issue seems harder to manage then initially looked.
--strk;
On Mon, Sep 27, 2004 at 06:52:38PM +0200, strk at refractions.net wrote:
> On Mon, Sep 27, 2004 at 09:25:35AM -0700, Chris Hodgson wrote:
> > By flatten I suppose you mean to remove any nested collections and put
> > them all in one big collection? Yes. We didn't have support for nested
> > collections when "collect()" was written (that was the first thing I
> > ever wrote for postgis!).
> >
> > I agree, collect shouldn't flatten, but a separate function that does
> > flatten would be a good idea.
>
> Good.
> And bed (the LWGEOM_EXPLODED structure needs a refactoring :)
> --strk;
>
> >
> > Chris
> >
> > strk at refractions.net wrote:
> >
> > >Current (OLD) collect() function flatten geometries.
> > >Should NEW collect() also do this or instead have a
> > >flatten(the_geom) taking care of this ?
> > >(I opt for the second)
> > >--strk;
> > >_______________________________________________
> > >postgis-devel mailing list
> > >postgis-devel at postgis.refractions.net
> > >http://postgis.refractions.net/mailman/listinfo/postgis-devel
> > >
> > >
> >
> > _______________________________________________
> > postgis-devel mailing list
> > postgis-devel at postgis.refractions.net
> > http://postgis.refractions.net/mailman/listinfo/postgis-devel
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-devel
More information about the postgis-devel
mailing list