Teams that want to understand what a TrueViewly report can support—and what it cannot decide.
By TrueViewly. Last reviewed:
How the first-pass screen works
A report starts with an address and organizes available location context into modules. Signals are designed to guide the next question, not to deliver a guarantee or a property-specific professional conclusion.
- Location and address inputs are evaluated against available mapped datasets and contextual indicators.
- Module-level findings are presented with explanations and coverage context where available.
- Users should consider results together and investigate material items through the appropriate primary sources.
Types of source context
Report coverage varies by module and location. TrueViewly can draw from sources and data products including FEMA flood-zone and National Risk Index context, NOAA Atlas 14 precipitation context, NHDPlus hydrography, USDA modeled wildfire data, CAL FIRE hazard zones, USGS modeled seismic ground motion and mapped faults, MTBS historical burn perimeters, USGS landslide datasets, and EPA regulated-facility and cleanup screening context.
- Flood and hydrology: mapped flood, surface-water, elevation, terrain, drainage, soil, and precipitation context.
- Wildfire: modeled annual burn probability and risk to potential structures, with separate housing/vegetation setting (WUI) and conditional flame-length evidence for mitigation follow-up.
- Earthquake: modeled ground motion, supported by community risk and mapped Quaternary-fault context where available.
- Landslide: mapped inventory and modeled susceptibility, with separate dated post-fire basin assessments where a match is available.
- Environmental: available cleanup, regulated-facility, RCRA and TRI scoring indicators; separate radon, nearby UST/release and conditional public-water monitoring evidence where matched.
Additional evidence is separate from the risk score
The additional evidence panels organize regional NOAA storm history, exact-point hail/tornado footprints, mapped levee context, regional NFIP claims and policy records, NFIP participation and CRS, nearby dams, regional karst geology, modeled local Vs30 and historical county radon potential. This evidence adds follow-up questions without changing the existing module scores, weights or overall risk score.
- Available describes source evidence, not a safe property. No match, outside coverage, unavailable and ambiguous are distinct outcomes.
- NFIP matching uses a locally imported 2024 community-boundary snapshot and the October 4, 2026 Community Status Book. Exact boundary points, conflicting communities and unidentified overlaps require local confirmation.
- Source dates differ from report-generation dates. A newly generated report does not make an older source current.
- SILVIS WUI describes census-block housing and vegetation, not parcel conditions. Conditional flame-length estimates describe intensity given fire, not annual fire likelihood or building damage. Missing coverage is not a modeled zero.
- Regional liquefaction and seismic site-class maps describe susceptibility or investigation requirements, not building-level probabilities. Tsunami planning areas are separate from hurricane surge and require local evacuation guidance.
- USGS 3DHP workunit and elevation-source footprints describe incremental mapping coverage, not rivers or flood exposure. No collected footprint does not mean hydrography is absent. NOAA Atlas 15 and UST Finder 2.0 monitoring do not replace the report sources before reviewed data are available.
- NOAA SLOSH high-tide hurricane scenarios add coastal inundation planning context where mapped, not annual probabilities, surveyed property depths or FEMA Base Flood Elevations.
- USGS post-fire basin estimates are conditioned on stated rainfall and dated assessment conditions. Perimeter-only matches do not supply basin numbers; no match does not exclude unassessed or downstream exposure.
- Leveed-area intersection is separate from nearby infrastructure and does not guarantee protection. Inspection and accreditation are dated inventory context.
- Regional NFIP summaries use explicit county/state geography, small-sample suppression and partial-year labels. They are not property claims history, active policies, total damages or a claims-rate denominator.
- Regional storm records are not independent storms or property losses. Exact-point footprints use no nearby buffer; a match is not building damage and a no-match is not zero hazard. Imported source periods and partial years remain explicit.
- Nearby UST/release records are not property contamination findings. Geocoding quality, missing fields and dated cleanup statuses require agency-file review.
- Service-area polygons identify candidate water systems, not verified suppliers. UCMR 5 is conditional historical monitoring, not tap tests, current safety or compliance; non-detects are not zero concentrations.
- The new evidence supports property and insurance conversations, not eligibility, premiums, loss estimates or an automated underwriting decision.
What the report is not
A screening output has important limits. Dataset coverage, data vintage, map precision, address matching, and the specific site conditions can affect what the report shows.
- Not a flood determination, survey, appraisal, inspection, certification, or government approval.
- Not legal, engineering, environmental, insurance, lending, or investment advice.
- Not a replacement for official records, site-specific assessment, disclosures, or qualified professional review.
How to use a report responsibly
Use the report to identify and document early follow-up questions. Confirm the items that matter to your transaction, client, property, or planned use through the right official source or specialist.
- Review the relevant report module, source context, and any coverage caveats.
- Escalate material questions to official agencies, local authorities, insurers, surveyors, inspectors, engineers, environmental consultants, or legal advisers as appropriate.
- Keep the screening report alongside the follow-up record, not in place of it.
Data sources, coverage, and appropriate use
TrueViewly uses available public and official-source data products as screening context. Each source has a specific role and limitations; coverage, currency, and detail can vary by location.
| Source family | What it contributes | Important limit |
|---|---|---|
| NOAA Storm Events Database | Additional county/state summaries for selected event types; default six-year window through the imported March 2026 snapshot. | Regional records, not independent storms or property claims. County summaries exclude forecast-zone-only records; nominal damage amounts and partial years require care. |
| NOAA Event Footprint Catalog | Additional exact-point matches to retained historical hail and tornado polygons, with source dates and record references. | No nearby buffer. Coverage and missing dates vary; no match is not zero hazard, and a match is not building damage. These polygons do not change scores. Interpretation guide. |
| FEMA flood maps | Mapped flood-zone, SFHA, and BFE context where available. | Coverage and map detail vary; confirm material questions through applicable official and local sources. |
| FEMA National Risk Index | Community-scale hazard, exposure, vulnerability, and resilience context. | Community or census-geography context is not a parcel-level assessment. |
| NOAA Atlas 14 | Precipitation-frequency and design-storm context. | Rainfall context does not establish site flooding or replace local drainage design. |
| USGS / NHDPlus HR | Mapped surface-water, hydrography, terrain, and elevation context. | Mapped features and elevation data are not a boundary survey or hydraulic model. |
| USGS landslide data | Mapped landslide inventory and susceptibility context where available. | Not a geotechnical site investigation or a real-time hazard forecast. |
| NOAA SLOSH storm-surge planning maps | High-tide hurricane-category inundation ranges for mapped coastal regions. | Not annual probability, a surveyed building depth or FEMA BFE. Missing coverage is not zero surge; leveed-area designations do not guarantee protection. Storm-surge guide. |
| USGS post-fire debris-flow assessments | Dated basin likelihood, sediment volume and published hazard for stated rainfall scenarios. | Selected assessed fires, not all burned areas. Perimeter-only matches do not supply basin numbers; imported basin estimates do not map downstream runout or building damage. Post-fire guide. |
| USDA Wildfire Risk to Communities | Modeled annual burn probability and risk to potential structures; separate conditional flame length and 4/8 ft exceedance evidence. | Intensity is conditional on fire, not annual likelihood or building damage. The 30 m intensity layers reflect 2022 landscape conditions across CONUS, Alaska and Hawaii, not territories. Not a current forecast or parcel inspection. Wildfire evidence guide. |
| SILVIS 2020 Wildland-Urban Interface | Surrounding census-block housing and vegetation setting, including Intermix and Interface classifications. | Prepared source scope includes states, DC and inhabited territories; report availability varies. Classification year 2020; vegetation years vary by region. Not parcel fuels, fire probability or insurance eligibility. Non-WUI does not establish safety. |
| MTBS burn history | Historical burn-perimeter proximity and density context. | Historical burns do not predict active fire behavior or current fuels. |
| CAL FIRE FHSZ | California fire-hazard severity-zone context where mapped. | Hazard-zone context is not an insurance-rate or parcel-condition determination. |
| USGS National Seismic Hazard Model | Modeled peak ground acceleration and spectral acceleration at selected return periods. | Reference-site ground motion is not parcel soil response, liquefaction analysis, or a structural-performance prediction. |
| USGS Quaternary faults | Mapped fault proximity, density, age, classification, and certainty context. | Fault proximity alone does not describe expected shaking or site response. |
| EPA environmental data | Available facility, compliance, release, and cleanup-site screening context. | Not a Phase I ESA, contamination-boundary map, or liability determination. |
| EPA UST Finder | Additional nearby geolocated tank-facility and release records, cleanup status, tank summaries and source coordinate quality. | Dated inventory records, not contamination pathways or property findings. Missing geometry and no-further-action status require care. UST guide. |
| EPA service areas / ECHO inventory | Version 3 service-area candidates grouped by PWSID, source/model verification, activity and separate seller relationships. | Even source-verified polygons do not confirm property service. No match is not proof of private-well use; ZIP/proximity and upstream sellers are not supplier fallbacks. |
| EPA UCMR 5 | Conditional candidate-system monitoring with constituent groups, collection dates, reporting levels and detected/non-detect counts. | Not tap testing, current water safety or compliance. Non-detect is not zero; lithium is not PFAS. No score changes. Water-monitoring guide. |
| NRCS soils | Mapped soil runoff, drainage, ponding, and infiltration context. | Map-unit attributes are generalized and do not replace site-specific testing. |
| FEMA Community Status Book / CRS | October 4, 2026 snapshot of matched community participation, CRS class and potential discount context. | Not insurance eligibility, a policy quote or guaranteed savings; confirm current community status and policy applicability. |
| FEMA NFIP community boundaries | Locally imported cl2024_v1 No Overlaps Whole polygons for coordinate-to-CID matching. | Boundary and status snapshots differ. Missing IDs, conflicting matches and exact edges require confirmation; territory geometry does not guarantee a usable CID. |
| USACE National Inventory of Dams | Nearest spatially usable inventory structures, distance and available consequence, condition and record-date attributes. | Hazard potential is not failure probability. Distance does not establish downstream exposure, and inventory/map availability is incomplete. |
| USGS karst compilation | 2014 regional karst, pseudokarst and thermokarst context in retained layers for states, PR and USVI. | Not an observed sinkhole, collapse probability or foundation assessment; GU, CNMI and AS are outside this compilation. |
| USGS Global Vs30 Mosaic | 2026 release of modeled median shear-wave velocity and logarithmic uncertainty on a global 30-arcsecond grid. | Regional modeling, not a measured site class. Masked cells are excluded; displayed NSHM ground motion and earthquake scores are not soil-adjusted. |
| EPA Radon Zones | 1993 county model joined through a validated Census 2024 FIPS crosswalk; unresolved historical geographies remain unmatched. | No territory coverage in this table. County potential is not indoor concentration; test the building regardless of zone. |
| USACE National Levee Database | Official retained leveed-area intersections, nearby embankments/floodwalls and dated system metadata. | Not guaranteed protection or a failure probability. Proximity is distinct from mapped intersection; preparation dates are not inspection dates. Interpretation guide. |
| OpenFEMA NFIP Claims v3 | Compact annual regional claim records and recorded payment components; September 8, 2026 snapshot with small-sample suppression. | Not property claims or total flood losses. Missing values are not zero; snapshot years are partial and uninsured/private losses are excluded. |
| OpenFEMA NFIP Policies v3 | Annual regional policy records and represented units with term-quality notes and explicit county/state geography. | Not unique properties, active policies, premiums or a claims-rate denominator. Interpretation guide. |
| Authoritative state geohazard maps | Regional liquefaction susceptibility or investigation zones, seismic site-class context and tsunami planning areas where reviewed coverage is available. | Regional purposes and dates differ. Not parcel testing, damage probability or current warnings; tsunami and hurricane surge are separate. Regional map guide. |
| USGS 3D Hydrography Program | Collected incremental workunit, elevation-source and limitation footprints describe mapping coverage. | Not river geometry, flood exposure or a completed nationwide replacement for existing hydrography. No footprint match does not mean no hydrography. |
Regional liquefaction, tsunami and mapping-coverage context, regional NOAA history, storm footprints, levees, NFIP history and community records, nearby dams, karst, local Vs30, radon, UST/releases and conditional public-water monitoring are additional evidence panels. They do not change current risk scores or weights and do not determine insurance eligibility, premiums or coverage.
Trust, but verify: the sources above are established public-source datasets. TrueViewly organizes their available context into a first-pass report, but the report is not itself an official determination. Read the module-level source and confidence information, then verify material findings through the appropriate primary record or qualified professional.
Free public tool
Check a FEMA flood zone by coordinates
Open the flood-zone lookup
Use a U.S. latitude and longitude to inspect the available mapped zone, SFHA status, base flood elevation, and supporting FEMA context.
Sources and further reading
- FEMA Community Status Book
- FEMA NFIP community-boundary dataset
- FEMA Community Rating System
- USACE National Inventory of Dams
- USGS karst compilation, OFR 2014-1156
- USGS Global Vs30 Mosaic
- EPA Map of Radon Zones
Source publications and live agency pages may differ from the snapshot used in a report. Check the report's source dates and confirm material findings through the responsible authority.
Frequently asked questions
Are all modules available for every address?
No. Availability and coverage can vary by location and data source. Reports should be read with their module context and any availability notes.
Does TrueViewly use real-time hazard forecasts?
No. The product is designed for available mapped and contextual screening data, not for real-time emergency forecasting.
Can a score be used as a final decision?
No. Any score or signal is informational context. Material decisions require the appropriate property-specific and professional review.
TrueViewly reports are informational decision-support outputs based on available datasets and user-provided inputs. They are not certifications, legal advice, engineering opinions, insurance determinations, government approvals, or a replacement for official records and professional due diligence.