Fact Lease

Fact Lease records what public web pages say about Houston and San Antonio commercial suites — dated, sourced, never invented.

Map layers and sources

Each layer is public data with a named source, a license, and an as-of date. A value belongs to the geography named on the row. It does not describe a suite, a building, or a tenant.

Some layers are not published.

Layers

Map layers by city. The same notes follow, one section per layer.
LayerGroupSan AntonioGreater HoustonGeoJSON
Anchors: grocery, hospitals, campuses People Shipped · as of 8 Oct 2026 · OpenStreetMap extract 2026-10-08 · OpenStreetMap node, or way or relation center · 435 features · OSM Shipped · as of 8 Oct 2026 · OpenStreetMap extract 2026-10-08 · OpenStreetMap node, or way or relation center · 1306 features · OSM San Antonio GeoJSON Greater Houston GeoJSON
Business establishments People Shipped · as of 12 Mar 2023 · 2023 · Census ZIP Code Tabulation Area · 89 features · Census ZBP Shipped · as of 12 Mar 2023 · 2023 · Census ZIP Code Tabulation Area · 253 features · Census ZBP San Antonio GeoJSON Greater Houston GeoJSON
Daytime workers per sq mi People Shipped · as of 31 Dec 2023 · 2023 · Census tract · 449 features · LEHD LODES Shipped · as of 31 Dec 2023 · 2023 · Census tract · 1381 features · LEHD LODES San Antonio GeoJSON Greater Houston GeoJSON
Median household income People Shipped · as of 31 Dec 2024 · 2020-2024 · Census tract · 449 features · ACS 5-yr Shipped · as of 31 Dec 2024 · 2020-2024 · Census tract · 1381 features · ACS 5-yr San Antonio GeoJSON Greater Houston GeoJSON
Flood zones Risk Shipped · as of 10 Jun 2026 · FIRM effective 2005-09-02 to 2026-06-10 · FEMA flood hazard zone · 8261 features · FEMA NFHL Shipped · as of 29 Jan 2021 · FIRM effective 2006-04-05 to 2021-01-29 · FEMA flood hazard zone · 19774 features · FEMA NFHL San Antonio chunked GeoJSON /layers/flood/san-antonio/{cell}.geojson Greater Houston chunked GeoJSON /layers/flood/houston/{cell}.geojson
Reported incidents per sq mi Risk Shipped · as of 30 Sep 2026 · Oct 2025 to Sep 2026 · ZIP · 61 features · SAPD offenses Shipped · as of 31 Dec 2024 · Jan 2024 to Dec 2024 · HPD beat · 117 features · HPD NIBRS San Antonio GeoJSON Greater Houston GeoJSON
Commercial building permits Rules & incentives Shipped · as of 30 Sep 2026 · Oct 2025 through Sep 2026 · ZIP Code Tabulation Area · 89 features · COSA permits Coming soon. data.houstontx.gov publishes a citywide monthly residential permit summary under its open-data terms, not commercial permits by ZIP. The Houston Permitting Center publishes weekly Permit Activity Report workbooks (new construction, remodel, and change of use by ZIP) at https://www.houstonpermittingcenter.org/sold-permits-search but states no license that allows a redistributed derived layer. Individual commercial permits are behind a search page and Texas Public Information Act requests. This city is not shipped. San Antonio GeoJSON
Opportunity Zones and TIRZ Rules & incentives Shipped · as of 11 Jun 2026 · Designated 2018; TIRZ boundaries as of 11 Jun 2026 · Census tract (Opportunity Zone) and TIRZ boundary · 45 features · COSA TIRZ Shipped · as of 24 May 2023 · Designated 2018; TIRZ boundaries as of 24 May 2023 · Census tract (Opportunity Zone) and TIRZ boundary · 174 features · COH TIRZ San Antonio GeoJSON Greater Houston GeoJSON
Zoning Rules & incentives Shipped · as of 4 Oct 2026 · City GIS base districts · City of San Antonio base zoning district · 57140 features · COSA zoning Houston has no zoning ordinance San Antonio chunked GeoJSON /layers/zoning/san-antonio/{cell}.geojson

Anchors: grocery, hospitals, campuses

Marks grocery stores, big-box stores, malls, hospitals, colleges, stadiums, and airports that draw people past a site.

Group: People

