Opened 23 years ago
Closed 23 years ago
#51 closed defect (invalid)
diffrent shape file used in a tile index
Reported by: | assefa | Owned by: | sdlime |
---|---|---|---|
Priority: | high | Milestone: | |
Component: | MapServer C Library | Version: | 3.5 |
Severity: | normal | Keywords: | |
Cc: |
Description
Here is what I found working on some one's bug : I have a tile index referencing to 2 shape files. These 2 shape files have a TEM_LABEL attribute in their respective DBF files but the position of this attriubue is diffrent : in the first file the attribute TEM_LABEL is the 77th attribute and in the 2nd file the attribute is the 52nd). While displaying the layers, the first layer seems to be displayed properly, but when passing through the second layer I get a core dump at : //file mapxbase.c function msDBFGetValueList. values[i] = strdup(msDBFReadStringAttribute(dbffile, record, itemindexes[i])); The reason for that is that, it is trying to access the 77th attribute but the number of attributes for the 2nd layer is 52. I think the layer->iteminfo has to be upadted to reflect the second layer, although I am not sure of this Comments from Steve Lime : One could consider this a bug or messy data setup. Tiled layers are supposed to be identical in every sense of the word. Same items, same number of items and same item order. I'll have to look closer at the tiled shapefile code to understand the impact. In the meantime you'll need to fix the data to conform to the definition of tiled data that is used. Please file a bug report if you would.
Note:
See TracTickets
for help on using tickets.