Create scientifically legible plots from verified NEXRAD single-site products
and decoded radar mosaics. Preserve site or domain, product, observation or
valid time, units, geometry, quality masking, and color meaning so a visually
compelling image cannot hide a wrong quantity or misleading spatial
interpretation.
Use this skill after nexrad-product-access or another trusted source has
provided a decoded site product. Use nexrad-mosaic-access to retrieve an
official MRMS composite before plotting it. This skill does not discover or
download radar files.
Level II moment for one NEXRAD site.
composite while preserving its grid, coverage, and product semantics.
for a target height.
provenance.
Do not use a plot to hide a missing sweep, unverified product, invalid gate mask,
geolocation error, or unsupported extrapolation.
Record:
orientation, valid-time semantics, and source/coverage or quality fields;
publication.
If the user asks only for “a radar image,” produce a useful default: a
single-site PPI with site marker, UTC time, product, units, color bar, range
rings, and missing-data treatment visible. For a decoded mosaic, use a map view
with the product, domain, valid time, units, legend, and missing-data treatment
visible. Ask only when product, site/domain, or time would materially change
the result and cannot be inferred safely.
projection.
interpolation, contouring, or thresholding.
or obtain beam height as a function of range and show which elevation is
nearest.
with zero, minimum reflectivity, or an opaque background that resembles weak
echo.
projection and origin.
their documented quality masks.
For a plan-position indicator:
missing gates according to an explicit policy.
scale appropriate to the quantity.
north arrow when orientation could be ambiguous, and optional geographic
context.
in the figure itself.
For reflectivity, do not imply that every dBZ color boundary is a categorical
precipitation type. Keep the measured reflectivity label visible and put any
rain-rate relation in a separate, explicitly derived layer.
For velocity, use a diverging scale centered on zero unless the product's
documented semantics require another convention. Radial velocity points toward
or away from the radar according to the data convention; it is not a full wind
vector. Do not draw environmental wind arrows from radial velocity without an
explicit deconvolution or retrieval method.
Preserve the physical unit for each field, such as differential reflectivity in
dB, differential phase in degrees, correlation coefficient as a unitless
quantity, and specific differential phase with its documented units and scale.
Keep raw dual-polarization fields separate from hydrometeor classification. If a
classification is displayed, state the input moments, thresholds, quality
masking, and whether the classification is measured, retrieved, or heuristic.
Do not normalize each sweep independently before an animation or comparison;
that can make a changing storm look stationary. Use one declared scale for the
whole sequence unless a separate panel is explicitly labeled.
Lowest-level products emphasize near-surface structure but are vulnerable to
terrain, clutter, biological targets, and beam broadening. Higher sweeps sample
different heights and can miss low-level features.
When selecting a sweep by target height:
Do not call the lowest sweep a surface observation. Its beam samples a volume
whose center height varies with range and whose width increases away from the
radar.
An RHI or cross-section is a derived view assembled from multiple sweeps or
volumes. Preserve source volume identity, azimuth or line orientation,
horizontal-distance coordinate, vertical coordinate, interpolation method, and
beam-height geometry.
Do not connect gates across large angular gaps, missing sweeps, or incompatible
volumes without showing the gap. Avoid implying sub-beam vertical resolution.
For a storm tilt sequence, use the same cross-section line or documented tracking
logic across times and show how the line moves.
For an animation or loop:
An animation is not evidence of temporal evolution unless frames are aligned,
correctly timed, and generated from the same product and projection.
For an MRMS or other decoded NEXRAD-derived grid:
projection, dimensions, coordinate orientation, and decoded extent.
mask before rendering. Preserve missing coverage as missing; do not turn it
into zero-valued precipitation or reflectivity.
with an explicit transformation and retain the native grid metadata.
color scale. Show coverage or source attribution when supplied with the
decoded data.
use nexrad-mosaic-construction for construction and label its output as a
local analysis.
Do not apply single-radar azimuth/range geometry or sweep labels to an MRMS
grid. Do not claim a mosaic represents every native radar moment or elevation.
Use the minimum visual elements needed to interpret the measurement:
orientation for gridded plots;
Avoid decorative terrain or boundaries that obscure gates, imply high
resolution, or dominate the measured field. Do not crop away the radar site,
range rings, or color bar without replacing the lost context.
For a multi-panel figure, label each panel by product and time and state whether
the panels share a scale. Use consistent geometry across panels so a viewer can
compare evolution without reorienting the scene.
Given a decoded KTLX volume, render the lowest usable reflectivity sweep with
the site, Level II moment, observed UTC time, dBZ units, color bar, range rings,
and invalid gates visibly masked. Read the timestamp and product metadata from
the volume rather than inventing them.
When comparing two velocity scans, first verify they are from the same site,
product, units, and sweep policy. Use one shared diverging color scale, show
each scan's actual UTC time, and leave missing gates masked rather than filling
them with zero velocity.
When plotting an MRMS composite, retrieve the exact product and timestamp withnexrad-mosaic-access, validate its native grid and valid-time semantics, and
show its provider, domain, units, legend, and missing-data mask. Do not apply
single-site sweep geometry or present the composite as a custom mosaic.
For static output, verify the actual rendered file—not only the plotting call.
Open or inspect the image and confirm:
For interactive output, also test zoom, time selection, product switching, and
the behavior when a sweep or scan is unavailable.
Record the plotting-library versions, projection, transformations, display
limits, masks, output path, and input identity. Pair the figure withweather-data-reproducibility when it must be regenerated later.
Return or publish:
applicable, and UTC/valid time shown;
transformations;
Do not return a plot without enough metadata for another analyst to understand
what is being displayed.
station details in images or logs.
controlled output paths.
use.
radar origin were used. Reproject the polar data explicitly.
interpreted as a full wind vector. Label the quantity as radial velocity.
normalized. Use one fixed scale across verified frames.
minimum color. Mask them and show a distinct background.
ignored. State the beam geometry and sampling height.
interpolated without gaps. Preserve resolution limits and missing sectors.
direct surface truth.
problems, or a wrong product selection.
interpretation and verification.