[mapserver-users] 3.5: how to handle empty DATA layers which were accepted in 3.4

[Steve Lime]

Layer handling was one of the biggest things that changed between
releases. So there may still be quirks. The point and shape draw methods
don't rely on the DATA element at all though. They just assume that you
have a valid shape with all the structural elements properly populated.

If you do a layer/map draw then you need valid DATA or inline features
but it sounds like you're not doing that.

Are you getting an error as the mapfile is parsed, when the draw method
is executed or what? I do what it to work as you've described.

Steve

Stephen Lime
Data & Applications Manager

Minnesota DNR
500 Lafayette Road
St. Paul, MN 55155
651-297-2937

>>> Andrea Giacomelli <andreag at crs4.it> 02/06/02 03:02AM >>>
Hi,

With 3.4 one of the approaches to draw points dynamically from a
database
was to have in the map file an layer without a DATA definition, which
was then populated with calls to $point->draw().

Apparently layers read by 3.5 MUST have a DATA property assigned.

The issue arises as I am using point data stored in an MS Access file.

Can a layer be appropriately defined in 3.5 in order achieve the same
result with the same logic ?

I know that 3.5 allows much more connectivity towards databases, but
for
this specific application (which is in fact a demo) I would like to
avoid porting also the data.

Regards,
-- 
=========================================
Andrea Giacomelli
=========================================