WAYNESBORO, GEORGIA · OPERATIONS

Infrastructure, safety, housing, and resilience.

Operations source confidence, public works references, weather, water, housing, environmental, mobility, and hazard context.

ExecutiveEconomicDowntown + ProjectsOperationsBriefingSources
Telemetry guardrailReference layerNo live dispatch, utility, or emergency claims.
Mobility16.0%Zero-vehicle context with MOE caveats.
Accessibility8.9%Disability context added for planning only.
OPERATIONS DATA CONFIDENCE

Reference layer first; no live telemetry claims

Health cardsSynthetic scoresInfrastructure, housing, and response metrics are source pending until official exports exist.
Weather readinessCached no-alert snapshotGAC033 / GAZ077 public NWS routing cached for briefings.
Water identityGA0330004 seedEPA ECHO/SDWIS identity only; no water-quality or live-utility claim promoted.
Energy resilience71.9% electric heatACS B25040 is heating-fuel planning context only; no utility account, outage, or rate-affordability claim promoted.
Safety sources8 routes indexedCrime, E-911, fire, and crash data paths are separated from unpublished public-safety counts.
Language access7.3% contextCensus Reporter C16001 supports public-communication planning only; no translation workload or service-demand claim promoted.
Hydrology3 USGS sites6 provisional IV series cached; still not flood telemetry or drainage performance.
SVI resilience7 tract rowsCDC/ATSDR SVI is county tract context until Waynesboro boundary overlap is mapped.
Environmental permits11 RCRA rowsEPA ECHO handler identity is source context only; no city inspection, zoning, or violation claim promoted.
OFFICIAL OPERATIONS ROUTES

Public service pages now sit above source pending system-health lanes

CITY ROUTE INDEX

What this fixes in the operations lane

Before the platform shows infrastructure, safety, streets, drainage, sanitation, or utility health as public metrics, this panel gives the page a visible official-route spine and makes clear what records are still missing.

These routes are public service references only. They do not prove work-order counts, complaint volume, staffing levels, asset condition, outage status, response time, or operating performance until official aggregate records are obtained and cited.

Public works hubPublic WorksAnchor public works source routing before streets, solid waste, storm-drainage, and beautification widgets make operational claims.Solid wasteSolid WasteReference service scope and customer-facing rules before any collection performance or route-efficiency metric is displayed.StreetsStreetsReference route for road-maintenance responsibilities before linking GDOT, work orders, or capital-project records.Storm drainageStorm Drainage InformationSource route for drainage-issue context; keep separate from flood telemetry, hydrology observations, or parcel-risk claims.Natural gasNatural GasComplements ACS heating-fuel context and utility-rate references before any account, service-territory, or outage metric is promoted.Fire departmentFireSource-routing baseline before fire incident, staffing, ISO, or response-time cards can be promoted.
Manually review each service page for adopted schedules, fees, contacts, forms, and document links before quoting operational rules.Request or obtain aggregate service records only: monthly work orders, missed pickups, street maintenance requests, drainage complaints, and response-time summaries if public.Pair public works route metadata with budgets, capital projects, weather/hydrology context, and GDOT road data before the public dashboard supports operations priorities.

Access method: Low-volume public page review; HTTP 200 confirmed for each listed official route. No forms submitted and no private systems accessed.

PARKS / CIVIC FACILITIES SOURCE

Service-location routes before access, condition, or program claims

OFFICIAL ROUTE INDEX

Why this belongs in Operations

This is a service-location and civic-asset source route only. It is not a parks condition assessment, reservation log, program attendance count, maintenance backlog, capital-improvement plan, accessibility audit, or live facility telemetry.

It gives the public-facing app a real civic-asset spine for parks, meeting space, youth amenities, and future service-location mapping without pretending to know utilization or condition.

Park / civic gathering spaceCity ParkGazebo · Picnic Tables · PlaygroundNeighborhood parkDavis Park (Sixth Street Park)Basketball Court · Benches · PlaygroundEvent / meeting facilityCity of Waynesboro Ice PlantChairs · Restrooms · Tables
Manually verify addresses/coordinates before placing facilities on the schematic map.Check reservation/rate documents before displaying costs, availability, or permitted uses.Pair with parks budgets, maintenance work orders, ADA/facility inventories, and recreation-program calendars before Council recommendations.

Official facility pages can anchor a public civic-asset inventory, but they do not prove condition, capacity, utilization, safety, accessibility, or capital need. Access method: Public CivicEngage Facilities pages; low-volume HTTP 200 checks for the directory and five facility-detail routes; no forms submitted.

INFRASTRUCTURE

Public source path only

SOURCE PENDING

No infrastructure health scores are displayed publicly until tied to adopted capital plans, asset inventories, work orders, compliance records, or official reports.

PUBLIC SAFETY

Aggregate records required

SOURCE PENDING

No incident counts, response times, crime trends, or corridor safety claims are displayed until official aggregate data is released or obtained through a lawful records process.

HOUSING & DEVELOPMENT

Permit and parcel evidence first

SOURCE PENDING

No development heat scores are displayed publicly until housing, permit, zoning, parcel, and project records are source-labeled and reconciled.

TRANSPORTATION PROJECT SOURCE

GDOT GeoPI queued before road-project claims

FILTER PENDING
GeoPI DashboardProject search / project information web appManual source route for GDOT transportation projects before any project tracker row is promoted.Project Search MapPublic ArcGIS project map surfaceCandidate map/filter path for Burke County corridor context after export/share rules are verified.
Observed public shapeGeoPI Project InformationHTTP 200 public GDOT application surface reached · map surface also reached.
Open GeoPI manually and test Burke County / Waynesboro filters; record only shareable project links or exported public rows.Separate GDOT state-route projects from City of Waynesboro capital projects, utility work, and local resurfacing lists.If stable rows exist, cache a small project identity snapshot with retrieval date, source URL, phase/status definitions, and no unsupported cost/schedule claims.

Source-routing seed only. This is not a confirmed Waynesboro project list, capital plan, road-condition score, construction schedule, or funding claim until specific GDOT rows are filtered, timestamped, and manually verified. Retrieved 5/31/2026 from public GDOT surfaces.

PUBLIC SAFETY SOURCE ROUTING

Crime and response cards stay source-gated until agency-level aggregates are verified

