<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7653.38">
<TITLE>RE: [postgis-devel] Testing ST_LineMerge issue</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>I haven't tried on 1.3.5 or 1.4, but on 1.3.3 it does.<BR>
<BR>
SELECT ST_GeomFromText(ST_AsText(ST_MakeLine(ST_Point(1,1), ST_Point(1,1))))<BR>
<BR>
So I guess at least we are consistent.<BR>
<BR>
-----Original Message-----<BR>
From: postgis-devel-bounces@postgis.refractions.net on behalf of Paul Ramsey<BR>
Sent: Wed 12/17/2008 1:06 PM<BR>
To: PostGIS Development Discussion<BR>
Subject: Re: [postgis-devel] Testing ST_LineMerge issue<BR>
<BR>
Our parser doesn't let that be created (does it?) so why should a<BR>
constructor? I think as long as our policy is consistent, we're doing<BR>
OK.<BR>
<BR>
P.<BR>
<BR>
On Wed, Dec 17, 2008 at 7:33 AM, Obe, Regina <robe.dnd@cityofboston.gov> wrote:<BR>
> I was thinking about this failed test more and even though I had<BR>
> dismissed it as something only a Monkey would do that is not urgent.<BR>
><BR>
> It has occurred to me that I may run into this issue with Monkey users<BR>
> and I may have already that may be a culprit in my geoserver random<BR>
> disconnects.<BR>
><BR>
> At least one of the projects I'm working on I have run into users<BR>
> creating invalid geometries. Since they put in a lot of effort making<BR>
> these monsters, we decided to just check on some schedule to make sure<BR>
> the new geometries being created are valid.<BR>
><BR>
> The monster I am talking about is this innocent one that I took out of<BR>
> the torture script because well you can't torture a dead server.<BR>
><BR>
> In its simplest form it looks like this.<BR>
><BR>
> SELECT ST_LineMerge(ST_MakeLine(ST_Point(1,1), ST_Point(1,1)));<BR>
><BR>
><BR>
> Now there are 2 issues here.<BR>
><BR>
> 1) GEOS ST_LineMerge is obviously not smart enough to realize that<BR>
> linemerging something like that is silly.<BR>
><BR>
> 2) ST_MakeLine lets you get away with creating this monstrosity. Which<BR>
> hmm I suppose there are reasons why someone may want to, but perhaps we<BR>
> shouldn't go there.<BR>
><BR>
><BR>
><BR>
><BR>
> -----------------------------------------<BR>
> The substance of this message, including any attachments, may be<BR>
> confidential, legally privileged and/or exempt from disclosure<BR>
> pursuant to Massachusetts law. It is intended<BR>
> solely for the addressee. If you received this in error, please<BR>
> contact the sender and delete the material from any computer.<BR>
> _______________________________________________<BR>
> postgis-devel mailing list<BR>
> postgis-devel@postgis.refractions.net<BR>
> <A HREF="http://postgis.refractions.net/mailman/listinfo/postgis-devel">http://postgis.refractions.net/mailman/listinfo/postgis-devel</A><BR>
><BR>
_______________________________________________<BR>
postgis-devel mailing list<BR>
postgis-devel@postgis.refractions.net<BR>
<A HREF="http://postgis.refractions.net/mailman/listinfo/postgis-devel">http://postgis.refractions.net/mailman/listinfo/postgis-devel</A><BR>
<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>