Todays mapserver head banging problem

[Ed McNierney]

Steve -

Do all the shapefiles for that TILEINDEX set have the same number of
attribute columns, in the same order?

	- Ed

Ed McNierney
President and Chief Mapmaker
TopoZone.com / Maps a la carte, Inc.
73 Princeton Street, Suite 305
North Chelmsford, MA  01863
Phone: +1 (978) 251-4242
Fax: +1 (978) 251-1396
ed at topozone.com 

-----Original Message-----
From: UMN MapServer Users List [mailto:MAPSERVER-USERS at LISTS.UMN.EDU] On
Behalf Of Stephen Woodbridge
Sent: Sunday, March 11, 2007 6:01 PM
To: MAPSERVER-USERS at LISTS.UMN.EDU
Subject: Re: [UMN_MAPSERVER-USERS] Todays mapserver head banging problem

More information ...

It looks like it is probably a tileindex problem and that there are two
data layers in the same coverage area and the second one that I had not
noticed seems to be the problem. I'm not sure what the problem is but
removing that layer allowed the image to be drawn.

If I can figure this out, I will file a bug, or take it up on the dev
list.

<rant>
My feeling is that we should detect issues and report helpful messages
so people don't waste hours and/or days fighting with issues and obscure
error messages. We have had discussions about logging the filename that
an associated error message is related to. If the error messages below
had had the file name included, it would have taken about 5 minutes to
diagnose the problem.
</rant>

-Steve W

Stephen Woodbridge wrote:
> I have a problem with a shapefile(?) or mapfile(?) for street data 
> that I have spent all day banging my head against.
> 
> mapserver 4.10.0 and CVS both are reporting:
> 
>> [Sun Mar 11 16:00:18 2007].666330 msDrawMap(): Layer 8 (Streets A30 
>> Z3 0), 0.006s Sun Mar 11 16:00:18 2007 - msDBFGetItemIndex(): DBASE 
>> file error.
>> Invalid record number 81000.
>> Sun Mar 11 16:00:18 2007 - msDrawMap(): Image handling error. Failed 
>> to draw layer named 'Streets A20 Z3'.
> 
> this shapefile only has 12121 records in it. I thought that maybe the 
> file was bad so I loaded it into postgres and dumped it to a new file 
> and I get the same error. The layer and shapefile definitions are
below.
> Anyone have any idea what is going on or how to debug this?
> 
> -Steve W
> 
>       LAYER
>         NAME "Streets A30 Z3 0"
>         GROUP "st"
>         STATUS DEFAULT
>         DATA "./Mexico/Major_roads/mexst"
>         TYPE LINE
>         MAXSCALE 500100
>         MINSCALE 50100
>         FILTERITEM "FCC"
>         FILTER "A30"
>         CLASS
>           STYLE
>             COLOR 170 153 34
>             WIDTH 4
>             ANTIALIAS TRUE
>           END
>           STYLE
>             COLOR 238 187 34
>             WIDTH 2
>             ANTIALIAS TRUE
>           END
>         END
>       END
> 
> woodbri at carto:/u/data/Mexico/Major_roads$ dbfdump -info mexst
> Filename:       mexst.dbf
> Version:        0x03 (ver. 3)
> Num of records: 12121
> Header length:  449
> Record length:  371
> Last change:    1995/7/26
> Num fields:     13
> Field info:
> Num     Name            Type    Len     Decimal
> 1.      ID              N       19      11
> 2.      NAME            C       75      0
> 3.      NAME_ALT        C       80      0
> 4.      FCC             C       3       0
> 5.      FCC_ALT         C       6       0
> 6.      LEN_MILES       N       19      11
> 7.      LEN_KM          N       19      11
> 8.      SPEED_MPH       C       3       0
> 9.      SPEED_KMH       C       50      0
> 10.     CITY            C       16      0
> 11.     CITY_ALT        C       32      0
> 12.     COUNTRY         C       16      0
> 13.     COUNTRYALT      C       32      0