UniATIS forum

Metar custom function now supports regular expression and instead of searching for weather from the decoded weather the search will now be done on the METAR itself. This will make the function much more flexible along with the regular expression pattern match.

Magvar in the settings needs be set to desired value which is then added to %mwdeg_t% under the winds section, whereas %mwdeg% contains the value from METAR as is.

VV was replaced by 'no clouds' message when there was no clouds present in METAR. It's been altered to take VV into count as well.

If you need changes to the ATIS formats you should contact Wills Damasio, who is in charge of the ATIS formats in Brazil.

It was a bug this time. The problem was with determining whether the surface condition points to a single runway or runway left, as the left runway isn't separately indicated in the report like the right one is. It was working fine as long as the report also included condition report for the runway ...

You seem to be missing %cumulus% in the format. EFHK: cloud_grp :FEW:[few]%cumulus%%cloudft_u% cloud_grp :SCT:[scattered]%cumulus%%cloudft_u% cloud_grp :BKN:[broken]%cumulus%%cloudft_u% cloud_grp :OVC:[overcast]%cumulus%%cloudft_u% UKZZ: cloud_grp :FEW:[few]%cloudft_u% cloud_grp :SCT:[SCT]%cloudft_u...

METAR or more likely the whole URL that was used when error occured would always be most helpful. 1) I didn't find any problem with CB report. FEW/SCT/BKN/OVC always reported CB where included. 2) This is due to the settings: cloud_base :15000,SKC This means the following: clouds at or above 15000ft...

It was related to it as I guessed and I've fixed it.

I think it may be because of how the database handles arrays with {}... but it really shouldn't affect the values. Probably something else in connection to it, because it shows correctly on the page.

Add replaces in the custom based on the following example: replace:mcloud_grp:mcloud_grp:(.*)(\{500\})(.*)$:$1[quinhentos]$3 I didn't test it, but it should work. The key is to use '\' before '{' and '}' to mark those as characters and not as operators. (.*) simply means any lenght of any characters...