Add "colour style" to the make-command. This gives the opportunity to give the map a special design, e.g. giving the country bounderies a special (darker) colour for a colour-filled map without predefining all that maps.
Greetings
Fred
Post requests for Digital Atmosphere V1.2 work
Export chart
Export chart: give the chart a name (e.g. Test) and a type (e.g. GIF) and save the chart. If you try to save the chart under the same name but a different type (JPG) it continues saving under the same type, even if you delete the file before you save. Saving under another name (Test-1) will do the trick.
Fred
Fred
-
Weasel
Gradient Fill
I know this is being worked on for a future release...
I was wondering if the pixel size could be reduced a bit when this feature is added to DA WS? Often times when blending the yellows, oranges and reds in the "Old" version, the oranges end up with a 'blocky' appearance. Perhaps reducing the pixel size would provide for a smoother color transition?
I like the gradient fill feature as it doesn't depend on an absolute value as does the current overfill option. Although overfill does a nice job with upper air winds!!
Thanks
Pat
I was wondering if the pixel size could be reduced a bit when this feature is added to DA WS? Often times when blending the yellows, oranges and reds in the "Old" version, the oranges end up with a 'blocky' appearance. Perhaps reducing the pixel size would provide for a smoother color transition?
I like the gradient fill feature as it doesn't depend on an absolute value as does the current overfill option. Although overfill does a nice job with upper air winds!!
Thanks
Pat
-
DG Cashion
- Junior Member
- Posts: 6
- Joined: Mon Sep 20, 2004 10:48 pm
- Location: Cazenovia, Woodford, Illinois, USA
Radar Refresh
I'm finding that a couple of the tasks that I am constantly repeating, often unsuccessfully since I'm the impatient type, getting the latest data for radar during storm threats in our area.
With the varied places, bandwidth and usage there are a couple things I'd like to suggest.
1. Have a interval based (I think I've mention this before) 'watch list'. Have a list of files that the date/time stamp is checked every X minutes or seconds. If the date/time stamp is different then it downloads the new file...if it hasn't changed then leave it alone.
2. Once it has found a new file and downloaded it notify me audibly without pushing DAWS to the front. I'd settle for a wav that says 'Hey Dummy you got a new radar file you need to view'
But it allows me to manage critical tasks - always a consideration in small ESDA's where one person may run several radios, notification processes, radar, field spotters, etc.
3. Even with DSL in the EOC if every machine was running five or six applications (such as DAWS for NEXRAD, UI-View to track field resources, a EMWIN product, etc) and had to individual download the data we wouldn't have the bandwidth to keep up. So over the last month or so we have replaced standalone software with client/server based applications. One machines 'pulls' the data now and distributes or makes available the data to every machine. This has cut our bandwidth utilization by 75% and given every workstation the same data instead of having X machines each dedicated to a single application and chasing all over to gather information. Is it possible to go to this client/server type system?
With the varied places, bandwidth and usage there are a couple things I'd like to suggest.
1. Have a interval based (I think I've mention this before) 'watch list'. Have a list of files that the date/time stamp is checked every X minutes or seconds. If the date/time stamp is different then it downloads the new file...if it hasn't changed then leave it alone.
2. Once it has found a new file and downloaded it notify me audibly without pushing DAWS to the front. I'd settle for a wav that says 'Hey Dummy you got a new radar file you need to view'
But it allows me to manage critical tasks - always a consideration in small ESDA's where one person may run several radios, notification processes, radar, field spotters, etc.3. Even with DSL in the EOC if every machine was running five or six applications (such as DAWS for NEXRAD, UI-View to track field resources, a EMWIN product, etc) and had to individual download the data we wouldn't have the bandwidth to keep up. So over the last month or so we have replaced standalone software with client/server based applications. One machines 'pulls' the data now and distributes or makes available the data to every machine. This has cut our bandwidth utilization by 75% and given every workstation the same data instead of having X machines each dedicated to a single application and chasing all over to gather information. Is it possible to go to this client/server type system?
-
Mark Trueman
- Member
- Posts: 10
- Joined: Thu Jan 08, 2004 7:52 pm
- Location: Salt Spring Island, Canada
Re: Post requests for Digital Atmosphere V1.2 work
My suggestions:
1. New variables:
a.) pseudoequivalent wet-bulb potential temperature (theta-w) and saturated theta-w. This would be useful for analyzing LI, cap strength and lifted surface parcel temperature at different pressure levels.
b.) CAPE and CIN
Obviously, these quantities will require using data from upper and surface files simultaneously.
c.) Potential vorticity
d.) Bunkers storm-motion vector field (again, computed from both upper and surface files).
2. Basic vector operations in scripting (e.g., subtracting a constant vector from all grid points)
3. Ability to manipulate several data files from different times (e.g., useful for compositing data from several different days, or for computing tendencies).
4. More sophisticated math tools in scripting (e.g., finite differencing for approximating gradients).
5. Enhanced drawing functionality (e.g., multiple draw layers and deeper undo cache).
6. Ability to control density of wind plots in gridded output. It would be nice to be able to skip plotting every other vector.
Finally, I'd like to re-iterate someone else's suggestion to make a button that allows the user to save a raw data file in a specific location. I'd like to add the suggestion to give the user the ability to make a given location the default folder for storing the data. I find that most of my time is eaten up going into the DAWS\data folder, copying and pasting the latest 'incoming' file to my archive data folder of choice.
1. New variables:
a.) pseudoequivalent wet-bulb potential temperature (theta-w) and saturated theta-w. This would be useful for analyzing LI, cap strength and lifted surface parcel temperature at different pressure levels.
b.) CAPE and CIN
Obviously, these quantities will require using data from upper and surface files simultaneously.
c.) Potential vorticity
d.) Bunkers storm-motion vector field (again, computed from both upper and surface files).
2. Basic vector operations in scripting (e.g., subtracting a constant vector from all grid points)
3. Ability to manipulate several data files from different times (e.g., useful for compositing data from several different days, or for computing tendencies).
4. More sophisticated math tools in scripting (e.g., finite differencing for approximating gradients).
5. Enhanced drawing functionality (e.g., multiple draw layers and deeper undo cache).
6. Ability to control density of wind plots in gridded output. It would be nice to be able to skip plotting every other vector.
Finally, I'd like to re-iterate someone else's suggestion to make a button that allows the user to save a raw data file in a specific location. I'd like to add the suggestion to give the user the ability to make a given location the default folder for storing the data. I find that most of my time is eaten up going into the DAWS\data folder, copying and pasting the latest 'incoming' file to my archive data folder of choice.
-
britbob
- Senior Member
- Posts: 223
- Joined: Sun Nov 07, 2004 6:38 pm
- Location: Gouda, Netherlands
- Contact:
Yes, I too would like to see the the gif/pallette issue fixedWally Mayo wrote:Exported charts as .gif render colors a bit differently than on screen or if saved as .bmp
That is, the bitmap exports do the color pallete exactly, while with gif exported charts the color pallete is modified or corrupted somehow.
Can the gif exports be fixed to be as accurate as the bitmaps?
And would like the highs/lows plotting option with ASUS fronts to be independent of the drawing box highs and lows as far as enabling.
One more suggestion for now: add the ability to loop frames. This could be used in three ways:
1. Allowing one to vizualize how the surface observations and analyzed fields change over time.
2. Allowing one to move quickly between upper-level plots/analyses at various levels, and between the upper analyses and surface observations.
3. Allowing one to view various analyzed fields on one set of observations across several frames instead of cluttering up one map with spaghetti.
1. Allowing one to vizualize how the surface observations and analyzed fields change over time.
2. Allowing one to move quickly between upper-level plots/analyses at various levels, and between the upper analyses and surface observations.
3. Allowing one to view various analyzed fields on one set of observations across several frames instead of cluttering up one map with spaghetti.