NO LIVE DISPATCH
Reference readyGBI Crime StatisticsValidate whether Waynesboro/Burke County agency-level crime counts are published through GBI before replacing demo public-safety trends.Endpoint needs confirmationFBI Crime Data ExplorerPotential agency-level crime baseline once the correct ORI/reporting agency is identified and response reliability is confirmed.Reference onlyCity Police / Fire pagesAnchor department context while incident counts, response times, and call categories remain request/export dependent.Records path identifiedBurke County E-911 pageFuture source path for aggregate call volume and response-time questions, not live dispatch telemetry.Emergency route indexedGEMA/HS Burke County profileAdds a state emergency-management anchor for preparedness, hazard, and coordination drilldowns without implying live incident status or response capability.Agency route indexedBurke County Sheriff public siteCross-check agency identity and published public-safety context before trying to map GBI/FBI ORI rows or county-level safety indicators.Seed connector readyGDOT Crash Data & ReportingPotential roadway/crash-safety context for corridors and downtown access after geography filters, dashboard export rules, and publication caveats are verified.Reference route indexed511 GeorgiaKeep live road-condition awareness separate from historic crash counts, police incidents, response times, and local street-condition claims.
Which agency/ORI should represent City of Waynesboro police reporting in FBI CDE or GBI tables?Does the city, sheriff, county EMA, or E-911 office publish monthly aggregate incident, fire, EMS, emergency-management, or call-volume reports?Can GDOT crash dashboard filters/export rules support Burke County or Waynesboro corridor safety summaries without scraping the web app?What fields can be safely requested as aggregate public records without exposing private incident details?

Public-safety operating metrics remain synthetic until official aggregate incident, response-time, or crime-reporting data is released or obtained through a lawful records process.

HEALTH + RESILIENCE SOURCE

CDC PLACES tract estimates scoped for Burke County

PUBLIC MODEL DATA
Observed public shape280 tract-measure rowsCDC PLACES: Local Data for Better Health, Census Tract Data, 2025 release
Geography guardrailBurke County census tractsNot yet a Waynesboro citywide metric; needs tract boundary review.
Best useGrant and resilience contextPair with ACS, hazards, and local service records before public recommendations.
2023 · tract 13033950101Any disability among adults38.7% · CI 33.9–43.5Pulled from public CDC PLACES Socrata API with county filter; display as data-shape/context only until tract geography and methodology are visible.
2023 · tract 13033950101Arthritis among adults32.3% · CI 28.8–35.9Pulled from public CDC PLACES Socrata API with county filter; display as data-shape/context only until tract geography and methodology are visible.
2023 · tract 13033950101Binge drinking among adults12.8% · CI 10.3–15.6Pulled from public CDC PLACES Socrata API with county filter; display as data-shape/context only until tract geography and methodology are visible.
2023 · tract 13033950101Cancer (non-skin) or melanoma among adults8.0% · CI 7.2–8.8Pulled from public CDC PLACES Socrata API with county filter; display as data-shape/context only until tract geography and methodology are visible.

CDC PLACES values are model-based public-health estimates. Do not present them as municipal operations telemetry, clinical records, or citywide Waynesboro claims until geography, tract coverage, year, confidence intervals, and methodology are visible.

HEALTH ACCESS · ACS CONTEXT

Insurance-coverage seed before health-service claims

NO-KEY API SEED
Waynesboro uninsured estimate19.8%1,102 residents · ±274 · ACS 2024 5-year

Planning context, not clinical or eligibility data

ACS survey planning context only: not Medicaid enrollment files, clinical records, eligibility determinations, provider capacity, charity-care demand, EMS workload, or municipal health-service telemetry.

Open Census Reporter B27010 query
With health insurance coverage80.2%4,467 people · Derived MOE pending
Uninsured age 19–34643643 people · ±212
Uninsured age 35–64459459 people · ±171
Waynesboro city19.8%1,102 uninsured · ±274 · universe 5,569
Burke County13.8%3,350 uninsured · ±515 · universe 24,260
Georgia12.4%1,329,511 uninsured · ±13,974 · universe 10,746,448

Treat ACS B27010 as health-access and grant-planning context only. Do not present it as official enrollment, household-level hardship, provider capacity, clinical status, emergency-response demand, or municipal operational performance. Next: Pair with CDC PLACES, hospital/clinic access, insurance enrollment assistance, EMS/public-health aggregates, and nonprofit service-location sources before Council health-access recommendations.

SERVICE ACCESS · OFFICIAL CITY ROUTE

Mental health resource navigation

RESOURCE ROUTE
Official local resource route indexedCity page indexedWaynesboro, Georgia residents; local, state, and national resource links listed by the city.Open official city resource page

What this adds to the operations lane

The platform now has a public, city-hosted service-navigation route beside ACS health-insurance and language-access context. This keeps the briefing layer from treating health-access questions as only survey metrics.

Source route only. This panel is not a clinical recommendation, provider endorsement, utilization count, emergency dispatch tool, eligibility finding, or measure of local mental-health burden.

Local resource pageHTTP 200City-hosted page with community-resource framing and local/national links.
Local provider examplesAddress/phone textPage text lists local/regional counseling and treatment resources; manual QA required before structured provider display.
Crisis routes988 / GCALLinks include 988 Georgia, Georgia Crisis and Access Line, and national crisis/help resources.
City resource pageMental Health Resources | Waynesboro, GAOfficial local source hub for public-facing service-navigation links.State crisis accessGeorgia Crisis and Access Line (GCAL)Reference route only; do not ingest private help-seeking or call records.988 Georgia988 Suicide & Crisis Lifeline in GeorgiaCrisis-resource link; display as public information, not municipal incident telemetry.State agency hubGeorgia DBHDDState behavioral-health source route for future aggregate program/context research.
Manually QA the city page and linked providers before exposing any structured provider names, addresses, or phone numbers.Pair with ACS health insurance, CDC PLACES, local clinic/hospital/service-location data, and public-health partners before the public dashboard supports health-access recommendations.Keep crisis links as public reference routes only; never scrape, infer, or display private help-seeking, call, patient, or eligibility data.

Retrieved by low-volume public page review on 6/1/2026. Keep this as source routing and public service-navigation context until provider details are manually verified.

ACCESSIBILITY / SERVICE CONTEXT · ACS

Disability-by-age seed before ADA or service-demand claims

