<!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] Re: [postgis-users] Changed bahaviourof PostGISconfuses MapServer</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>I like the idea of listing why, but slight correction. Its not so much common to Mapserver users as common to anyone<BR>
who uses MULTILINESTRINGS. I think it only affects mapserver if you display multilinestrings, but there are tons of other things people do like st_dump of multiline and so forth that would break.<BR>
<BR>
How about we change to Found to contain bug affecting MULTILINESTRINGS.<BR>
<BR>
<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: postgis-devel-bounces@postgis.refractions.net on behalf of Kevin Neufeld<BR>
Sent: Sun 12/14/2008 12:59 AM<BR>
To: PostGIS Development Discussion<BR>
Subject: Re: [postgis-devel] Re: [postgis-users] Changed bahaviourof PostGISconfuses MapServer<BR>
<BR>
Sounds ok to me. BTW, I added a brief note to the downloads page<BR>
indicating why 1.3.4 is no longer listed ... just so people don't get<BR>
confused and wonder what happened.<BR>
-- Kevin<BR>
<BR>
Paul Ramsey wrote:<BR>
> Fair enough. Then I would like to change the PostGIS downloads page to<BR>
> reference 1.3.3 in the interim... P.<BR>
><BR>
> On Sat, Dec 13, 2008 at 11:46 AM, Obe, Regina <robe.dnd@cityofboston.gov> wrote:<BR>
> <BR>
>> -1<BR>
>><BR>
>> Well I mean not ASAP. Lets wait till at least Tuesday. I agree it is a<BR>
>> far reaching bug that I suspect affects many functions. Anything that needs<BR>
>> to extract a multi into individual linestrings will be affected.<BR>
>><BR>
>> Then again I'm not convinced that many people have deployed into production<BR>
>> and this to me would affect people who are unable to compile for themselves<BR>
>> more than anyone else (e.g lots of windows users who have deployed) so we<BR>
>> have to wait for Mark's +1 anyway.<BR>
>><BR>
>> Besides I want to get the torture script further along to brute force test<BR>
>> to make sure no other surprises. So far the torture script<BR>
>> tests all the functions that deal with one geometry, or 2 geometry or no<BR>
>> args, but have yet to test for things that take other arguments (like all<BR>
>> the Affine and so forth).<BR>
>><BR>
>><BR>
>><BR>
>><BR>
>><BR>
>><BR>
>> -----Original Message-----<BR>
>> From: postgis-devel-bounces@postgis.refractions.net on behalf of Paul Ramsey<BR>
>> Sent: Sat 12/13/2008 12:13 PM<BR>
>> To: PostGIS Users Discussion; PostGIS Development Discussion<BR>
>> Subject: [postgis-devel] Re: [postgis-users] Changed bahaviour of<BR>
>> PostGISconfuses MapServer<BR>
>><BR>
>> Yes, Peter, I think it should call for a quick 1.3.5. Mapserver users<BR>
>> are a huge contingent of PostGIS users, and anyone with a LINE layer<BR>
>> now has a crasher. 1.3.5 should come off the line ASAP. There's always<BR>
>> more version numbers, IMO.<BR>
>><BR>
>> Can we have a quick vote on 1.3.5 release-from-branch, no-waities?<BR>
>><BR>
>> +1<BR>
>><BR>
>> P.<BR>
>><BR>
>> On Sat, Dec 13, 2008 at 1:25 AM, Peter Hopfgartner<BR>
>> <peter.hopfgartner@r3-gis.com> wrote:<BR>
>> <BR>
>>> Mark Cave-Ayland wrote:<BR>
>>> <BR>
>>>> Peter Hopfgartner wrote:<BR>
>>>><BR>
>>>> <BR>
>>>>> Dear MLs,<BR>
>>>>><BR>
>>>>> sorry for cross-posting to both, PostGIS and MS, but seems to rtouch<BR>
>>>>> both.<BR>
>>>>><BR>
>>>>> I've tried to install PostGIS 1.3.4 on a CentOS 5 server with MapServer<BR>
>>>>> 5.2.1 and PostgreSQL 8.2.11.<BR>
>>>>><BR>
>>>>> the command:<BR>
>>>>><BR>
>>>>> shp2img -l prova -e 1587541 5116731 1591730 5120008 -m prova.map ><BR>
>>>>> ../../public/technet/test-<pgis-version>.png<BR>
>>>>><BR>
>>>>> with 1.3.3 gave the result shown in figure test-postgis-1.3.3-4.png (a<BR>
>>>>> simple line layer)<BR>
>>>>><BR>
>>>>> Upgrading to 1.3.4 the picture became as in test-postgis-1.3.4-1.png, an<BR>
>>>>> empty picture.<BR>
>>>>><BR>
>>>>> The relevant mapfile fragment is Mapfile.frag.txt, the SQL table<BR>
>>>>> definition is e405.sql, all objects are MULTILINESTRINGs [SELECT<BR>
>>>>> DISTINCT<BR>
>>>>> geometrytype(the_geom) FROM public.e405 results in MULTILINESTRING], the<BR>
>>>>> geometry column is registered as MULTILINESTRING in geometry_columns.<BR>
>>>>><BR>
>>>>> Running the MapServer query:<BR>
>>>>><BR>
>>>>> SELECT<BR>
>>>>> asbinary(force_collection(force_2d(the_geom)),'NDR'),common_uid::text<BR>
>>>>> from<BR>
>>>>> public.e405 WHERE (tiplinapp is not null) and (the_geom && setSRID(<BR>
>>>>> 'BOX3D(1587541 5116702.44897959,1591730<BR>
>>>>> 5120036.55102041)'::BOX3D,find_srid('','public.e405','the_geom') ))<BR>
>>>>><BR>
>>>>> changed for better result readability into:<BR>
>>>>><BR>
>>>>> SELECT AsEWKT(force_collection(force_2d(the_geom))),common_uid::text<BR>
>>>>> from<BR>
>>>>> public.e405 WHERE (tiplinapp is not null) and (the_geom && setSRID(<BR>
>>>>> 'BOX3D(1587541 5116702.44897959,1591730<BR>
>>>>> 5120036.55102041)'::BOX3D,find_srid('','public.e405','the_geom') ))<BR>
>>>>><BR>
>>>>> by hand gives slightly different results, as shown in the attached<BR>
>>>>> files.<BR>
>>>>><BR>
>>>>> To make a long story short, 1.3.4 seems to better preserve the<BR>
>>>>> MULTILINESTRING, but this seems to confuse MapServer.<BR>
>>>>><BR>
>>>>> Regards,<BR>
>>>>><BR>
>>>>> Peter<BR>
>>>>> <BR>
>>>> Hi Peter,<BR>
>>>><BR>
>>>> This is likely the known issue with MULTILINESTRINGs in 1.3.4 causing<BR>
>>>> segfaults :( The patch you need is very simple and can be found here:<BR>
>>>><BR>
>>>> <A HREF="http://postgis.refractions.net/pipermail/postgis-commits/2008-December/000866.html">http://postgis.refractions.net/pipermail/postgis-commits/2008-December/000866.html</A><BR>
>>>> if you can't wait for a 1.3.5 release. Please let us know whether this<BR>
>>>> resolves the problem for you.<BR>
>>>><BR>
>>>><BR>
>>>> HTH,<BR>
>>>><BR>
>>>> Mark.<BR>
>>>><BR>
>>>> <BR>
>>> Should this issue call for a quick 1.3.5 release? If I understood this<BR>
>>> issue<BR>
>>> well, everybody rendering PostGIS data stored as a MULTILINE geometry will<BR>
>>> have this very same problem, at least with MapServer. I would guess that<BR>
>>> this is quite a big share of PostGIS users that will be hit by this issue.<BR>
>>><BR>
>>> Regards,<BR>
>>><BR>
>>> Peter<BR>
>>><BR>
>>><BR>
>>><BR>
>>><BR>
>>> --<BR>
>>><BR>
>>> Dott. Peter Hopfgartner<BR>
>>><BR>
>>> R3 GIS Srl - GmbH<BR>
>>> Via Johann Kravogl-Str. 2<BR>
>>> I-39012 Meran/Merano (BZ)<BR>
>>> Email: peter.hopfgartner@r3-gis.com<BR>
>>> Tel. : +39 0473 494949<BR>
>>> Fax : +39 0473 069902<BR>
>>> www : <A HREF="http://www.r3-gis.com">http://www.r3-gis.com</A><BR>
>>><BR>
>>> _______________________________________________<BR>
>>> postgis-users mailing list<BR>
>>> postgis-users@postgis.refractions.net<BR>
>>> <A HREF="http://postgis.refractions.net/mailman/listinfo/postgis-users">http://postgis.refractions.net/mailman/listinfo/postgis-users</A><BR>
>>><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>
>> ________________________________<BR>
>><BR>
>> The substance of this message, including any attachments, may be<BR>
>> confidential, legally privileged and/or exempt from disclosure pursuant to<BR>
>> Massachusetts law. It is intended solely for the addressee. If you received<BR>
>> this in error, please contact the sender and delete the material from any<BR>
>> computer.<BR>
>><BR>
>> ________________________________<BR>
>><BR>
>> Help make the earth a greener place. If at all possible resist printing this<BR>
>> email and join us in saving paper.<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>
>> <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>
</FONT>
</P>
</BODY>
</HTML>
<HTML><BODY><P><hr size=1></P>
<P><STRONG>
The substance of this message, including any attachments, may be confidential, legally privileged and/or exempt from disclosure pursuant to Massachusetts law. It is intended solely for the addressee. If you received this in error, please contact the sender and delete the material from any computer.
</STRONG></P></BODY></HTML>
<P><hr size=1></P>
<P><STRONG><font size="2" color="339900"> Help make the earth a greener place. If at all possible resist printing this email and join us in saving paper. </p> <p> </font></STRONG></P>