Opened 14 years ago

Closed 14 years ago

Last modified 14 years ago

#3259 closed defect (duplicate)

PHP/mapscript fails to draw map zoomed in with 'MULTIPOLYGON' layer in mapserver g.t. 5.0.2

Reported by: basic999 Owned by: pramsey
Priority: normal Milestone:
Component: PostGIS Interface Version: unspecified
Severity: normal Keywords:
Cc: tbonfort

Description

Program in PHP/mapscript uses zoompoint to zoom in. With complicated 'MULTIPOLYGON' layers included , ie stewardship layers in example attached map will display only zoomed out all the way in releases greater than 5.0.2. Have tried 5.2.3, 5.4.2, and 5.6.1 all with same failure.

Attachments (3)

shp2img_dbg.txt (15.0 KB ) - added by basic999 14 years ago.
shp2img out for mapserver 5.0.2 and 5.6.1
shp2img_5_6_1_full.txt (24.5 KB ) - added by basic999 14 years ago.
shp2img_dbg_shpfile.txt (26.4 KB ) - added by basic999 14 years ago.
changed layer gapown from postgis to shapefile

Download all attachments as: .zip

Change History (16)

comment:1 by basic999, 14 years ago

database dump and source code were too large for upload. ftp from ancalagon.zo.ncsu.edu/anonymous In /out/OG_pub get database dump ncgap_12_28_2009 and code bug.tar.gz.

comment:2 by pramsey, 14 years ago

Can you supply the layer name of interest, an extents that works, and an extents that does not work?

Ideally, use those to test with shp2img and see if the problem is in the core mapserver engine, rather than mapscript.

Finally, for extra bonus marks, dump the database table to a shape file and see if the problem manifests there too.

The more you can narrow down the problem and the reproduction of the problem, the easier it is for a developer to quickly pick it up and fix it.

Thanks!

by basic999, 14 years ago

Attachment: shp2img_dbg.txt added

shp2img out for mapserver 5.0.2 and 5.6.1

comment:3 by basic999, 14 years ago

Hi,

I turned on layers counties and gapown and and set extent to a zoomed extent. Ran shp2img compiled in 5.0.2 and produced a map. Ran shp2img compiled with 5.6.1 and failed to make a map. Attached output with -all_debug 2 for both. layers gapown, gapman, and gapsta all fail in same way. These 3 layers were made from same input by a pl/pgsql script.

will work on getting a test using the shapefile.

by basic999, 14 years ago

Attachment: shp2img_5_6_1_full.txt added

comment:4 by basic999, 14 years ago

Hi,

Attached output for mapserver 5.6.1 at default extent, which always works.

by basic999, 14 years ago

Attachment: shp2img_dbg_shpfile.txt added

changed layer gapown from postgis to shapefile

comment:5 by aboudreault, 14 years ago

basic999, what zoomed extent are you trying to produce?

comment:6 by aboudreault, 14 years ago

nvm, I've just noticed the extent in the log file.

comment:7 by aboudreault, 14 years ago

What failure do you get ? I think I'm not getting the same bug than you... with 5.6.1/trunk... using the extent 806873 188697 969149 273715, mapserver/shp2img never ends. I'm investigating in the problem...

comment:8 by aboudreault, 14 years ago

Cc: tbonfort added

It looks like your POLYGONS (I've only tested gapown) have an invalid exterior ring (probably not closed ?) and that AGG is unable to add a pattern/path for the HATCH symbols with those polygons. The code has a little bit changed in the mapserver agg renderer. Perhaps tbonfort would know what's the problem. Everything seems to work if we use GD renderer rather than AGG, or if we simply don't use HATCH symbol. basic

comment:9 by pramsey, 14 years ago

Looks like the same thing as #3207 ?

comment:10 by aboudreault, 14 years ago

effectively. basic999, may you confirm us that we are experiencing the same behavior? to close this ticket.

comment:11 by basic999, 14 years ago

I have tested both of these changes, ie use GD instead of AGG and comment out the hatch-lines and with either of these changes did draw a map using mapserver-5.4.2/shp2img.

At this point do I need to make a choice to stay with 5.02, not use AGG or not use the hatch, or will this be fixed when #3207 is resolved?

comment:12 by aboudreault, 14 years ago

Resolution: duplicate
Status: newclosed

We will of course fix this bug, not sure when though. I'm going to add you in CC in the other ticket.

Closing this ticket since it is a duplicate of #3207.

comment:13 by basic999, 14 years ago

I applied patch from #3207 on 5.6.1. It worked and my site is now running 5.6.1 with no problems.

Thanks.

Note: See TracTickets for help on using tickets.