tileindex: sequence of attributes in individual shapefiles matter s
Stephen Woodbridge
woodbri at SWOODBRIDGE.COM
Wed Mar 29 09:11:00 PST 2006
Bart,
Can I suggest you write a bug against ogrtindex as this is a requirement
for mapserver to function and it save a lot of headaches to catch it
early on.
-Steve W.
Bart van den Eijnden (OSGIS) wrote:
> Hi Steve,
>
> okay, good to know tile4ms checks for this sort of thing, ogrtindex
> doesn't throw errors ...
>
> Best regards,
> Bart
>
> Stephen Woodbridge wrote:
>
>> Hi Bart,
>>
>> It does fetch by name from the first file that is opened but then
>> remembers the indexes. If you use tile4ms, this now checks for these
>> kinds of errors and trows and error. Mapserver can open 10 of
>> thousands of files when drawing a layer and this would add a lot of
>> additional overhead to fetch the column numbers based on names for
>> every file.
>>
>> I know it is a pain, but your should fix the data. It would not be
>> hard to write a little perl script to read the dbf file and reorder
>> the attributes.
>>
>> -Steve W
>>
>> Eijnden, B. van den (Bart) wrote:
>>
>>> Hi list,
>>>
>>> today we encountered that the sequence of attributes of the individual
>>> shapefiles which were used in a tile-index are important. In 3 out of 4
>>> shapefiles the CLASSITEM column was the 3rd column, but in the 4th
>>> shapefile
>>> it was the 4th column, so that one did not show up in the map ....
>>>
>>> Apparently Mapserver fetches attribute values based on a column
>>> index? Would
>>> it be better to fetch by name? Otherwise I think this requirement
>>> should be
>>> documented somewhere.
>>>
>>> Best regards,
>>> Bart
>>>
>>>
>>> Disclaimer
>>> ************************************************************************
>>> Aan dit bericht kunnen geen rechten worden ontleend. Dit bericht is
>>> uitsluitend bestemd voor de geadresseerde. Als u dit bericht per abuis
>>> hebt ontvangen, wordt u verzocht het te vernietigen en de afzender te
>>> informeren. Wij adviseren u om bij twijfel over de juistheid of de
>>> volledigheid van de mail contact met afzender op te nemen.
>>>
>>> This message shall not constitute any rights or obligations.
>>> This message is intended solely for the addressee.
>>> If you have received this message in error, please delete it and
>>> notify the sender immediately. When in doubt whether this message
>>> is correct or complete, please contact the sender.
>>> ************************************************************************
>>>
>>
>>
>
>
More information about the MapServer-users
mailing list