Method: One Overpass query per metro bbox (San Antonio west -99.15 south 28.95 east -97.9 north 29.95; Houston west -96.2 south 28.9 east -94.6 north 30.4) to https://overpass.openstreetmap.fr/api/interpreter, with the Fact Lease layer user agent, cached, and spaced so the two cities are not sent together. https://overpass-api.de/api/interpreter reset the TLS handshake on this refresh (unexpected EOF), so the extract is the same query against the public Overpass instance that answered. Categories are shop=supermarket (grocery); shop=department_store and shop=wholesale (department or big-box); shop=mall (shopping center or mall); amenity=hospital; amenity=university or amenity=college; leisure=stadium (stadium or arena); aeroway=aerodrome with a 3-letter iata tag. A node uses its coordinate. A way or relation uses the Overpass center. disused=yes, abandoned=yes, and demolished=yes are dropped. The name is the OSM name tag, or name:en when name is absent, otherwise null. No address, brand, or operator is copied. Two features with the same category and the same name within 80 meters collapse to one pin (a way kept ahead of a relation, then a node) so a building outline and its node are not both drawn. This GeoJSON is a derivative database of OpenStreetMap offered under the Open Database License 1.0. Credit © OpenStreetMap contributors, and share any derivative database under the same license.

Caveat: These are OpenStreetMap tags, not a verified tenant list and not a Fact Lease measurement. Coverage depends on what volunteers have mapped. The file is a derivative database under ODbL 1.0; attribute © OpenStreetMap contributors. Names are the OSM name only. Letters on the map are G grocery, D department or big-box, P mall, H hospital, U university or college, E stadium, A airport.

Sources

  • OpenStreetMap (OSM). City: San Antonio and Greater Houston. License: Open Database License (ODbL) 1.0. This GeoJSON is a derivative database.. Retrieved 8 Oct 2026. © OpenStreetMap contributors. © OpenStreetMap contributors

San Antonio

Shipped · as of 8 Oct 2026 · OpenStreetMap extract 2026-10-08 · OpenStreetMap node, or way or relation center · 435 features · OSM San Antonio GeoJSON

Greater Houston

Shipped · as of 8 Oct 2026 · OpenStreetMap extract 2026-10-08 · OpenStreetMap node, or way or relation center · 1306 features · OSM Greater Houston GeoJSON

Business establishments

Shows how many employer establishments sit in each ZIP, and which sectors account for that count.

Group: People

Method: Figures are U.S. Census Bureau ZIP Code Business Patterns for 2023, the newest reference year whose bulk file was on www2.census.gov when this layer was refreshed. The Census Data API at api.census.gov/data/2023/cbp requires a key and was not called; the script reads the same product's bulk files zbp23totals.zip (total establishments and mid-March employment) and zbp23detail.zip (establishments by NAICS sector). The detail file stores each sector as a 6-character root: 44---- is retail trade (NAICS 44-45), 31---- is manufacturing (31-33), and 42----, 52----, 53----, 54----, 62----, and 72---- are wholesale, finance and insurance, real estate, professional services, health care, and accommodation and food. The national file has no separate 32----, 33----, or 45---- row; 3-digit rows such as 339/// and 445/// sit under those roots and are not added again. A sector count is 0 when Census published the ZIP and omitted that sector. Establishment counts are not suppressed; a sector with no establishments is left out of the file. A ZIP Census does not publish stays null on every count, including the total, rather than zero. A repeated sector row keeps the first count and is not summed. Employment is the published noise-infused count when emp_nf is G (under 2 percent), H (2 percent to under 5 percent), or J (5 percent or more), including a published zero. Flags D, S, and N, and the older A-M suppression letters, withhold the count (Census replaces it with zero) and this layer stores null. Size-class columns are ignored: an N there is not a number, and summing the classes would invent a total the file does not publish. The map classes establishments per square mile of ZCTA land. San Antonio polygons are 2010 ZCTAs, so the denominator is ALAND_SQMI from the 2010 Gazetteer (Gaz_zcta_national.zip, the file whose columns include POP10 and HU10). Houston polygons are 2020 ZCTAs, so the denominator is ALAND_SQMI from the 2020 Gazetteer. The rate is the establishment total divided by the Gazetteer's published ALAND_SQMI, rounded to one decimal. It is not measured from the simplified polygon. A ZIP with no positive land area stays null rather than switching to the raw count. Polygons are the ZCTA shapes already on the rent map, copied here and not edited in public/map. A ZIP code is not the same boundary as a ZCTA. Class breaks are quintiles of the painted values across both cities. The top-sectors line is up to three sectors with a count above zero, written as the sector name, the count, and of the ZIP total.