NO-KEY API SEED
Waynesboro disability estimate8.9%495 people · MOE derived after covariance review · ACS 2024 5-year

Planning context, not a finding

ACS survey context only: not clinical records, benefits eligibility, ADA compliance findings, department workload, EMS demand, school special-education data, or live service telemetry.

Open Census Reporter B18101 query
Under 18 with disability285.7% of disabled estimate · Derived MOE pending
Age 18-64 with disability32164.8% of disabled estimate · Derived MOE pending
Age 65+ with disability14629.5% of disabled estimate · Derived MOE pending
Waynesboro city8.9%495 of 5,569 residents in ACS universe
Burke County16.3%3,961 of 24,260 residents in ACS universe
Georgia13.1%1,409,891 of 10,746,448 residents in ACS universe

Treat ACS B18101 as accessibility and grant-planning context only. Do not present it as ADA compliance, local service burden, health diagnosis, benefit participation, or individual-level disability evidence. Next: Calculate proper MOE for derived disability rollups before any public narrative claim.

LANGUAGE ACCESS · ACS CONTEXT

Public communications seed before translation-demand claims

NO-KEY API SEED
Language other than English at home7.3%379 residents age 5+ · Derived MOE pending · ACS 2024 5-year

Communication planning context, not a municipal workload claim

ACS survey planning context only: not school enrollment, translation-demand proof, immigration status, household-level language records, emergency communications performance, or live municipal service telemetry.

Open Census Reporter C16001 query
Speak only English at home92.7%4,848 people · ±300
Spanish spoken at home6.1%319 people · ±202
Speak English less than very well4.6%240 people · Derived MOE pending
Waynesboro city7.3%379 non-English at home · 4.6% less than very well
Burke County3.1%702 non-English at home · 1.2% less than very well
Georgia15.5%1,592,544 non-English at home · 5.8% less than very well

Treat ACS C16001 as public-communication and service-planning context only. Do not present it as individual language need, school enrollment, immigration status, emergency alert performance, or proof of official translation demand. Waynesboro limited-English ACS seed: 4.6% (240 residents age 5+), with derived MOE still pending.

FOOD ACCESS / GRANT READINESS

USDA ERS tract dataset route indexed before grocery-access claims

EXTRACT PENDING
XLSX · 81.83 MB2019 Food Access Research Atlas data downloadPrimary tabular route for tract-level low-income / low-access indicators after low-volume manual download and schema review.ZIP · 8.65 MB2019 Food Access Research Atlas data downloadSmaller packaged route to inspect data files before building a normalized Burke County extractor.USDA ERS page · ReferenceState-level estimates of low income and low access populationsContext route for statewide comparison language; not a substitute for tract-level local extraction.
Download the smaller 2019 ZIP manually/low-volume and inspect schema before automating any parser.Filter only Georgia / Burke County tract rows, then crosswalk tracts that intersect Waynesboro before city-facing cards appear.Show USDA vintage, tract geography, and methodology notes beside any future food-access or grant-readiness metric.

This is a food-access source route only. Do not display Waynesboro food-desert, grocery-access, nutrition, poverty, or grant-eligibility claims until tract rows are extracted from the USDA file, vintage is recorded, and tract-to-city geography is reviewed. Retrieved 5/31/2026 from the USDA ERS download page.

Survey contextACS tenure, burden, monthly costs, tenure income, typology, crowding, valuesGood for planning questions; never a parcel, lease, payroll, eligibility, or program record.
Official routeCity LIHTC + Community Development + utility/rate pagesPDF/page review pending before claims about projects, rates, or eligibility.
Hard-data nextqPublic parcels, tax digest, permits, code aggregatesNeeds export permission, records request, or manual source review.
HOUSING SOURCE SNAPSHOT

ACS housing context before parcel-level vacancy claims

PUBLIC API SEED
Occupied housing units2,204MOE ±243 · B25003
Renter-occupied units1,556MOE ±240 · B25003
Vacant housing units469MOE ±236 · B25002
Median gross rent$746MOE ±73 · B25064
70.6% Renter share of occupied units17.5% Vacant share of total housing units

This seed is public ACS housing context from Census Reporter. It is not a parcel inventory, live vacancy survey, rent roll, tax record, code-enforcement list, or official city housing program finding. Release: ACS 2024 5-year (2020-2024); retrieved through Census Reporter, not the credentialed Census API.

HOUSING COST BURDEN · ACS CONTEXT

Affordability pressure context before program or eligibility claims

NO-KEY API SEED
Renter households ≥30%44.3%689 of 1,556 renter-occupied units · MOE ±253

Guardrail for public use

Cost-burden estimates can frame affordability questions, grant readiness, and housing-source priorities — but they cannot stand in for rent rolls, household eligibility, eviction records, or city program enrollment.

Census Reporter B25070 / B25091 source query
Renter households ≥30%44.3%689 households · MOE ±253 · B25070
Owner households ≥30%19.3%125 households · MOE ±97 · B25091
Rent not computed7.4%115 households · MOE ±120 · B25070
Waynesboro city44.3%renter cost burden · 19.3% owner burden
Burke County41.2%renter cost burden · 18.8% owner burden
Georgia48.4%renter cost burden · 20.7% owner burden

ACS housing-cost-burden estimates are survey context only. They are not rent-roll records, household eligibility findings, eviction filings, utility hardship records, parcel condition, official affordability program enrollment, or municipal telemetry. Release: ACS 2024 5-year (2020-2024); retrieved 5/31/2026.

MONTHLY HOUSING COSTS · ACS CONTEXT

Rent and owner-cost medians before local affordability claims

NO-KEY API SEED
Median gross rent$746MOE ±$73 · B25064 · Burke $758

Cost context, not a rent roll

Useful beside cost burden, tenure, home values, utility rates, LIHTC/DCA, and parcel/tax records to frame affordability questions before the public dashboard supports any recommendation. Mortgage-owner median: $1,379 with MOE ±$99.

Census Reporter B25064 / B25088 source query
Median gross rent$746MOE ±$73 · county $758 · state $1,393
Median owner costs$846MOE ±$482 · county $661 · state $1,293
Owner costs with mortgage$1,379MOE ±$99 · county $1,394 · state $1,783
Owner costs without mortgage$507MOE ±$133 · county $435 · state $541
Waynesboro city$746median rent · $846 owner total · $1,379 mortgage-owner
Burke County$758median rent · $661 owner total · $1,394 mortgage-owner
Georgia$1,393median rent · $1,293 owner total · $1,783 mortgage-owner

