Shapefile field problem

[Abe Gillespie]

Nope, all pretty standard like NAME, FULLADDR, etc.  Nothing blatantly
weird.

-Abe

On Dec 2, 2004, at 11:41 AM, Ethan Alpert wrote:

>
>
> This is interesting what are the field names? Any of them start with
> numbers?
>
> -e
>
> -----Original Message-----
> From: UMN MapServer Users List [mailto:MAPSERVER-USERS at LISTS.UMN.EDU]
> On
> Behalf Of Abe Gillespie
> Sent: Thursday, December 02, 2004 9:32 AM
> To: MAPSERVER-USERS at LISTS.UMN.EDU
> Subject: Re: [UMN_MAPSERVER-USERS] Shapefile field problem
>
>
> I certainly will as soon as I have the chance.  I'm working on getting
> this project out the door so I don't have much time right now.  I've
> encountered "problematic" fields in the past where when MapServer
> encounters a problematic field it drops it and any fields after it.
> What
> I have done is just deleted fields that gave me problems and then the
> other "good" fields would show up.  I thought it had to do with NULLs
> in
> these fields.  Now one of the problematic fields is one I need to *use*
> ... so I can't exactly delete it.  I can attach the files if so
> desired.
> Is it ok to simply attach files and post to the group?
>
> Are there any tools I can use to check the integrity of a shapefile
> (and
> the shapes / records within said file)?
>
> Thanks.
> -Abe
>
> On Dec 2, 2004, at 11:05 AM, Frank Warmerdam wrote:
>
>> On Thu, 2 Dec 2004 11:19:01 -0500, Abe Gillespie <agillesp at vt.edu>
>> wrote:
>>> I used ogrinfo and it shows all the fields just fine.  Specifically
>>> I'm trying to get a roads layer to work.  I need to use the NAME
>>> field for labeling and querying.  But MapServer doesn't seem to
>>> recognize this field (or any other fields past NAME).  Oh, also, this
>
>>> is my MapServer
>>> configuration:
>>>
>>> MapServer version 4.2.0 OUTPUT=GIF OUTPUT=PNG OUTPUT=WBMP
>>> SUPPORTS=FREETYPE INPUT=TIFF INPUT=EPPL7 INPUT=JPEG INPUT=SHAPEFILE
>>
>> Abe,
>>
>> I don't know what is going wrong, but if you are keen to get a fix I
>> would encourage you to try and reproduce the problem with 4.4, and if
>> "successful" to report a detailed bug report along with the file, and
>> everything needed to reproduce the problem.  Also note the actual
>> binaries you downloaded that resulted in the problem.
>>
>> I'm quite surprised by the problem you are encountering, but it
>> doesn't sounds like it is really in my area.  Hopefully Steve will
>> pick up on it.
>>
>> Best regards,
>>
>> --
>> ---------------------------------------
>> +--------------------------------------
>> I set the clouds in motion - turn up   | Frank Warmerdam,
>> warmerdam at pobox.com
>> light and sound - activate the windows | http://pobox.com/~warmerdam
>> and watch the world go round - Rush    | Geospatial Programmer for
> Rent
>>
>