Caveat: ZIP Code Business Patterns count establishments with paid employees during the week of March 12. They leave out businesses with no paid employees, and they are not a storefront count or a leasing inventory. A ZIP code is not the same area as the ZCTA drawn here. Employment is noise-infused and is blank when Census withholds it. A sector shows 0 only when Census published the ZIP and left that sector out. A ZIP Census does not publish is blank, not zero. Per square mile uses Gazetteer land area for the ZCTA vintage named in the method, not the area of the simplified polygon.

Sources

San Antonio

Shipped · as of 12 Mar 2023 · 2023 · Census ZIP Code Tabulation Area · 89 features · Census ZBP San Antonio GeoJSON

Greater Houston

Shipped · as of 12 Mar 2023 · 2023 · Census ZIP Code Tabulation Area · 253 features · Census ZBP Greater Houston GeoJSON

Daytime workers per sq mi

See how many jobs are located in the tract, all jobs (JT00), per square mile of land.

Group: People

Method: All jobs (JT00), segment S000, from LEHD LODES 2023 workplace-area characteristics for Texas. Block rows (15-digit w_geocode) are summed to the census tract (first 11 digits): total jobs C000, manufacturing CNS05, retail CNS07, professional services CNS12, health care CNS16, and accommodation and food CNS18. Jobs per square mile is C000 divided by land area in square miles (TIGER ALAND in square meters / 2,589,988.110336), rounded to the nearest job. Blocks with no jobs are absent from LODES, so a tract in a county that was read and that has no rows is zero jobs. Class breaks are quintiles of jobs per square mile for the tracts shipped in both cities, rounded to 2 significant figures. TIGERweb rejected the request from this network, so tract lines are TIGER/Line 2024 census tracts (NAD83 geographic, about a meter from WGS84 in Texas). Land area is the TIGER ALAND field, not the simplified polygon. Drawn coordinates use Douglas-Peucker tolerance 0.0005 degrees and 5 decimal places.