ACS B25064/B25088 monthly housing-cost estimates are survey planning context only. They are not rent rolls, lease records, mortgage-servicing records, property-tax bills, utility hardship records, household eligibility data, or municipal housing telemetry. Release: ACS 2024 5-year (2020-2024); retrieved 6/1/2026.

TENURE INCOME · ACS CONTEXT

Owner/renter income bridge before affordability recommendations

NO-KEY API SEED
Renter-occupied households$35.0KMOE ±$27,352 · B25119 · owner median $62.5K

Affordability bridge, not household files

ACS B25119 adds tenure-specific income context next to rent, cost-burden, home-value, and utility-rate panels. The owner/renter median-income gap is $27.5K, but the renter MOE is large, so public briefing copy should stay cautious and source-gated.

Census Reporter B25119 source query
All occupied households$41.6KMOE ±$9,969 · Affordability baseline before mixing income, rent, ownership, utility-rate, and tax records.
Owner-occupied households$62.5KMOE ±$17,639 · Owner affordability / rehab planning context; not mortgage-servicing or tax-record evidence.
Renter-occupied households$35.0KMOE ±$27,352 · Renter affordability context to pair with rent, cost-burden, LIHTC, utility-rate, and service-location sources.
Waynesboro city$35.0Krenter median · $62.5K owner median · $27.5K gap
Burke County$30.8Krenter median · $65.1K owner median · $34.4K gap
Georgia$49.8Krenter median · $96.4K owner median · $46.5K gap

ACS B25119 is survey planning context only. It is not payroll, tax-return data, rent-roll data, mortgage-servicing records, household eligibility data, local revenue, utility hardship records, or municipal telemetry. Release: ACS 2024 5-year (2020-2024); retrieved 6/1/2026.

HOUSING STOCK AGE · ACS CONTEXT

Older housing context before rehab, blight, or infrastructure claims

NO-KEY API SEED
Pre-1980 housing units76.2%2,036 of 2,673 ACS housing units · MOE on total ±334

Presentation-safe use

Use this as a planning signal for rehabilitation, weatherization, grant readiness, and parcel-export prioritization — not as a condition finding or inspection record.

Census Reporter B25034 source query
1970 to 197920.4%
546 units · MOE ±257
1960 to 196914.1%
376 units · MOE ±188
1950 to 19599.1%
244 units · MOE ±141
1940 to 194913.3%
356 units · MOE ±261
1939 or earlier19.2%
514 units · MOE ±162
Waynesboro, GA76.2%pre-1980 share · 11.0% post-2000 · 2,673 units
Burke County, GA47.6%pre-1980 share · 24.6% post-2000 · 11,300 units
Georgia31.5%pre-1980 share · 35.1% post-2000 · 4,541,835 units

ACS B25034 is survey housing-stock context only. It is not a parcel condition survey, code-enforcement record, lead-paint finding, rehabilitation-cost estimate, vacancy count, or downtown building inventory. Release: ACS 2024 5-year (2020-2024); retrieved 5/31/2026.

HOUSING TYPOLOGY · ACS CONTEXT

Structure mix before parcel, zoning, or infill claims

NO-KEY API SEED
2–4 unit structures28.2%754 of 2,673 ACS housing units · total MOE ±334

Planning use, not a parcel inventory

Useful for housing typology, infill strategy, infrastructure planning, and grant framing once paired with parcels, zoning, permits, LIHTC/DCA records, and local housing initiatives.

Census Reporter B25024 source query
Single-family units60.0%
1,605 units · derived from B25024
2–4 unit structures28.2%
754 units · derived from B25024
5+ unit structures9.1%
242 units · derived from B25024
Mobile homes2.7%
72 units · derived from B25024
Waynesboro, GA60.0%single-family · 28.2% 2–4 unit · 2.7% mobile home
Burke County, GA58.4%single-family · 7.5% 2–4 unit · 30.0% mobile home
Georgia70.8%single-family · 5.1% 2–4 unit · 7.8% mobile home

ACS B25024 is survey housing-stock structure context only. It is not a parcel inventory, zoning determination, building-code record, occupancy certificate, tax record, permit history, rent-roll dataset, or affordability-program evidence. Release: ACS 2024 5-year (2020-2024); retrieved 5/31/2026.

RENTER STRUCTURE MIX · ACS CONTEXT

Rental typology before parcel, zoning, or landlord claims

NO-KEY API SEED
Renter units · 2-4 structures46.6%725 of 1,556 renter-occupied ACS units · derived MOE approx. ±241

Useful housing question, not a rental registry

B25032 separates owner and renter units by structure type. It sharpens the housing lane by showing where renter context lives in single-family, small multifamily, and apartment-scale structures before any parcel or zoning claim is made.

Census Reporter B25032 source query
Renter-occupied share70.6%
1,556 units · MOE ±240
Renter units · 1 detached37.2%
579 units · MOE ±206
Renter units · 2-4 structures46.6%
725 units · derived MOE approx. ±241
Renter units · 5+ structures15.6%
242 units · derived MOE approx. ±122
Waynesboro city70.6%renter share · 46.6% small multifamily · 37.2% detached
Burke County30.0%renter share · 29.8% small multifamily · 39.8% detached
Georgia34.3%renter share · 13.2% small multifamily · 33.5% detached

ACS B25032 is household survey context only. Do not treat it as parcel inventory, rental registry, landlord ownership data, zoning determination, permit history, rent roll, code-enforcement evidence, or municipal telemetry. City renter share: 70.6%; release ACS 2024 5-year (2020-2024); retrieved 6/1/2026.

HOUSING CROWDING · ACS CONTEXT

Occupancy pressure lens before code, rental, or service claims

NO-KEY API SEED
Occupied units >1.00 occupants/room0.0%0 of 2,204 occupied ACS units · derived MOE ±49

Read the zero correctly

Useful as a housing-condition pressure lens when paired with cost burden, housing age, qPublic/parcel exports, code-enforcement aggregates, LIHTC/DCA records, and local service-provider evidence.

