[postgis-devel] Re: [postgis-users] Changed bahaviour of PostGISconfuses MapServer

[Paul Ramsey]

Fair enough. Then I would like to change the PostGIS downloads page to
reference 1.3.3 in the interim... P.

On Sat, Dec 13, 2008 at 11:46 AM, Obe, Regina <robe.dnd at cityofboston.gov> wrote:
> -1
>
> Well I mean not ASAP.  Lets wait till at least Tuesday.   I agree it is a
> far reaching bug that I suspect affects many functions.  Anything that needs
> to extract a multi into individual linestrings will be affected.
>
> Then again I'm not convinced that many people have deployed into production
> and this to me would affect people who are unable to compile for themselves
> more than anyone else (e.g lots of windows users who have deployed) so we
> have to wait for Mark's +1 anyway.
>
> Besides I want to get the torture script further along to brute force test
> to make sure no other surprises.  So far the torture script
> tests all the functions that deal with one geometry, or 2 geometry or no
> args, but have yet to test for things that take other arguments (like all
> the Affine and so forth).
>
>
>
>
>
>
> -----Original Message-----
> From: postgis-devel-bounces at postgis.refractions.net on behalf of Paul Ramsey
> Sent: Sat 12/13/2008 12:13 PM
> To: PostGIS Users Discussion; PostGIS Development Discussion
> Subject: [postgis-devel] Re: [postgis-users] Changed bahaviour of
> PostGISconfuses MapServer
>
> Yes, Peter, I think it should call for a quick 1.3.5. Mapserver users
> are a huge contingent of PostGIS users, and anyone with a LINE layer
> now has a crasher. 1.3.5 should come off the line ASAP. There's always
> more version numbers, IMO.
>
> Can we have a quick vote on 1.3.5 release-from-branch, no-waities?
>
> +1
>
> P.
>
> On Sat, Dec 13, 2008 at 1:25 AM, Peter Hopfgartner
> <peter.hopfgartner at r3-gis.com> wrote:
>> Mark Cave-Ayland wrote:
>>>
>>> Peter Hopfgartner wrote:
>>>
>>>> Dear MLs,
>>>>
>>>> sorry for cross-posting to both, PostGIS and MS, but seems to rtouch
>>>> both.
>>>>
>>>> I've tried to install PostGIS 1.3.4 on a CentOS 5 server with MapServer
>>>> 5.2.1 and PostgreSQL 8.2.11.
>>>>
>>>> the command:
>>>>
>>>> shp2img -l prova -e 1587541 5116731 1591730 5120008 -m prova.map >
>>>> ../../public/technet/test-<pgis-version>.png
>>>>
>>>> with 1.3.3 gave the result shown in figure test-postgis-1.3.3-4.png (a
>>>> simple line layer)
>>>>
>>>> Upgrading to 1.3.4 the picture became as in test-postgis-1.3.4-1.png, an
>>>> empty picture.
>>>>
>>>> The relevant mapfile fragment is Mapfile.frag.txt, the SQL table
>>>> definition is e405.sql, all objects are MULTILINESTRINGs [SELECT
>>>> DISTINCT
>>>> geometrytype(the_geom) FROM public.e405 results in MULTILINESTRING], the
>>>> geometry column is registered as MULTILINESTRING in geometry_columns.
>>>>
>>>> Running the MapServer query:
>>>>
>>>> SELECT
>>>> asbinary(force_collection(force_2d(the_geom)),'NDR'),common_uid::text
>>>> from
>>>> public.e405 WHERE (tiplinapp is not null) and (the_geom && setSRID(
>>>> 'BOX3D(1587541 5116702.44897959,1591730
>>>> 5120036.55102041)'::BOX3D,find_srid('','public.e405','the_geom') ))
>>>>
>>>> changed for better result readability into:
>>>>
>>>> SELECT AsEWKT(force_collection(force_2d(the_geom))),common_uid::text
>>>> from
>>>> public.e405 WHERE (tiplinapp is not null) and (the_geom && setSRID(
>>>> 'BOX3D(1587541 5116702.44897959,1591730
>>>> 5120036.55102041)'::BOX3D,find_srid('','public.e405','the_geom') ))
>>>>
>>>> by hand gives slightly different results, as shown in the attached
>>>> files.
>>>>
>>>> To make a long story short, 1.3.4 seems to better preserve the
>>>> MULTILINESTRING, but this seems to confuse MapServer.
>>>>
>>>> Regards,
>>>>
>>>> Peter
>>>
>>>
>>> Hi Peter,
>>>
>>> This is likely the known issue with MULTILINESTRINGs in 1.3.4 causing
>>> segfaults :(  The patch you need is very simple and can be found here:
>>>
>>> http://postgis.refractions.net/pipermail/postgis-commits/2008-December/000866.html
>>> if you can't wait for a 1.3.5 release. Please let us know whether this
>>> resolves the problem for you.
>>>
>>>
>>> HTH,
>>>
>>> Mark.
>>>
>> Should this issue call for a quick 1.3.5 release? If I understood this
>> issue
>> well, everybody rendering PostGIS data stored as a MULTILINE geometry will
>> have this very same problem, at least with MapServer. I would guess that
>> this is quite a big share of PostGIS users that will be hit by this issue.
>>
>> Regards,
>>
>> Peter
>>
>>
>>
>>
>> --
>>
>> Dott. Peter Hopfgartner
>>
>> R3 GIS Srl - GmbH
>> Via Johann Kravogl-Str. 2
>> I-39012 Meran/Merano (BZ)
>> Email: peter.hopfgartner at r3-gis.com
>> Tel. : +39 0473 494949
>> Fax  : +39 0473 069902
>> www  : http://www.r3-gis.com
>>
>> _______________________________________________
>> postgis-users mailing list
>> postgis-users at postgis.refractions.net
>> http://postgis.refractions.net/mailman/listinfo/postgis-users
>>
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-devel
>
>
> ________________________________
>
> 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.
>
> ________________________________
>
> Help make the earth a greener place. If at all possible resist printing this
> email and join us in saving paper.
>
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-devel
>
>