[postgis-devel] Distance Merge

Paul Ramsey pramsey at cleverelephant.ca
Fri Nov 20 16:32:02 PST 2009


On Fri, Nov 20, 2009 at 1:51 PM, Nicklas Avén
<nicklas.aven at jordogskog.no> wrote:
> what is not fixed is handling the empty geometries.

Detect with lwgeom_is_empty()

> I would like some suggestion or advice.
> I have looked a little at the old code. It seems to return 0 at once there
> is one empty geometry in a collection. Is that right behavior? or is it the
> parser that defines this anyway?

The right behavior is defined here:

http://trac.osgeo.org/postgis/wiki/DevWikiEmptyGeometry

I am going to update that page a bit to reflect your question on
collections -- if any part of the collection is non-empty, the
distance is defined against that part. If it is all empty, the
distance is NULL.

P.

>
> otherwise I think we can put it in trunk. If any bugs show I think they will
> be quite easy to find.
> If not Regina has seen any unstabilities?
>
> Thanks
> Nicklas
>
> 2009-11-20 Paul Ramsey wrote:
>
> Nicklas, do you feel like your distance work is ready to merge?
>>
>>P
>>_______________________________________________
>>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