“Native” is not a complete answer until the geographic reference is named. A plant may be native somewhere in the United States, documented in one county, associated with an ecoregion, and still be a poor choice for a particular patio or yard. Those are separate questions.
A useful verification process produces three distinct verdicts: native-range status, documented local occurrence, and site suitability. A fourth field—seed source or provenance—can be added when locally adapted plant material matters. The goal is not to force every source into a simple yes or no, but to create a conclusion that another person could reproduce.
Define the question before opening a database
Decide which standard you are checking: native to the state, county, EPA Level III or IV ecoregion, or another named ecological region. These scales do not always agree. A county may contain more than one ecoregion, and an ecoregion may cross several counties.
Set up a simple worksheet before searching. Keep these columns separate:
- Plant name searched, accepted scientific name, and synonyms
- Native-range result and the geographic scale used by the source
- Documented occurrence in the county, including the record type and date
- EPA ecoregion and relevant site conditions
- Hardiness information, nursery availability, and optional seed source or provenance
The five-step verification workflow
1. Normalize the plant’s scientific name
Begin with the full scientific name rather than a common name. Include the subspecies or variety when that rank is relevant to the plant you are considering. Common names can refer to more than one taxon, while databases may use a different accepted name from a nursery label or older field guide.
Search the USDA PLANTS database for standardized names, plant symbols, distributional information, and references. A PlantAtlas site may also expose synonyms and nomenclatural citations. Record the name you entered and every accepted name or synonym returned. Confirm that the source is describing the same species, subspecies, or variety you intend to buy.
2. Use USDA PLANTS as a broad cross-check
USDA PLANTS is a useful first screen for distribution and nativity, but read the geographic scale carefully. Its occurrence information is generally mapped at county or county-equivalent scale, while native-status jurisdictions can be broad—for example, the entire Lower 48. A taxon marked native within that broad jurisdiction is not automatically native to your state or county.
Also check whether the database distinguishes native and introduced occurrence information within a larger jurisdiction. Write down the exact jurisdiction and status shown, rather than summarizing the result as simply “native.” This wording prevents a common mistake: treating a broad-range status as a local determination.
3. Compare the county map with BONAP
Use BONAP’s North American Plant Atlas as an independent county-scale comparison. BONAP publishes U.S. county maps for vascular plants and describes them as integrated phytogeographic databases. The public atlas identifies its displayed atlas as last updated December 15, 2014.
Agreement between USDA PLANTS and BONAP strengthens the case that a county occurrence is documented in both broad distribution sources. Disagreement is a reason to investigate, not a reason to choose the map that supports a preferred answer. Because the public BONAP atlas has a stated 2014 update date, check a more current state flora or specimen source when a recent taxonomic change, newly found population, or current status matters.
4. Find a state flora, herbarium, or specimen atlas
For a local question, a state-level source can provide stronger context than a national map. Search for a state flora, university herbarium, plant atlas, or specimen database, and look for county, locality, collector, collection date, and specimen fields.
The Indiana Plant Atlas illustrates the value of specimen-backed records: its occurrence records are based on herbarium specimens and can be searched by taxon, county, locality, collector, and collection date. Other states use different systems, so do not assume that every atlas has the same coverage or record standards.
For each useful record, capture the accepted taxon, source name, county, native or introduced label if supplied, specimen or occurrence identifier, locality, collection date, and access date. An old specimen can establish historical occurrence without demonstrating that a current wild population remains.
5. Map the property to an ecoregion, then assess the site
EPA Level III and IV ecoregion maps provide an environmental framework for the continental United States. Level IV is more detailed than Level III. Use the map or associated GIS data to identify the ecoregion at the property, but do not use the ecoregion as a substitute for a species distribution record.
Ecoregion information helps you ask a better ecological question: does the plant’s documented range overlap a comparable environmental setting? It does not prove that every location in that ecoregion is native habitat. Soil, moisture, shade, drainage, heat, exposure, and other local conditions still matter. Political boundaries alone are not a complete description of plant distribution.
Only after checking nativity and occurrence should you assess whether the plant fits the site. For a small yard, patio, or balcony, record sun exposure, reflected heat, wind, container or ground conditions, drainage, and available moisture. For container-specific considerations, see How to Find Native Plants That Can Grow Well in Containers in Your Region.
How to read maps and records without overclaiming
A shaded county or county dot is evidence of a documented record. It is not proof that the plant is native throughout that county, abundant there, appropriate for every yard, or currently extant. County maps also may not reveal whether a record came from intact habitat, a disturbed site, or a cultivated setting.
If a result is disputed, use an occurrence aggregator or herbarium portal to inspect the underlying data. USGS describes BISON records as filterable by record basis, provider, location, and date, with queries possible by county or a drawn boundary. The same USGS material warns that BISON data are not comprehensive enough for a missing record to prove absence from a range.
Treat records with extra care when they have a vague locality, no collection date, uncertain identification, cultivated context, or coordinates that appear to be a county centroid. Occurrence alone also does not settle native status: databases can include introduced, cultivated, or historical records.
When sources disagree: document, rank, and report uncertainty
Conflicts can result from taxonomic revisions, different definitions of native status, different map units, incomplete sampling, introduced populations within a species’ broader range, or different update schedules. Handle the disagreement as part of the result.
- Search the accepted name and synonyms, and confirm the taxonomic rank.
- Compare the broad USDA PLANTS result with BONAP’s county map.
- Check the most relevant current state flora, herbarium, or specimen-backed atlas.
- Inspect record dates, localities, collection context, and native or introduced labels.
- Save the links, names searched, map dates, record identifiers, and access dates.
- Label the conclusion as confirmed, likely, unresolved, or not documented at the chosen geographic scale.
For a county-level gardening decision, current state or specimen-backed evidence usually deserves more weight than a broad national map, while the national sources remain useful corroboration. If the evidence remains mixed, write “not resolved” or “not documented at county scale” instead of converting uncertainty into a confident claim.
Do not confuse native range with a plant tag
USDA Plant Hardiness Zones describe where perennial plants are likely to thrive based on average annual extreme minimum winter temperatures. They do not map a species’ natural range. USDA also notes that microclimates and non-winter factors are not captured, and places sharing a hardiness zone can differ substantially in heat, humidity, and daily temperature conditions.
A plant can be cold-hardy where it is not native. A native plant can also fail in a particular container or yard because of shade, drainage, soil texture, moisture, heat, wind, or plant provenance. Nursery availability is similarly a supply fact, not evidence of local nativity.
Sources and further reading
- www.epa.gov — www.epa.gov
- www.epa.gov — www.epa.gov
- plants.usda.gov — plants.usda.gov
- bonap.net — bonap.net
- bonap.net — bonap.net
- www.idigbio.org — www.idigbio.org
- pubs.usgs.gov — pubs.usgs.gov
- plants.sc.egov.usda.gov — plants.sc.egov.usda.gov
- pubs.usgs.gov — pubs.usgs.gov
- nrcsgeoservices.sc.egov.usda.gov — nrcsgeoservices.sc.egov.usda.gov
- content.ces.ncsu.edu — content.ces.ncsu.edu
- planthardiness.ars.usda.gov — planthardiness.ars.usda.gov
- planthardiness.ars.usda.gov — planthardiness.ars.usda.gov
- indiana.plantatlas.usf.edu — indiana.plantatlas.usf.edu
- plantatlas.usf.edu — plantatlas.usf.edu
- extension.arizona.edu — extension.arizona.edu
