Page 2 of 2

Posted: Sun Aug 29, 2004 8:22 pm
by texsky
Pat,

The "ingest" function was created by Tim because "import" was causing problems with users who were trying to import both pre-drawn maps and data, all within the same script. Therefore, to resolve the conflict, Tim simply separated the two functions..."ingest" for data, and "import" for maps.

hth,
Bob

Posted: Mon Aug 30, 2004 5:15 am
by Klaus Breddemann
Thanks again Bob.

Wrt fronts I have tried the following script:

download,http://www.hamweather.net/weather/asus0 ... tm\frt.dat
ingest,c:\DigAtm\frt.dat
PRODUCT,WXP,0,FRT

Now something funny did occur when running the script:
1. when including the line "ingest ... etc." - there was no display of a plotted front at all
2. and without the line "ingest ... etc" - solid and dashed black lines were criss-crossing my map.

I also noticed when including the fronts-script in my script for analyzing pressure, winds etc. ( taking your advise to include as the last line) the whole display was corrupted and I even had to reboot my PC

Reading in front related topics, it appears that plotting fronts are quite troublesome - or did I write the script incorrectly?

In any case, I find Tim's program absolutely great and hope he keeps up the good work. Hopefully wave/swell analyzes and hurricane tracking will be included soon.

Wished there would be a separate section in the forum just for posting scripts which actually work, in order to get some ideas and to minimize hours spent on frustrating trials.

Rgds
Klaus

Another mystery solved

Posted: Mon Aug 30, 2004 7:16 am
by Klaus Breddemann
By playing around with my fronts script, I finally discovered what went wrong.

I was working with a map of the NW Pacific and got these strange lines as mentioned in my earlier posting. By switching to a map of the USA and then running my fronts script I got perfectly drawn fronts without any other garbage lines.

The "error" I can see now, derived from the fact that I believed the URL address would cover the fronts system worldwide, while in fact it only covered the USA. Therefore I saw only strange and overlapping lines on my map from the USA to the NW Pacific.

It also prooved, that my script (as posted earlier) was correct and that it was necessary to invoke the line "ingest ... etc."

Now, does anybody knows a site which covers the fronts system worldwide or at least the NW Pacific?

Posted: Mon Aug 30, 2004 3:59 pm
by texsky
Klaus,

The frontal bulletin is a product designed for North American use only. However, there's something called Fleetcode that covers Western Europe that basically does the same thing, plus it includes isobars as well.

Also, keep in mind that the frontal bulletin is updated once every 3-4hrs, so it may not represent timely or even accurate information.

hth,
Bob

Posted: Tue Aug 31, 2004 12:13 am
by Weasel
Klaus,

This is a script to archive weather data, as well as update the display of wind barbs, contoured slp, and station plots within DAWS. I decided not to export the map to an image file as the data can be retrieved later. This script downloads metars and buoy data, although I'm not certain both plots will display, as there is some sort of conflict in DAWS between metar and bouy data, both are saved and can be loaded seperately. So create the directory c:weatherarchive and start saving data!! Pick whatever colours you prefer, i chose green for wind barbs because I like green (yellow for station plots from the styles preferences) and I use a black background:)

download,http://www.atmos.albany.edu/weather/dat ... HZ_sao.wmo
download,http://www.atmos.albany.edu/weather/dat ... HZ_boy.wmo
ingest,C:\weatherarchive\@YYZ@MMZ@DDZ@HHZ_sao.wmo
erase
analyze,HILO CONT CINT=1 LINE=2 SLPR
analyze,BKNT COLOR=0:200:0 WIND
product,plf,0

Pat

Posted: Tue Aug 31, 2004 12:23 am
by Weasel
Klaus, regarding the above script, times are again set through the scheduler. I would suggest updating the map at 45 or 50 minutes past the hour for every hour. While the display will be a little dated by this time, It does allow more stations to be added for archiving purposes. Perhaps even updating at 25 after and 50 after would be a good way to go, as you can get a good look, most of the time, at 25 after, and then a better look, and a better more complete archive file at 50 after. Don't worry, the saved data file is updated as the newer file is downloaded if you choose the latter approach.

Pat

Posted: Tue Aug 31, 2004 6:28 am
by Klaus Breddemann
Thanks Pat, your sample script is really great. I never thought of archiving in this manner. BTW I have run your script and DAWS apparently did not find any inconsistencies with meta and buoy data or otherwise did not behave differently.

What puzzles me a bit are the different file extensions in use by various sites like .wmo, .dat, .txt. Does it mean that DAWS is able to analyze whatever file extension is being used, or what is the meaning of it?

Thanks also for the scheduling tip. I already noticed different file sizes occurring within the hour ranging from 20K to original 700K.

I am living in the Far East and naturally I am interested in the weather of the South China Sea and NW Pacific to be applied to my profession. I was using an excellent site run by the US Navy (of wich the Joint Typhoon Warning Centre [JTWC] is included in DAWS). Unfortunately they will restrict usage by the public from 1. October onwards and have posted a new link to their new site, which in my opinion is not on par of what is available up to now. I am still on the lookout for fronts data covering the NW Pacific, so if you or anybody comes across something, I would be very grateful.

Any other useful script available? Here's the place to dump it.

Rgds
Klaus