Erase basemap problem
Posted: Mon Jul 24, 2006 6:49 pm
This was a problem with the previous edition of DAWS.
For example, I run a surface script each six hours and then run an upper air script every twice daily on the scheduler.
The surface analysis uses basemaps of a different colour and size to those that the upper air scripts use.
The surface script will run through fine, then a few hours later the upper scripts will start up. It`s here where we see a problem. Fusion and DAWS does not want to completely remove the former basemap or dimensions from the surface script run. Thus the finished product is a mess, with a blend of two different sized basemaps.
Essentially in scripting, we cannot use different size or coloured basemaps. They must be identical?
Am I correct in thinking the erase command should be removing all basemap features ready for a new one?
For example, I run a surface script each six hours and then run an upper air script every twice daily on the scheduler.
The surface analysis uses basemaps of a different colour and size to those that the upper air scripts use.
The surface script will run through fine, then a few hours later the upper scripts will start up. It`s here where we see a problem. Fusion and DAWS does not want to completely remove the former basemap or dimensions from the surface script run. Thus the finished product is a mess, with a blend of two different sized basemaps.
Essentially in scripting, we cannot use different size or coloured basemaps. They must be identical?
Am I correct in thinking the erase command should be removing all basemap features ready for a new one?