San Antonio's open data doesn't come from one place. Eight public agencies publish it, each on its own portal, because each does a different job: the City, Bexar County and VIA, which most people have heard of, and the San Antonio River Authority, the Alamo Area MPO, Opportunity Home San Antonio, the Edwards Aquifer Authority and the Texas Department of Transportation, which almost nobody links to. The federal government's live river gauges round it out. The first three have the most, so this page starts with them; the other five are further down.
Not sure where something lives? python3 starters/peek/main.py --find <word> searches every publisher's layers at once.
The short version:
- City of San Antonio publishes what the city does: the services it delivers (311, permits, fire calls), the rules it sets (zoning, historic districts, overlays), the things it builds and maintains (streets, sidewalks, drainage), and its economy. It covers city limits.
- Bexar County publishes the ground and the civic map: census geography with population, schools, every district people vote in, and San Antonio as it was in 1896–97. It covers the whole county, suburbs and unincorporated areas included.
- VIA Metropolitan Transit publishes the buses: every route, stop and scheduled trip, and live positions.
- San Antonio River Authority publishes the river and creeks: floodplains, water quality, the Mission Reach.
- Alamo Area MPO publishes where the region's roads are going: funded projects, flood-exposed roads, bike stress.
- Opportunity Home San Antonio publishes public and affordable housing: its 135 communities, who each is for, homes and bedrooms, by council district.
- Edwards Aquifer Authority publishes the water underneath: the aquifer's level, springflow and drought stage.
- Texas Department of Transportation publishes the state's roads: traffic counts on every state road, with twenty years of history, and every project it's building. Its terms are the strictest here: see below.
The best projects usually combine them: the City's 311 calls divided by the County's census population, or the County's 1896 buildings beside the City's historic landmarks.
Counts and details below were checked in October 2026, from each portal's own listing. Portals change, and the agencies publish more than their portals list, so treat these as approximate: data/catalog.json has this week's count of everything.
Portal: data.sanantonio.gov · about 166 datasets · License: CC BY 4.0 · Credit: Data: City of San Antonio Open Data, CC BY 4.0
| Area | Datasets | Good for |
|---|---|---|
| Service requests | 311 service calls, about 500,000 since 2020, with type, department, opened and closed times, service deadline, late or on time, council district, and location | The richest everyday data in either portal |
| Building and growth | Building permits, Board of Adjustment cases and variances, plats, plan reviews, annexation areas | Where the city is being built, block by block |
| Planning rules | Zoning, future land use, sector and corridor plans, historic districts and landmark sites, the River Improvement Overlay, the Alamo Viewshed, Mission Protection and World Heritage buffers, military overlay zones | Why the city looks the way it does: what can be built where, and what's protected |
| Streets and infrastructure | Streets, sidewalks, crosswalks, bike facilities, speed humps, traffic signs, storm drains and channels, low-water crossings, pavement condition, bond projects | Walking, biking and flooding projects |
| Street safety | Vision Zero projects, severe pedestrian and bicyclist injury areas | Safer streets, which is not the same as crime data |
| Neighborhoods and boundaries | Council districts (2022), neighborhood associations, neighborhood conservation districts, the Central Business District, Downtown District land use, TIRZ, opportunity zones | Boundaries to scope a project to one part of town |
| Economy | Businesses by ZIP and industry, industry clusters, employment and occupations, GDP and graduates against peer cities, economic development incentives | San Antonio's economy over time |
| Fire | Fire department calls for service, inspections, arson investigations | Emergency services inside city limits |
| Parks and places | Park boundaries, trails and trailheads, libraries, City Hall, public safety facilities | Where things are |
| Health | COVID-19 cases, deaths and vaccinations, by ZIP (countywide) | Historical public health |
| New and unusual | A pilot street-light sensor dataset, good-neighbor engagement events | Worth opening to see what's inside |
| Police | SAPD arrests, offenses, and calls for service | See "Build with care" in the README: the starters here don't use these |
311, building permits, zoning and planning rules, fire department data, street infrastructure, street-safety data, the economy datasets, and the City's own neighborhood and council boundaries.
The portal runs CKAN, and many of its geographic datasets are also ArcGIS feature services.
# Find datasets
https://data.sanantonio.gov/api/3/action/package_search?q=311
# Read rows from a dataset's table (resource_id from the dataset page)
https://data.sanantonio.gov/api/3/action/datastore_search?resource_id=...&limit=100
# Ask questions in SQL, so you don't download everything
https://data.sanantonio.gov/api/3/action/datastore_search_sql?sql=SELECT "COUNCIL_DIST", COUNT(*) FROM "resource-id" GROUP BY "COUNCIL_DIST"Watch for duplicate copies. Some datasets exist twice: once as a CKAN table and once as an ArcGIS layer, with different column names. 311 calls are COUNCIL_DIST and TYPENAME in the CKAN table, and CouncilDistrict and TypeName in the ArcGIS layer the 311-by-district starter uses. Pick one copy and stay with it.
Filter on the server. CKAN supports filters and full SQL, and ArcGIS supports where and outStatistics. Downloading everything and filtering locally is slower, and it hides the fact that the API could have done it.
Portal: gis-bexar.opendata.arcgis.com · 35 items, 28 of them map layers, back to 1896, plus Tricentennial layers back to 1718 that aren't on the portal · License: set per dataset, in each layer's description · Credit: Data: Bexar County Information Technology GIS
| Area | Datasets | Good for |
|---|---|---|
| San Antonio, 1718–1800s (not on the portal) | Built for the Tricentennial and published only in the County's ArcGIS account: RullmanAcequia, 16 stretches of the Spanish acequias with the year each was dug and abandoned; Labores, the mission fields; 300_GrantedLots, 348 land grants with grantee, year and labor; Rullman_River, the river as these maps draw it; SAMissions and Spanish_Forts |
How the city was laid out, and why. Grantees are 18th-century settlers, many of them Canary Islanders |
| San Antonio, 1896–97 | Historic Buildings (1896): 15,349 building outlines from the Sanborn fire-insurance maps, with building type, land use, owner, number of floors and square footage. City Blocks (1896). Historic Points of Interest (1896–97): about 4,200 places. Residences and Employment (1897): about 21,000 and 11,000 records from the city directory | History no other county has. The floor counts mean the 1896 city can be rebuilt in 3D |
| Census geography | Census tracts, block groups and blocks, with 2020 Census population and race counts (P1_001N is total population), and a data dictionary |
Anything per person: divide by population before comparing areas |
| Who represents you | Voter precincts, early voting sites, U.S. Congress (redistricted for 2026), Texas House, Texas Senate and State Board of Education (redistricted 2022), County Commissioner precincts | "Who represents me?" projects |
| Courts | Justice of the Peace and Constable precincts and offices | County justice geography |
| Schools | Public and private schools | Not in the City's portal |
| Emergency services | Emergency Services District (ESD) legal boundaries and response areas | Who answers 911 outside city limits |
| Places | County parks, libraries, military installations, ZIP code areas, the county boundary | Countywide reference |
| Pointers, not data | Address points and streets, parcels, plat maps and land records, contours, traffic lights and signs, foreclosure notices | These are PDFs explaining where to request the data from other County offices |
The 1718–1800s and 1896–97 history, census geography with population, schools, voting and representation districts, courts geography, emergency services districts, and countywide coverage beyond city limits.
- The 1897 Residence and Employment layers are real people, with names and occupations, and race recorded in the language of the time. Use them for history in aggregate, never to look up individuals.
- Election data: the early voting sites layer is a reference, not the official list. For where and when to vote, always link the Bexar County Elections Department and VoteTexas.gov.
Every layer is an ArcGIS feature or map service. Find a layer's service address on its page in the portal, then query it. Layers that aren't on the portal, like the Tricentennial set, are listed in the County's services directory; much of what's there is internal dashboards and working files, so stick to layers with a clear public purpose.
# Count, filter, and get GeoJSON in latitude and longitude
.../FeatureServer/0/query?where=1=1&outFields=*&outSR=4326&f=geojson
# Which polygon is this point in? (e.g. which voter precinct is Geekdom in)
.../MapServer/0/query?geometry=-98.4936,29.4241&geometryType=esriGeometryPoint&inSR=4326&spatialRel=esriSpatialRelIntersects&outFields=*&f=jsonServices return at most 1,000 to 2,000 features per request: page with resultOffset until exceededTransferLimit is false. The acequias --1897 starter shows how.
Developer page: viainfo.net/developers-resources · License: VIA's developer license · Credit: Data provided by VIA Metropolitan Transit
The schedule (GTFS). One zip, about 6 MB: https://www.viainfo.net/BusService/google_transit.zip. GTFS is the format every transit agency and trip planner uses, so what you learn here works for any city. Inside:
| File | What it holds |
|---|---|
stops.txt |
About 6,100 stops, with names, coordinates and wheelchair boarding |
routes.txt |
88 routes |
trips.txt |
About 14,700 scheduled trips, each with a route, direction and destination sign |
stop_times.txt |
When every trip reaches every stop (the big one, about 35 MB unzipped) |
calendar.txt, calendar_dates.txt |
Which days each schedule runs, and the holiday exceptions |
shapes.txt |
The line each route draws on a map |
transfers.txt, fare_attributes.txt, fare_rules.txt |
Transfers and fares |
agency.txt, feed_info.txt |
Who publishes it, and the dates the schedule is valid |
VIA publishes a new schedule a few times a year; feed_info.txt says which dates the current one covers.
Live data (GTFS-realtime). Four protobuf feeds:
| Feed | Address |
|---|---|
| Vehicle positions | http://gtfs.viainfo.net/vehicle/vehiclepositions.pb |
| Trip updates (live arrival predictions) | http://gtfs.viainfo.net/tripupdate/tripupdates.pb |
| Service alerts | http://gtfs.viainfo.net/alert/alerts.pb |
| Combined feed | http://gtfs.viainfo.net/gtfs-realtime/trapezerealtimefeed.pb |
They're served over plain http://, so a web page on https:// can't fetch them directly: put a small server or serverless function in between. Read them with gtfs-realtime-bindings (Python or JavaScript).
The buses: every route, stop and trip, and where buses are right now. Neither portal carries transit.
- Use is limited to "uses that utilize the VIA Data for assisting mass transportation riders." A departure board or a "getting here" block qualifies; analysis unrelated to riders may not.
- Credit "Data provided by VIA Metropolitan Transit" wherever the data shows.
- No VIA logos or trademarks, and never present a project as VIA's, or as made with or in partnership with VIA.
- The data is as-is, VIA can change or stop it without notice, and using it means accepting VIA's indemnity terms.
These agencies run their own portals, separate from the City's and the County's, and most of what they publish answers the same ArcGIS queries. peek reads any of them, and prints the right credit line. Counts were checked on October 29, 2026.
Some of their public layers are surveys and feedback forms that hold what people submitted. Leave those alone.
San Antonio River Authority — sariverauthority-sara-tx.opendata.arcgis.com
The river and its creeks: watersheds, floodplains (including drafts), stream centerlines, water quality and impaired stretches, the restored parks of the Mission Reach (Acequia Park among them), paddling trails, and creek and trail projects across the county. More than 100 public layers.
- Terms: the River Authority's own, in each layer's description. Data is as-is, and you must cite the date you retrieved it and say: "This uses River Authority's data but is not endorsed or verified by River Authority."
- Live data: its "Current Conditions" layer copies USGS gauge readings, but it isn't kept current. For live creek levels, go to USGS (below).
Alamo Area MPO — AAMPO GeoNexus
The Alamo Area Metropolitan Planning Organization plans and funds the region's roads and transit, across Bexar, Comal, Guadalupe and part of Kendall counties. Its layers are about where the region is going:
- Funded projects: the Transportation Improvement Program, 2027–2030 (68 projects with cost, year and agency), and the long-range Mobility 2050 plan.
- Resilience: 6,372 road segments, plus bridges, culverts and airport pavement, each scored for how much of it floods in storms from 5-year to 500-year.
- Getting around: bike facilities and each road's level of traffic stress for cyclists, congestion, and VIA's network.
- People: census layers on income, language and the digital divide.
- Major developments: a tracker of big regional projects.
Terms: as-is, not legal surveys, per each layer's disclaimer. Credit: Data: Alamo Area Metropolitan Planning Organization
The city's housing authority publishes about a dozen public layers under its ArcGIS account (services2.arcgis.com/nH68joXCaOE0Iiws): its housing communities and developments by council district, and its own low water crossings map. There's no portal; peek --find finds them. Terms: informational use only, per its disclaimer. Credit: Data: Opportunity Home San Antonio
Edwards Aquifer Authority — data.edwardsaquifer.org
The aquifer under San Antonio, and the springs it feeds. The authority posts the daily level of the J-17 index well in Bexar County, springflow at Comal and San Marcos Springs, and the drought stage, on its data portal and website. It also publishes more than 100 map layers (aquifer zones, recharge areas, monitoring sites) under services2.arcgis.com/p0kPTvyvhLmiT5Ha.
- Terms: most layers are marked for demonstration and informational use. Read the disclaimer on the one you use.
- Note: the daily readings come as a web page and an embeddable widget, not a data feed.
- Credit:
Data: Edwards Aquifer Authority
Texas Department of Transportation — gis-txdot.opendata.arcgis.com
TxDOT publishes for the whole state, so most of its 800-plus layers aren't about San Antonio, and many are old or internal. peek recognizes and credits any TxDOT layer you give it by address, but peek --find and the catalog don't sweep TxDOT's account; the layers worth starting from are listed here and in data/. Checked November 14, 2026:
- Traffic counts:
TxDOT_AADT_Annuals_(Public_View), the Annual Average Daily Traffic at every count station on state roads, with nineteen years of history. 893 stations in Bexar County, counted through 2025. busiest-roads reads it. - Projects:
TxDOT_DCIS_All_Projects, every project TxDOT runs, with its highway, limits, type of work, stage and estimated cost. 428 active in Bexar County, about $11.7 billion.busiest-roads --buildingreads it. - Road conditions, live:
DriveTexas_PointsandDriveTexas_Lines, closures, construction and delays on state highways, refreshed about every 15 minutes. Both were empty when checked; TxDOT also publishes a national-standard work-zone feed (WZDx), listed on data.gov. - Crash data: not an open API. TxDOT's CRIS query tool and a public extract with personal details removed are available by request at txdot.gov. Leave crash records out of anything public.
All of these sit under services.arcgis.com/KTcxiTD9dsQw4r7Z.
- Terms: informational use only and no warranty; not for commercial use or resale; and distribution to third parties needs TxDOT's written consent. Explore it for yourself; ask TxDOT before you publish anything made from it. The full text is in ATTRIBUTION.md.
- Credit:
Data: Texas Department of Transportation
USGS river gauges — waterdata.usgs.gov
The U.S. Geological Survey runs live stream gauges in San Antonio's creeks and river, reporting water height and flow every 15 minutes, with no key. The two downtown:
- 08178000: San Antonio River at San Antonio
- 08178500: San Pedro Creek at Furnish St
curl "https://waterservices.usgs.gov/nwis/iv/?format=json&sites=08178000,08178500¶meterCd=00065,00060"00065 is gage height in feet; 00060 is flow in cubic feet per second.
- Terms: U.S. government work, public domain.
- Credit:
Data: U.S. Geological Survey
CPS Energy, SAWS, Port San Antonio, Visit San Antonio, Centro San Antonio and the Bexar Appraisal District don't publish open data we could find. If one does, open an issue.
The full summary of every source's terms is in ATTRIBUTION.md.