Opened 17 years ago

Closed 17 years ago

#230 closed defect (fixed)

Polygon features randomly appear and disappear

Reported by: jng Owned by: trevorwekel
Priority: high Milestone:
Component: General Version: 1.2.0
Severity: critical Keywords:
Cc: External ID: 954036

Description

There is this really strange bug where certain polygon features randomly appear and disappear as you pan around the map.

I have attached a package with the suspect data in question. It contains:

odbc.FeatureSource - Which contains a connection to an embedded ms access database.
Plots.FeatureSource - A feature source that is joined to odbc.FeatureSource (1:1 left outer join)
Plots.LayerDefinition - A layer using the original feature class in Plots.FeatureSource
Status.LayerDefinition - A layer using the extended feature class in Plots.FeatureSource
Test.MapDefinition - A map containing both layers.
Test.WebLayout - The weblayout containing the map.

Seeing the bug in action:


1) Open the map or web layout.
2) Pan to the lower right region of the map.
3) Activate the "Status" layer. You will see the themed objects.
4) De-activate the "Plots" layer. Nothing should change because both layers reference the same feature source, left outer 1:1 join means that both layers should have the same number of features. If not, you are starting to see the bug in action.
5) Pan around that region of the map, random objects from the layer "Status" will appear and disappear on each pan, regardless of the theme rules applied.

Extra Notes:


Environment:

  • Windows XP SP2
  • MapGuide Open Source 1.2.0 RC2 w/ PHP web server extensions.
  • Plots.FeatureSource was originally an ESRI Shape file exported from Autodesk Map3D 2007 that was converted to Autodesk SDF in MapGuide Studio 2008.
  • When I originally discovered this bug, the odbc data source was pointing to a SQL Server 2005 Express database. As I was able to reproduce this with an Access Database, I don't believe the external odbc data source has any factor.

Attachments (1)

Bug.mgp (162.3 KB ) - added by jng 17 years ago.
Package containing the problematic data

Download all attachments as: .zip

Change History (7)

by jng, 17 years ago

Attachment: Bug.mgp added

Package containing the problematic data

comment:1 by jng, 17 years ago

Severity: blockercritical

More notes:

  • Trying to analyse the extended feature class via the schemareport causes MgUnclassifiedException errors to be thrown.
  • Exported the same layer to MapGuide from Map, but this time directly to SDF from AutoCAD Map3D 2008. Bypassing the CAD -> SHP -> SDF process. And the problem seems to have gone away. I suspect there may be some kind of problem in the SHP -> SDF conversion in MapGuide Studio that resulted in a corrupted SDF?

comment:2 by jbirch, 17 years ago

Resolution: invalid
Status: newclosed

I believe that this is a Studio problem. I'm going to close this ticket and let it go through the ADSK channels.

comment:3 by mmicall, 17 years ago

Resolution: invalid
Status: closedreopened

I am using a straight polygon shapefile joined with an access odbc connection to a table within the database. The information is themed against one of the resultant joined fields.

When I am zoomed out - some of the records display with the correct symbol - when I zoom right in on a polygon it may or may not switch to another colour and if I pan and I am zoomed in really close it might display the proper classification symbol.

Seems similar as above issue - only using a shapefile.

I did notice that the field definition of the schema for the shapefile and the access table are different within ArcMap (used to review data). In the fields tab of the layer properties form, the precision and length are different for the joining fields.

I have tried to make them the same but was unable.

First time posting - advanced apologies!

Mike Micallef

comment:4 by tomfukushima, 17 years ago

Owner: set to trevorwekel
Status: reopenednew

comment:5 by tomfukushima, 17 years ago

External ID: 954036

comment:6 by brucedechant, 17 years ago

Resolution: fixed
Status: newclosed

This has been fixed with the submissions for tickets 292, 413 and 429.

Note: See TracTickets for help on using tickets.