Census Reporter B25014 source query
Owner occupied29.4%648 occupied units · MOE ±216
Renter occupied70.6%1,556 occupied units · MOE ±240
Owner occupied81.0%
≤0.50 occupants / room · 525 units · MOE ±201
Owner occupied19.0%
0.51–1.00 occupants / room · 123 units · MOE ±103
Owner occupied0.0%
>1.00 occupants / room · 0 units · MOE approx. ±35
Renter occupied43.7%
≤0.50 occupants / room · 680 units · MOE ±241
Renter occupied56.3%
0.51–1.00 occupants / room · 876 units · MOE ±271
Renter occupied0.0%
>1.00 occupants / room · 0 units · MOE approx. ±35
Waynesboro, GA0.0%0 units >1.00 occupants/room · 70.6% renter share
Burke County, GA0.8%71 units >1.00 occupants/room · 30.0% renter share
Georgia2.4%97,290 units >1.00 occupants/room · 34.3% renter share

ACS B25014 is survey planning context only. A zero estimate with nonzero margin of error must not be interpreted as proof no household is crowded; it is not a code-enforcement, inspection, rent-roll, occupancy-certificate, homelessness, household-level, or municipal service record. Release: ACS 2024 5-year (2020-2024); retrieved 6/1/2026.

HOME VALUE DISTRIBUTION · ACS CONTEXT

Owner-occupied value lens before parcel/tax claims

NO-KEY API SEED
$200K–$299K band22.4%145 of 648 owner-occupied units · total MOE ±216

Tax-base signal, not tax records

Useful as a housing-market/value-distribution planning lens after pairing with qPublic parcels, tax digest, sales, permits, housing condition, and affordability-program records.

Census Reporter B25075 source query
Under $100K36.3%
235 units · derived from B25075
$100K–$199K23.0%
149 units · derived from B25075
$200K–$299K22.4%
145 units · derived from B25075
$300K+18.4%
119 units · derived from B25075
Waynesboro, GA40.7%$200K+ owner-occupied units · 36.3% under $100K · 23.0% $100K–$199K
Burke County, GA37.0%$200K+ owner-occupied units · 39.9% under $100K · 23.2% $100K–$199K
Georgia71.7%$200K+ owner-occupied units · 12.3% under $100K · 16.0% $100K–$199K

ACS B25075 is owner-occupied home-value survey context only. It is not an appraisal roll, parcel valuation export, tax assessment, sale record, rent-roll dataset, code-enforcement evidence, or affordability-program eligibility finding. Release: ACS 2024 5-year (2020-2024); retrieved 5/31/2026.

HOUSING AFFORDABILITY SOURCE

LIHTC route indexed before housing pipeline claims

PDF REVIEW PENDING
City LIHTC PDF routeLocal submittal notice / application-cycle reference PDFAnchor housing-affordability and development-intake questions to an official city document route before replacing synthetic housing heat scores.City LIHTC navigation routeCivicPlus route resolving to the current city-hosted LIHTC documentMonitor whether the city updates the route for future application cycles without scraping private submissions.Georgia DCA program cross-checkState housing-program authority and LIHTC context routeCross-check state terminology, application-cycle calendars, award records, and compliance context before the public dashboard cites housing-credit policy.
document_yearApplication or notice year as stated in the city/DCA document after manual review
program_routeCity LIHTC route, DCA program page, and any official application-cycle URL
project_or_applicantOnly if publicly disclosed in official documents; never infer from rumor or private submissions
status_labelSource-labeled notice, submitted, awarded, denied, under review, or unknown
evidence_urlDirect public URL and retrieval timestamp for every future housing-credit observation

This is a housing-policy/source-routing seed only. It does not claim affordable-housing unit counts, eligibility, award status, financing terms, project approvals, or development pipeline facts until the PDF and DCA records are manually reviewed and source-labeled. Source route checked as public DocumentCenter access; no unit-count, award, or project-status claim is promoted.

WEATHER / HAZARD READINESS SOURCE

NWS point routing for emergency briefings

PUBLIC API
Forecast officeCAEGrid 32,17
County zoneGAC033Burke County alert path
Forecast / fire zoneGAZ077Fire weather GAZ077
Radar stationKCLXWaynesboro, GA
Point metadataRoutes the city point to NWS grid, county, forecast, fire-weather zone, and radar station metadata.ForecastPublic forecast periods for city-readiness context after timestamped fetch.Hourly forecastHourly weather context for events, public works, and safety briefings after timestamped fetch.County alerts pathActive NWS alerts for Burke County zone; fetch live at display time or cache with timestamp.
CACHED GRIDPOINT FORECAST

7 NWS periods cached for source-labeled public works / event readiness

6/4/2026, 11:28:23 AMWaynesboro, Georgia point forecast routed to WFO CAE grid 32,17Open NWS forecast endpoint
Today84°FSunny5 mph NE · 0% precip.
Tonight57°FClear0 to 3 mph SE · 0% precip.
Friday86°FSunny0 to 3 mph NW · 0% precip.
Friday Night61°FPartly Cloudy3 mph S · 0% precip.

This is a cached public forecast snapshot, not an official emergency command feed, dispatch system, or live outage/incident monitor. Refreshed nightly by the public-site build workflow.

CACHED ACTIVE ALERT SNAPSHOT

No active NWS alerts in cached Burke County snapshot

No active NWS watches, warnings, or advisories were returned for Burke County zone GAC033 at 2026-06-04T11:28:23.795Z.

6/4/2026, 11:28:23 AMBurke County, Georgia alert zone GAC033Open NWS alert endpoint

This is source-routing metadata for readiness planning, not a live emergency feed. Alert status and forecasts must be fetched, timestamped, and displayed with NWS attribution before use in public claims. This is a cached public alert snapshot. It is not dispatch telemetry; use the linked NWS endpoint for the latest official alert status.

DRINKING WATER SOURCE SNAPSHOT

EPA ECHO / SDWIS water-system identity + compliance screen

