When scripts are run which iterate over a number of times, there is an inconsistency in label size when using layer label, this behavior has also been seen in color bar labels, and annotations. This type of inconsistency will frustrate and cause users to move to a different system. I am currently trying to rectify the problem in this script which generated these images by only apply labels when necessary, setting the projection only once (while making sure that auto-set projection is off) and adding sleep statements. However, users should not have to worry about this much detail.
Joleen
animation at
ftp://ftp.ssec.wisc.edu/pub/ssec/jf/201 ... isanim.gif
You may notice there is an error in the label. This is not GOES-14 but GOES-13. I was modifying an old script and that was hard coded. Here is one solution to getting that information from the data....
Code: Select all
metaDataVIS, visibleData = getADDEImage(<parameters>)
sensorName = metaDataVIS["sensor-type"]
?sensorName
sensorNameSplit = sensorName.split(" ") #reconstruct name, split into array to make this easier
?sensorNameSplit
sensorName = sensorNameSplit[0] + '-' + sensorNameSplit[1] # I don't like this path because this could cause inconsistency. Ideas?
?sensorName
This returns:
GOES 13 imager # from metaDataVIS["sensor-type"] command
['GOES', '13', 'imager'] # the metaDataVIS.split(" ") command
GOES-13 # the final string