Veteran population and service-connected disability (ACS)
U.S. Census Bureau
In a RepVector build, this dataset sizes the addressable population behind a territory.
What this dataset is
Veteran counts by county, including veterans 65 and over, median veteran income and the number carrying a service-connected disability rating. The denominator that turns a list of VA sites into a rate: how many veterans each site has to cover, and how many of them are old enough or disabled enough to need care often. It is published by U.S. Census Bureau and can be queried at county and state level, refreshed annual (5-year rolling estimates). Each row is an aggregate statistic for a geography, so results describe a market as a whole rather than a single account.
Why it is useful
- Turns a place name into a denominator, so counts from other datasets become rates you can compare across markets.
- Separates markets that look busy because they are large from markets that are genuinely underserved.
- Supports age, income and household splits that shape which offering fits a territory.
Questions it helps answer
- How many people actually live inside this territory?
- Is demand here driven by population size or by unusually high per-capita need?
- Which nearby counties are large enough to justify a second visit each month?
How different verticals use it
RepVector is vertical-agnostic: this dataset is selected by what your question asks for, not by industry. These are common ways teams put it to work.
Converts patient volumes into per-capita rates so a small county with high need outranks a large one with low need.
Sizes catchment areas and household mix before committing to a site or a route.
Segments a territory by income and household composition to match product to market.
Projects the school-age and working-age base a programme would serve.
How RepVector uses it
- You describe a market in plain language. The geography resolver turns the place you named into the exact identifiers this dataset needs — city to county to state, plus DMA where relevant — so a query at county runs without you knowing any codes.
- The planner selects Veteran population and service-connected disability (ACS) only when your question matches what it actually reports. It is never included to pad a result.
- Returned rows are normalised into the shared metric layer, so figures from U.S. Census Bureau line up with every other source in the same dashboard instead of sitting in an isolated table.
- Quality checks score coverage and recency. If U.S. Census Bureau suppresses or omits a value for your geography, the gap is reported as a gap — nothing is estimated or filled in.
- The result renders as charts, KPIs and, where the rows are entities, prioritised targets you can export to PDF, Excel, CSV or JSON.
What it does not tell you
- Describes people, not buyers — pair it with provider or facility data before building a call list.
How it fits with the rest of the catalog
Population figures become decision-grade once divided into provider counts and facility capacity for the same geography. RepVector queries every selected dataset against the same resolved geography and time window, then normalises the results into one metric layer so they can be charted side by side. These datasets are the most common companions to Veteran population and service-connected disability (ACS):
Other population datasets
Build the list for one county and see whether the names are right.
Ask in plain language. RepVector finds the universe, enriches each target from its own website, scores it 0–100, and hands you a ranked call list with phones, addresses and named contacts.
3 free runs — no card required.