Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Visibility errors reading some METARs

Featured Replies

I have found that using Active Sky V1.5 (and FSUIPC 2.94) that some METARs are not being handled correctly in terms of visibility.Flying into NZWN and NZCH last night the visibility was quoted as 25KM and 15KM but Acitve Sky reads this incorrectly and shows it as only 1 mile (1.6km). This may be unique to New Zealand.I have copied this morning's METAR which has a similar visibility as an example:NZWN 082100Z 18008KT 30KM FEW015 BKN025 14/09 Q1009 NOSIG RMK KAUKAU 17008KTI have been searching everywhere this morning for an Australian station who was quoting visibility other than 9999 or CAVOK but couldn't find any! However, from memory I think we just quote the number of metres ie 3000 or 700 etc (but not sure on that one). It does seem though that New Zealand is different and this might be putting a spanner in the works.Just another note ... is a METAR visiblity of 9999 or CAVOK read correctly as >10KM?Also, although you have probably already addressed this - some of our METAR stations go from being manned during the day to automatic at night. At night, there is no visibility component (the same as other 24hr auto stations in Australia) and therefore it is quoted as //// in the METAR. Please see example below - do you know how this gets handled in Active Sky currently?YAYE 082230Z 17013KT //// 20/12 Q1015 RMK RF00.0/001.4 CLD:CLR BLW 125 VIS:////Any advice would be gratefully appreciated.

  • Commercial Member

Hi,This problem with KM vis handling was identified and is fixed in wxRE.The //// would not be processed and visibility would default to standard CAVOK style. In 1.5 there may be problems handling this unexpected data but it is improved in wxRE. I just checked and it appears to load fine. Thanks!-Damian[table border=0" cellspacing="30" cellpadding="0][tr][td align = "left"]Damian ClarkHiFi Simulation SoftwareDeveloper of ActiveSkyThe next-generation weather environment simulation for FS2002!http://hifi.avsim.net/activesky[/td][td]http://hifi.avsim.net/activesky/images/wxresmallbanner.jpg][/td][/tr][/table://http://hifi.avsim.net/activesky/ima...][/tr][/table

Damian Clark
HiFi  Simulation Technologies

Damien, I received this private eMail response from a user and although it doesn't affect me directly, I thought you might like the feedback. Regards, John ...I'm afraid that I had similar experience at LKPR - metar was giving vis = 0100 but the ActiveSky translated it as 1Mi visibility instead. In this respect I don't like ActiveSky and I lost my trust in itCiaoVladimir

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.