PWSID SEED
Primary community systemWAYNESBOROGA0330004 · Community water system · Ground water
Population served5,900EPA ECHO/SDWIS field, not a live city utility count.
Query scope23 active Burke systemsFiltered display: systems listing Waynesboro as served city.
Waynesboro PWSID screen0 violation qtrs · 0 SNC qtrsGA0330004 · serious violator: No
County query flags5 current-violation rows · 2 SV rows23 inspection rows in ECHO summary; row-level review still required.
Waynesboro subset flags3 smaller systems with violation quarters0 subset systems with SNC quarters; do not conflate with city utility.
GA0330068CROSS ROADS RV PARK WATER SYSTEMTransient non-community system · pop. 30 · 5 violation qtrs · SNC 0
GA0330060DOGWOOD RV PARKTransient non-community system · pop. 110 · 2 violation qtrs · SNC 0
GA0330071DOLLAR GENERAL #21167Transient non-community system · pop. 35 · 0 violation qtrs · SNC 0
GA0330069DOLLAR GENERAL STORE #18659Transient non-community system · pop. 26 · 0 violation qtrs · SNC 0
GA0330065URBAN KITCHENTransient non-community system · pop. 23 · 1 violation qtrs · SNC 0

Low-volume public EPA ECHO/SDWIS seed. Use for water-system identity and public reporting context only; do not present as live utility telemetry, water quality assurance, a customer count, or a complete local operations feed. Violation-quarter fields are screening flags that require row-level SDWIS/ECHO report review before any public water-quality claim. Open system-level ECHO/SDWIS reports for GA0330004 and flagged small systems; verify violations, monitoring periods, contaminants/rules, and dates before display beyond screening flags. Retrieved 6/1/2026, 11:08:31 AM from a public EPA ECHO SDWIS REST query.

STATE WATER VERIFICATION

Georgia EPD route added before water-quality claims

VERIFY BEFORE USE
State source hubGeorgia EPD Drinking Water ProgramHTTP 200 verified · Reference page for public water-system rules, permitting, consumer confidence, lead/copper, water-loss, and compliance-report routes.Public lookup routeDrinking Water WatchLinked by EPD · Manual/low-volume route for water-system detail lookup; do not scrape or present compliance facts until the exact PWS record is opened and verified.Public PDF reportAnnual PWS Compliance ReportPDF reachable · Statewide compliance-report evidence path; parse only with report year, page/table citation, and local PWSID cross-check.Public PDF appendixPWS Violations AppendixPDF reachable · Appendix route for manual QA before any violation-related text is allowed in the app.
pwsIdsystemNamereportYearstateReportUrldrinkingWaterWatchUrltableOrPageCitationretrievedAtverificationStatus
Open Drinking Water Watch manually for GA0330004 / WAYNESBORO and confirm it matches EPA ECHO SDWIS identity before displaying state-level facts.Index the latest Georgia EPD annual compliance report and appendix; do not rely on the 2021 PDF for current compliance posture.If report rows are parsed, display only source-labeled identity/report metadata first; keep violation or water-quality interpretation out until each record is manually verified.

Georgia EPD routes add a state verification path for drinking-water context. They are not live utility telemetry, not a water-quality claim, and not proof of current compliance/noncompliance without exact PWSID, report year, page/table citation, and manual QA. Retrieved 5/31/2026.

UTILITY RATE / WATER REFERENCES

Official city pages now separate source links from unsupported assumptions

REFERENCE INDEX
Official city department pageWater DepartmentOperations source hub for water-service context and links to rate/schedule references.Official city water information pageAbout Our WaterReference page for water-system public information before citing any claims.Official city rates pageWater RatesCandidate source for future utility-cost cards after manual extraction/QA.City DocumentCenter fee schedule2025 Schedule of Rates and FeesPotential normalized fee/rate seed for water, sewer, sanitation, and administrative charges.City DocumentCenter PDFOutdoor Watering RestrictionsCandidate policy/reference citation for drought/readiness and water-use guidance; not telemetry.

Official city pages and PDF links are indexed as a public reference surface only. Rate amounts, watering rules, fees, and customer-service details must be verified directly against the linked city pages/PDFs before being treated as current facts. Retrieved/source-checked 5/31/2026 from public City of Waynesboro pages.

ENERGY RESILIENCE · ACS CONTEXT

Heating-fuel mix seed before utility or outage claims

NO-KEY API SEED
Electricity as heating fuel71.9%1,584 households · ±257 households · ACS 2024 5-year

Resilience planning context, not utility telemetry

ACS survey context only: not utility account records, outage data, load forecasts, rate studies, emergency shelter demand, energy-burden eligibility, or live municipal telemetry.

Open Census Reporter B25040 query
Occupied housing units in table universe2,2042,204 households · ±243
Electricity as house-heating fuel71.9%1,584 households · ±257 households
Utility gas as house-heating fuel28.1%620 households · ±221 households
Waynesboro city71.9%28.1% utility gas · 0.0% propane · 2,204 occupied units
Burke County76.6%11.4% utility gas · 10.3% propane · 9,184 occupied units
Georgia57.0%37.4% utility gas · 4.2% propane · 4,074,366 occupied units

Treat ACS B25040 as energy-resilience planning context only. Do not use it as electric/gas customer counts, utility service territory, outage exposure, energy-burden eligibility, affordability, or emergency-response workload evidence. Waynesboro utility-gas seed: 28.1% (620 households), with share MOE still pending.

DIGITAL INFRASTRUCTURE SOURCE

Digital access context separated from coverage claims

ACS CONTEXT + FCC ROUTE
With internet subscription92.4%2,036 households · MOE ±255 · B28002002
Broadband of any type91.5%2,016 households · MOE ±251 · B28002004
Cellular data plan only25.2%556 households · MOE ±230 · B28002006
Cable, fiber optic, or DSL55.7%1,227 households · MOE ±311 · B28002007
No internet access6.2%137 households · MOE ±105 · B28002013
Data Download HubNational Broadband Map public download navigation and availability-data entry pointFind the current filing-cycle data and permitted download workflow before building county/city coverage cards.Nationwide DataNationwide availability / location-fabric download surface as exposed by the FCC map appScope whether county-level extracts or state-level files can be filtered to Burke County without scraping the map UI.FCC BDC ProgramProgram documentation, challenge process, and official BDC contextKeep Council and operations copy aligned with FCC terminology before presenting broadband-access context.
vintageFCC filing/data vintage used for any exported availability records
geographyCounty, census block, location fabric ID, or city-boundary method used for aggregation
technologyFixed/wireless technology category where published
providerProvider name only if public export terms permit display
availabilityMetricServed/unserved/underserved/maximum advertised speed field with FCC definition attached
Cross-check ACS household subscription estimates against FCC BDC availability exports before any broadband-coverage conclusion.Keep margins of error visible when briefing digital inclusion, remote-work readiness, or grant context.Pair with school, library, and workforce-program sources before the public dashboard supports connectivity interventions.

