From cc38a94ac9ced80db9fec3789fdad37a5893912e Mon Sep 17 00:00:00 2001 From: finity69x2 <32221243+finity69x2@users.noreply.github.com> Date: Tue, 21 Mar 2023 06:23:28 -0400 Subject: [PATCH] Update lookup_options.md --- lookup_options.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/lookup_options.md b/lookup_options.md index 2f9b3be..aac18f2 100644 --- a/lookup_options.md +++ b/lookup_options.md @@ -7,6 +7,8 @@ The county-based alert lookup relies on geographic boundaries defined by county ## Zone (recommended method) The final method, zone-based alert lookup, relies on geographic boundaries defined by the NWS based on weather patterns and conditions. Zones can vary in size and shape and are often used in areas with complex topography or microclimates where weather conditions can differ significantly over short distances. By defining zones based on weather patterns, the NWS can issue more targeted and precise alerts that consider each zone's unique conditions. Zone-based queries are the recommended method for most users. +NOTE: The NWS Alerts integration will use both of the above (County and Zone) if you select the "Zone ID" lookup method in the integration configuration. + ## Coordinate (most precise) On the other hand, the point-based alert lookup uses the user's precise location (based on submitted coordinates) to query weather alerts for your specific location. This method provides more accurate and targeted information, particularly useful for users who live or work in areas with microclimates or complex topography. However, this method may delay awareness of severe weather developing in the user's region.