Caveat: Counts are jobs located in the tract (the workplace, not the worker's home) and cover all jobs (JT00). LODES adds statistical noise, so a small count is not an exact job total. A tract with no rows is zero jobs because LODES omits blocks that have none. A tract with no land area has no jobs-per-square-mile figure. The vintage lags the calendar. This is an area figure, not a figure for any suite.

Sources

San Antonio

Shipped · as of 31 Dec 2023 · 2023 · Census tract · 449 features · LEHD LODES San Antonio GeoJSON

Greater Houston

Shipped · as of 31 Dec 2023 · 2023 · Census tract · 1381 features · LEHD LODES Greater Houston GeoJSON

Median household income

See the median household income of the census tract around an address, with the published margin of error.

Group: People

Method: Population (B01003), households (B11001), median age (B01002), median household income and its 90 percent margin of error (B19013), and per capita income (B19301) are the published ACS 2024 5-year estimates for the census tract. A Census sentinel such as -666666666 is stored as null. moeLarge is true when (margin of error / 1.645) / median household income is over 0.30. The Census data API redirected a keyless request to its missing-key page, so these figures are the same release's table-based summary file. Class breaks are quintiles of median household income for the tracts shipped in both cities, rounded to the nearest $1,000. TIGERweb rejected the request from this network, so tract lines are TIGER/Line 2024 census tracts (NAD83 geographic, about a meter from WGS84 in Texas). Land area is the TIGER ALAND field, not the simplified polygon. Drawn coordinates use Douglas-Peucker tolerance 0.0005 degrees and 5 decimal places.

Caveat: A 5-year estimate is not one year. The margin of error is the published 90 percent margin for median household income, shown as ± that amount. A large margin (coefficient of variation over 30 percent) is flagged. A figure the Census Bureau did not publish is blank, not zero. This is an area figure, not a figure for any suite.

Sources

San Antonio

Shipped · as of 31 Dec 2024 · 2020-2024 · Census tract · 449 features · ACS 5-yr San Antonio GeoJSON

Greater Houston

Shipped · as of 31 Dec 2024 · 2020-2024 · Census tract · 1381 features · ACS 5-yr Greater Houston GeoJSON

Flood zones

Shows the effective FEMA flood zone at a site: the regulatory floodway, the 1% annual-chance area, and the 0.2% area.

Group: Risk

Method: Effective FEMA NFHL only (MapServer public/NFHL layer 28, Flood Hazard Zones / S_FLD_HAZ_AR). Preliminary FIRMs, pending layers, and Harris County MAAPnext are not read. Polygons with SFHA_TF = T are kept: a ZONE_SUBTY containing FLOODWAY, ENCROACHMENT, or FLOWAGE EASEMENT is cat floodway; every other SFHA zone (A, AE, AH, AO, A99, V, VE, and any other SFHA code) is cat 1pct. A ZONE_SUBTY containing 0.2 PCT or 0.2 PERCENT is cat 0.2pct (shaded Zone X). Plain Zone X and Zone D are not drawn. The service generalizes at maxAllowableOffset 0.0001 degrees (about 11 m) in WGS84; coordinates are then rounded to 4 decimals. A polygon still over 80 KB, or a cell over 400 KB, is simplified further (up to about 0.003 degrees). Each polygon is copied into every 0.1 degree cell its bounding box touches inside the metro envelope. Polygons are not clipped to the cell, so the same feature id (FLD_AR_ID) can appear in neighboring cells and can be slightly coarser in a dense cell. Dedupe drawn copies by feature id. FIRM panel effective dates are the minimum and maximum EFF_DATE on layer 3 inside the same envelope. A polygon that collapses under generalization is omitted from the map. A suite zone in at-buildings.json is a separate unsimplified point query against the same effective layer.

Caveat: These are regulatory zones on the effective Flood Insurance Rate Map, not a forecast that a building will flood. Confirm a site on the official FIRM or FIRMette at https://msc.fema.gov. Houston has many Letters of Map Revision, and Atlas 14 rainfall studies are not effective on every panel. Shapes on this map are generalized. A zone stored for a suite comes from a separate unsimplified point query and can still disagree with the building when the Census address point sits in the street.

Sources

  • FEMA National Flood Hazard Layer (FEMA NFHL). City: San Antonio and Greater Houston. License: Public domain (U.S. government work). Retrieved 8 Oct 2026. Federal Emergency Management Agency.

San Antonio

Shipped · as of 10 Jun 2026 · FIRM effective 2005-09-02 to 2026-06-10 · FEMA flood hazard zone · 8261 features · FEMA NFHL San Antonio chunked GeoJSON /layers/flood/san-antonio/{cell}.geojson

Greater Houston

Shipped · as of 29 Jan 2021 · FIRM effective 2006-04-05 to 2021-01-29 · FEMA flood hazard zone · 19774 features · FEMA NFHL Greater Houston chunked GeoJSON /layers/flood/houston/{cell}.geojson

Reported incidents per sq mi

Official reported-incident counts by area, for a place you might lease.

Group: Risk

Method: San Antonio counts each SAPD offense row whose NIBRS crime-against value is person, property, or society, for Oct 2025 to Sep 2026. A month is included only when the extract's latest report date in that month is the last calendar day, and the twelve months are consecutive. Rows without a five-digit ZIP are omitted. 53 offenses in that window have a ZIP with no polygon in the Census 2010 ZCTA file used here; they are not drawn and not assigned to a neighbor. San Antonio is drawn by ZIP. A ZIP can cross agency lines, so the polygon is not an SAPD boundary. Houston counts Group A offense counts from the City of Houston GIS republish of HPD's public NIBRS yearly file for Jan 2024 to Dec 2024, summed by beat. Month row counts in that file are 17540, 16764, 18074, 18871, 19623, 18561, 18257, 18263, 17930, 17961, 16579, 16708. Group B rows and justifiable homicide are omitted because that file does not give them a crime-against category. 1564 Group A offenses have a blank beat or a code that is not an HPD beat id (including out-of-jurisdiction and campus codes) and are omitted. 4172 Group A offenses sit on a beat id with no polygon in the June 2025 beat file and are omitted. NIBRSPublicView2025.csv returned HTTP 302 to /. NIBRSPublicView2026.csv returned HTTP 302 to /. The map uses the City of Houston GIS republish of the calendar year that could be read here, not those yearly CSV files. The map paints reported incidents per square mile. Quintile breaks are the fifths of areas in that city only, at one decimal. Houston and San Antonio are not placed on one shared threshold. api.census.gov requires a key this refresh does not have, and no beat-population crosswalk is used, so resident population and the per-1,000 rate are left blank. Per square mile uses the city's published beat area when the polygon carries one, otherwise the polygon area. A very small beat can show a large per-square-mile figure because that published area is the denominator. Sheriff, constable, school-district, and university police reports are not in these counts. Houston beats are Houston Police Department geography and do not cover the rest of Greater Houston. FBI and Texas DPS figures are agency-wide only and are not split onto these areas. The San Antonio coverage polygon is the City of San Antonio boundary published by its Planning and Community Development Department. The Houston coverage polygon is the City of Houston limit where the city's police-service field is full.

Caveat: Reported incidents only, published by the San Antonio Police Department (SAPD) or the Houston Police Department (HPD) for the city on the map. Sheriff, constable, school-district, and university police are not included. Not all crime is reported. Counts follow where people are, including daytime populations and retail centers, not only residents. Beats and ZIP areas differ in size. In San Antonio a ZIP can cross agency lines and is not an SAPD service area. Read this alongside other information. A per-resident rate is left blank where resident population is under 1,000 or was not published for that area.

Sources

  • City of San Antonio Open Data, SAPD Offenses (SAPD offenses). City: San Antonio. License: Creative Commons Attribution 4.0. Retrieved 8 Oct 2026. City of San Antonio, SAPD Offenses. City of San Antonio, SAPD Offenses (https://data.sanantonio.gov/dataset/sapd-offenses), licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/).
  • US Census Bureau 2010 ZIP Code Tabulation Areas (Census ZCTA). City: San Antonio. License: Public domain (US government work). Retrieved 8 Oct 2026. US Census Bureau 2010 ZCTAs, the same polygons as the Fact Lease rent map.
  • City of Houston GIS, HPD NIBRS Yearly Cases (2020-2024) (HPD NIBRS). City: Greater Houston. License: Public domain (City of Houston GIS; COHGIS data may be copied without permission). Retrieved 8 Oct 2026. Houston Police Department and Houston Information Technology Services (HITS-GIS).
  • City of Houston GIS, Houston Police Beats (HPD beats). City: Greater Houston. License: Public domain (City of Houston GIS; COHGIS data may be copied without permission). Retrieved 8 Oct 2026. Houston Police Department, HITS-GIS. Beat boundaries updated June 2025..
  • City of San Antonio, city boundary (COSA limits). City: San Antonio. License: City of San Antonio GIS warranty disclaimer; the item states no prohibition on copying. Retrieved 8 Oct 2026. City of San Antonio Planning and Community Development Department, Comprehensive Division.
  • City of Houston GIS, City Limits (full police service) (COH limits). City: Greater Houston. License: Public domain (City of Houston GIS). This item's license text is blank. Sibling COHGIS HPD layers on the same organization say COHGIS data is in the public domain and may be copied without permission.. Retrieved 8 Oct 2026. City of Houston Police Department mapping, City Limits (full police service).

San Antonio

Shipped · as of 30 Sep 2026 · Oct 2025 to Sep 2026 · ZIP · 61 features · SAPD offenses Coverage: SAPD jurisdiction boundary. San Antonio GeoJSON

Greater Houston

Shipped · as of 31 Dec 2024 · Jan 2024 to Dec 2024 · HPD beat · 117 features · HPD NIBRS Coverage: HPD jurisdiction boundary. Greater Houston GeoJSON

Commercial building permits

Shows where the city has issued commercial building permits, a sign of construction activity around a site.

Group: Rules & incentives

Method: Counts City of San Antonio building permits issued in the last 12 complete calendar months whose PERMIT TYPE and WORK TYPE are one of: Comm New Building Permit / New, Comm Addition Permit / New, Comm Remodel Permit / Existing, Comm Shell Permit / New (a new building shell), Comm Finish Out Permit / New (commercial interior finish-out). Trade permits, minor commercial repair, sitework, fences, and residential permits are not counted, so one project is not counted once per trade. The ZIP is the five-digit group at the end of the published address. A permit whose ZIP is not in the city's ZCTA file is left out. Duplicate permit numbers count once. Declared valuation is the sum of figures the city published on those permits; a blank is left out of the sum and is not stored as zero. The same project valuation is sometimes repeated on related permits, so the sum is not a de-duplicated construction cost. ZIPs with no matching permit keep count 0, which was observed, not estimated. Class breaks are quintiles of ZIPs with at least one counted permit. A count of 0 is not a quintile class. The ZIP counts and valuation sums are a Fact Lease aggregation of the city's permit file, not an official city table.

Caveat: Issued permits are not completed buildings and not a forecast. Declared valuation is the applicant's figure as the city published it. A blank valuation is omitted from the sum, and the same figure can appear on more than one permit for one project. Addresses and owner names are not shown.

Sources

  • City of San Antonio Development Services, PERMITS ISSUED (COSA permits). City: San Antonio. License: Dataset license_id cc-by (Creative Commons Attribution), labeled on the Building Permits package. COSA Open Data Portal Terms of Use (last modified January 8, 2020) grant a non-exclusive revocable license to use and distribute, and require attribution to the department plus a citation of the webpage and the date. The ZIP counts are a modified aggregation, not official government data.. Retrieved 8 Oct 2026. City of San Antonio Development Services Department. City of San Antonio Development Services Department

San Antonio

Shipped · as of 30 Sep 2026 · Oct 2025 through Sep 2026 · ZIP Code Tabulation Area · 89 features · COSA permits San Antonio GeoJSON

Greater Houston

Coming soon. data.houstontx.gov publishes a citywide monthly residential permit summary under its open-data terms, not commercial permits by ZIP. The Houston Permitting Center publishes weekly Permit Activity Report workbooks (new construction, remodel, and change of use by ZIP) at https://www.houstonpermittingcenter.org/sold-permits-search but states no license that allows a redistributed derived layer. Individual commercial permits are behind a search page and Texas Public Information Act requests. This city is not shipped.

Opportunity Zones and TIRZ

A tenant can see whether a site sits in a 2018 designated Opportunity Zone or a tax increment reinvestment zone.

Group: Rules & incentives

Method: Opportunity Zone polygons are the HUD Opportunity Zones layer of tracts designated in 2018 (IRS Notice 2018-48, updated by Notice 2019-42; layer coverage date December 2019). The geometry edit date on that layer is not the designation date. Nominations for the 2027 round, including the Texas nominations sent to Treasury on 4 September 2026, are not drawn. A feature is kept only when the GEOID is 11 digits. The name is Census tract plus that GEOID. San Antonio keeps Bexar County (029). Houston keeps Harris (201), Fort Bend (157), Montgomery (339), Brazoria (039), Galveston (167), Waller (473), Liberty (291), Chambers (071), and Austin (015). A tract is kept whole when its bounding box intersects the city map frame. San Antonio TIRZ polygons are the City of San Antonio TIRZ layer. The id is the integer zone number and the name is the published name. That city's as-of date is the TIRZ layer's own dataLastEditDate. Houston TIRZ polygons are the COHGIS TIRZ layer, which stores a name and not a number. The number is joined from the Mayor's Office of Economic Development roster. The FY2026 adopted budget lists the same roster, records that TIRZ 4 Village Enclaves terminated on 31 December 2013, and records that TIRZ 28 Texas Medical Center was created on 14 December 2022. TIRZ 28 is not in the GIS file, so it is not on this map. One GIS polygon has a null name and ships with a null id rather than a guessed number. Any other unmatched name also keeps a null id. Houston's as-of date is the date printed in the layer description, which is the boundary file's own date. The map label is TIRZ plus the number, then the name. Both kinds are one FeatureCollection per city, Opportunity Zones first, then TIRZ, drawn as an outline overlay with no hue. Polygons are simplified and rounded to 4 decimals, and a ring that would collapse is kept. There is no city-limits coverage mask on this layer, because that mask would hide county Opportunity Zone tracts.

Caveat: These outlines are Opportunity Zones designated in 2018 (IRS Notice 2018-48, updated by Notice 2019-42), in effect through 31 December 2028, and city TIRZ boundaries. This map does not show tracts nominated for the 2027 round. Being inside a designated tract or a TIRZ is not a guarantee of any tax benefit or incentive. Houston's GIS file does not include Texas Medical Center (TIRZ 28).

Sources

San Antonio

Shipped · as of 11 Jun 2026 · Designated 2018; TIRZ boundaries as of 11 Jun 2026 · Census tract (Opportunity Zone) and TIRZ boundary · 45 features · COSA TIRZ San Antonio GeoJSON

Greater Houston

Shipped · as of 24 May 2023 · Designated 2018; TIRZ boundaries as of 24 May 2023 · Census tract (Opportunity Zone) and TIRZ boundary · 174 features · COH TIRZ Greater Houston GeoJSON

Zoning

A tenant can see whether the city's base district is commercial, office, industrial, mixed use, residential, or special.

Group: Rules & incentives

Method: San Antonio features come from the City of San Antonio COSA Zoning layer. Each polygon keeps the exact Base code. The family letter follows the base code when Base is present: SpecDistrict does not repaint it, and overlay districts are not painted. When Base is blank, the Zoning label is classified; if that is also blank, SpecDistrict is classified. R-*, RM-*, MF-*, RE, and RP are Residential (R). C-1, C-2, and C-3, including suffixes such as C-2NA, C-2P, and C-3R, plus NC, NC-, O-1, O-1.5, and O-2, are Commercial and office (C). OCL is not office. L, I-1, and I-2 are Industrial (I). MI-1 and MI-2 are Special and other (S), as are MH, DR, FR, RD, PUD, ED, AE, OCL, UZROW, and UNKNOWN. OCL and UZROW are not written as fills. OCL means outside the city limit, which the coverage mask explains. UZROW means unzoned right-of-way, so those street polygons are omitted. Both still classify as S. Exact D and UD, and codes starting with MXD, IDZ, TOD, or FBZ, are Mixed use (M). DR is Development Reserve, not Downtown D. The GIS spells the form-based district FBZ (for example FBZ T4 and FBZ T6-2). FBZD in the design spec is that same family, and the feature keeps the GIS spelling. Anything unrecognized is S and the source spelling is kept. No code is invented. Polygons are copied into every 0.025° cell the bounding box touches, inside the San Antonio map frame. The cell id is floor((lng+180)/0.025)_floor((lat+90)/0.025). A 0.05° cell cannot stay under 400 KB without deleting small districts: one downtown 0.05° cell is about 18,000 parcels and about 8 MB raw, and dissolving it still leaves shapes that fit 400 KB only by collapsing those lots. Cells at or under 400 KB ship as parcel polygons. A ring that would collapse under simplification is kept at the rounded original. A cell over 400 KB is clipped to the cell and dissolved with mapshaper on code, spec, letter, cat, and name, so different codes are not merged, then simplified the same way. featureCount counts written features, including a parcel listed in each cell its box touches. Coordinates are rounded to 5 decimals, or 4 after a dissolve. Houston is cut because the city has no zoning ordinance. The City of Houston land-use layer (appraisal-district use codes, COHGIS public domain, item 06b9106fb025429888d05f2602148a54) is existing use, not a legal district, so it is not drawn as zoning. HCAD parcels are not used. Deed restrictions have no citywide public GIS layer. A separate land-use layer would be an owner decision. The coverage polygon is the City of San Antonio boundary from COSABoundary, simplified, labeled San Antonio city limits. Incentive zones do not use a city-limits mask, because Opportunity Zone tracts extend into the county.

Caveat: Fills are the city's base zoning district on the as-of date. Overlay districts may also apply. Pending cases and specific use permits are not shown. Confirm the district with the city. The City of Houston has no zoning ordinance. Development follows Chapter 42 (subdivision rules) and private deed restrictions, which are recorded with the county clerk and are not mapped here.

Sources

  • City of San Antonio — Zoning (COSA zoning). City: San Antonio. License: City of San Antonio Open Data Policy: data is open and free to reuse, republish, or manipulate without restriction, including commercial use. Portal terms grant a non-exclusive, revocable, as-is license.. Retrieved 8 Oct 2026. City of San Antonio GIS / Planning and Community Development.

San Antonio

Shipped · as of 4 Oct 2026 · City GIS base districts · City of San Antonio base zoning district · 57140 features · COSA zoning Coverage: San Antonio city limits boundary. San Antonio chunked GeoJSON /layers/zoning/san-antonio/{cell}.geojson

Greater Houston

Houston has no zoning ordinance

Location facts for one address

Facts for one address are not part of the suite JSON. Location facts (/api/location-facts.json) accept ?building= (the geocode key) or ?suite= (a suite id). A building key that has not been computed returns the same not-yet-computed line as the suite page.