ACS B28002 is household survey context for subscription/access questions. It is not FCC availability, provider service territory, speed-test evidence, affordability proof, outage data, or municipal broadband telemetry. Source: Census Reporter ACS internet subscription profile ACS 2024 5-year (2020-2024). This seed is a digital-infrastructure source route only. It does not claim current Waynesboro broadband coverage, provider service, subscription rates, affordability, outages, or digital-equity status. Runtime reached FCC National Broadband Map data-download pages with HTTP 200. Help article was Cloudflare-protected from this environment, so documentation review remains manual.

MOBILITY ACCESS · ACS CONTEXT

Household vehicle availability seed

NO-KEY API SEED
Zero-vehicle households16.0%353 households · ±195 · ACS 2024 5-year

Service-access context, not a transportation conclusion

ACS survey context only: not live traffic, transit ridership, household hardship, school transportation, emergency response, or municipal operations telemetry.

Open Census Reporter B08201 query
No vehicle available16.0%353 households · ±195
1 vehicle available48.6%1,072 households · ±267
2+ vehicles available35.3%779 households · MOE derived after covariance review
Waynesboro city16.0%353 of 2,204 households
Burke County9.0%823 of 9,184 households
Georgia5.9%240,272 of 4,074,366 households
ACS survey contextB08201 + B25044Household vehicle availability and tenure split; margins of error visible.
Route / access nextService locations + local transit/nonprofit routesNeeded before translating vehicle access into program or facility recommendations.
Corridor evidenceGDOT / commute / safety sourcesNeeded before any road, traffic, transit, or pedestrian-safety conclusion.
Owner households with no vehicle0.0%0 households · MOE ±20
Renter households with no vehicle22.7%353 households · MOE ±195
Renter households with one vehicle51.7%804 households · MOE ±232

The table can break vehicle availability by household size, but this seed surfaces only high-level city/county/state context until derived MOE and interpretation notes are added. Added B25044 tenure split: renter zero-vehicle households are 22.7% of renter households in the cached ACS seed. ACS B25044 is household survey context for mobility and service-access planning. It is not vehicle registration data, transit ridership, traffic volume, school transportation records, emergency-response evidence, code-enforcement evidence, or municipal telemetry. Pair with commute, GDOT, transit/nonprofit, school, and service-location sources before any public recommendation.

CLEAN WATER PERMIT SOURCE

EPA ECHO facility identity seed for Burke / Waynesboro

PUBLIC REST
County query rows10Active Burke County CWA facility query
Current violation rows3Summary count from ECHO response; verify before citing
Waynesboro sample54 effective · 1 expired in cached sample
GAL038466CITY OF WAYNESBORO628 MYRICK ST · Effective
CWA
GAIS15140CMS WAYNESBORO LLC770 MILLS ROAD · Effective · GAR050000
CWA
GAIS03625FIAMM ENERGY LLC1 FIAMM WAY · Expired · GAR050000
CWA
GA0026786GA POWER/PLANT VOGTLERIVER RD · Effective
CWA
GAIS13332INGEVITY GEORGIA, LLC1000 GARY WAY · Effective · GAR050000
CWA

This seed is a source-routing layer for environmental and utility-permit awareness. It is not a finding of violation, not a complete environmental inventory, and not live operational telemetry. Use ECHO source pages and official records before making facility-specific claims. Retrieved 5/31/2026, 5:10:06 AM from EPA ECHO; this panel is a public source path, not a municipal environmental claim.

RCRA / HAZARDOUS WASTE SOURCE

EPA ECHO handler identity seed for environmental context

PUBLIC REST SEED
County query rows11Active Burke County RCRA handler query
Waynesboro sample6Cached public identity rows, not a complete inventory
Violation rows0Summary metadata only; profile QA required before citing
GAR000079392 · VSQGBURKE TRUCK & TRACTOR706 W. Sixth Street, Waynesboro, GA 30830 · No Violation Identified
No SNC
GAR000065672 · VSQGCVS PHARMACY #3778317 South Liberty Street, Waynesboro, GA 30830 · No Violation Identified
No SNC
GAD054223987 · SQGLEGION INDUSTRIES INCWaynesboro, GA 30830 · No Violation Identified
No SNC
GAR000049403 · SQGMR GOLF CARTSWaynesboro, GA 30830 · No Violation Identified
No SNC
GAD094066321 · SQGSOUTHERN NUCLEAR - PLANT VOGTLEWaynesboro, GA 30830 · No Violation Identified
No SNC
GAR000073668 · VSQGTRACTOR SUPPLY COMPANY #1841Waynesboro, GA 30830 · No Violation Identified
No SNC
Open each ECHO facility profile before exposing compliance-detail drilldowns.Cross-check RCRA handler addresses against zoning, parcel, and business-source routes before map promotion.Keep summary row counts as source metadata until violation/enforcement rows are individually reviewed.

EPA ECHO RCRA rows are public environmental-regulatory source-routing context only. This seed is not a complete local business inventory, a municipal inspection record, a zoning determination, a hazard finding, live environmental telemetry, or a standalone violation/compliance conclusion. Retrieved 5/31/2026, 5:38:32 PM from EPA ECHO RCRA REST Services.

TRI FACILITY SOURCE

EPA Envirofacts TRI identity rows for Burke / Waynesboro

PUBLIC API SEED
County query rows5TRI_FACILITY rows returned by county filter
Waynesboro rows5Public identity sample, not a complete inventory
Closed indicator rows1Field copied as reported; profile QA required
30830FMMTC1FIAM · WAYNESBOROFIAMM ENERGY LLC1 FIAMM WAY, WAYNESBORO, GA 30830 · Closed indicator in facility table
Closed flag
30830GLBBS1201G · WAYNESBOROGLOBE BUSINESS FURNITURE1201 GRIFFIN LANDING RD, WAYNESBORO, GA 30830 · Facility identity row
Identity
30830KWKST770MI · WAYNESBOROSAM DONG GA INC770 MILLS RD, WAYNESBORO, GA 30830 · Facility identity row
Identity
30830STHRN8803R · WAYNESBOROSOUTHERN NUCLEAR - PLANT WILSON/VOGTLE8803 RIVER RD, WAYNESBORO, GA 30830 · Facility identity row
Identity
3083WLSTMG1RITZ · WAYNESBOROGE GRID SOLUTIONS1 RITZ INSTRUMENT WAY, WAYNESBORO, GA 30830 · Facility identity row
Identity
Open EPA TRI Facility Report or Envirofacts release tables for each TRI ID before displaying chemical/release values.Record reporting year, chemical, medium, units, data-quality notes, and EPA profile URL before any public environmental claim.Keep TRI identity separate from city permits, zoning, inspections, code enforcement, and live environmental telemetry.

TRI_FACILITY rows are public environmental source-routing context only. This seed is not a complete environmental inventory, emissions finding, violation finding, health-risk claim, zoning determination, city inspection record, or live telemetry feed. Retrieved 6/1/2026, 6:56:59 AM from EPA Envirofacts; chemical/release tables are intentionally not displayed yet.

HYDROLOGY / STORMWATER SOURCE

USGS active stream-gage inventory for Burke County

PUBLIC NWIS
Query result3 active stream sites13033 county code · ST site type
Closest named routeBRIER CREEK NEAR WAYNESBORO, GAHUC 03060108 · drainage area 473 sq mi
Use in OSSource inventory onlyCurrent stage/flow cards require separate timestamped observations and unit QA.
021973269 · SHELL BLUFF LANDINGSAVANNAH RIVER NEAR WAYNESBORO, GA33.1504, -81.7541 · HUC 03060106
8,300 sq mi
02197830 · IDLEWOODBRIER CREEK NEAR WAYNESBORO, GA33.1183, -81.9636 · HUC 03060108
473 sq mi
02201230 · MIDVILLEOGEECHEE RIVER AT MIDVILLE, GA32.8147, -82.2350 · HUC 03060201
1,340 sq mi
Test USGS instantaneous-values endpoint for the Brier Creek and Savannah River site numbers before showing any current-stage or flow cards.Cross-check gauges against city/county storm-drainage and emergency-management source routes before the public dashboard cites drainage or flood context.Keep the panel as a source inventory until observation timestamps, units, and station availability flags are cached.

USGS NWIS site inventory is a public hydrology source route only. It does not prove flooding, drainage performance, water quality, utility service, or emergency conditions for Waynesboro. Retrieved 5/31/2026, 1:04:28 PM from the public USGS NWIS Site Service.

HYDROLOGY OBSERVATION SEED

Latest USGS point readings added with strict caveats

PUBLIC IV SNAPSHOT
Primary local gage8.47 ftBRIER CREEK NEAR WAYNESBORO, GA · Gage height · provisional P
Connector shape

6 public observation series across 3 stations

Burke County active stream sites near Waynesboro; station observations are point measurements, not citywide flood status.

0219732697,480 ft³/sSAVANNAH RIVER NEAR WAYNESBORO, GA · 5/31/2026, 1:15:00 PM · provisional P02197830825 ft³/sBRIER CREEK NEAR WAYNESBORO, GA · 5/31/2026, 1:30:00 PM · provisional P022012301,490 ft³/sOGEECHEE RIVER AT MIDVILLE, GA · 5/31/2026, 1:00:00 PM · provisional P
Refresh immediately before presentations and show retrieval time because IV data changes throughout the day.Add flood-stage/action-stage metadata only after station-specific thresholds are confirmed from USGS/NWS pages.Keep observations separated from city drainage-performance, emergency-response, and water-quality claims.

USGS instantaneous values are public provisional point observations. They are not flood alerts, emergency-management instructions, stormwater capacity metrics, or live municipal utility telemetry. Retrieved 5/31/2026, 1:38:00 PM from the USGS NWIS Instantaneous Values Service.

HAZARD / RESILIENCE SOURCE ROUTING

Flood and storm-history sources queued before map claims

SOURCE STUB
FEMA NFHLSource identified; runtime TLS check failed in this environmentAnchor future parcel/downtown/infrastructure resilience overlays without inventing flood-zone claims.NOAA Storm EventsSeed connector readyCreate a source-labeled historical hazard context panel for public public works planning.FEMA MSCManual verification path identifiedHuman-verification path before any NFHL flood layer is presented in public demos.
NOAA STORM EVENTS SEED

1 Burke County row found in 2026

Burke County, Georgia county-zone rows; not parcel-level, citywide damage, or live emergency telemetry

31-JAN-26 08:00:00Heavy SnowSingle public 2026 county-zone row observed in the current NOAA details file; trends require multi-year extraction.
Connector postureCSV filter provenStormEvents_details-ftp_v1.0_d2026_c20260519.csv.gz

This is a source-routing stub only. Do not present flood-zone, storm-loss, insurance, or parcel-specific hazard findings until FEMA/NOAA records are fetched, cached, timestamped, and manually QA’d against the official source views. This seed proves the historical storm-event connector shape only. Do not present it as a complete hazard profile, disaster-loss ledger, flood-zone finding, or active emergency feed. Annual CSVs are revised; refresh and QA multiple years before briefing trends.

OPERATIONS SOURCE LEDGER

Official city service pages now anchor the operations lane

REFERENCE LAYER
UtilitiesSource hub identified
Utility Information

Anchor utility module labels, customer-service workflow links, and future records-request questions.

WaterReference ready
Water Department / About Our Water

Source-label water system context while separate public reports or operational exports are requested.

Secondary reference linked in seed file
SewerReference ready
Sewer & Wastewater

Source-label wastewater responsibility and future capital-project / compliance document questions.

Public WorksSource hub identified
Public Works

Tie road, drainage, solid waste, and maintenance placeholders to an official department source hub.

Solid WasteReference ready
Solid Waste

Add public-facing service context before any route, tonnage, or complaint data exists.

Storm drainageReference ready
Storm Drainage Information

Support infrastructure risk questions without pretending there is live drainage telemetry.

Public safetyReference only
Police and Fire department pages

Keep public-safety KPIs synthetic until aggregate incident/response records are officially released or requested.

Secondary reference linked in seed file

This is a public reference layer, not live telemetry. The next trustworthy upgrade is to attach retrieval dates, reports, adopted budgets, work orders, or records-request responses before any operational score is treated as fact.