ESBD_File_349424_2024 Land Parcel Technical Specification.pdf
PDF 161 KB Posted
- Attached to
- 2024 Parcel Data
- Solicitation number
- 0000002124
- Issued by
- Dallas County, Texas
About this file
The document is a technical specification for a 2024 land parcel data collection contract opportunity issued by the Texas Geographic Information Office (TxGIO). The contract requires the delivery of parcel data, in Esri Shapefile and File Geodatabase formats, for all 254 Texas counties no later than July 17th, 2024. The data must conform to TxGIO's standardized schema, be projected in WGS 1984 (WKID 4326), and be delivered via AWS, hard drive, or other TxGIO-approved method. The parcel data must be organized into county-level and statewide File Geodatabases following specific naming conventions.
The related state and local contract opportunity is seeking bids for the 2024 parcel data collection and delivery. The contract is being advertised by the Texas Water Development Board, and bids should be submitted to the bid room and cc'd to the specified contacts. The contract has no further details provided regarding pricing, set-asides, incumbents, funding, or other salient information.
View the file
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
2024 Land Parcel Technical Specifica�on
1. Expected delivery date for 2024 Land Parcel Data
a. All land parcel data must be provided to TxGIO no later than 4:00 PM on July 17th, 2024.
2. Deliverable file type, file size and reference/name
a. The final product will be delivered via AWS, hard drive or other TxGIO approved method.
b. Deliverables are to be stored in a final folder named stratmap-[YEAR]-land-parcels labeled with the respec�ve year.
i. For example: stratmap-2023-land-parcels
c. Data will be delivered for each county as an Esri Shapefile and File Geodatabase (FGDB) stored in two folders named shp and fgdb, respec�vely. Addi�onally, a statewide FGDB should be delivered.
i. The shp folder will store all Esri Shapefiles and associated files for each county following this naming conven�on: stratmap[YR]-landparcels_[County FIPS Code]_[county name]_[date]
1. For example: stratmap23-landparcels_48001_anderson_202301
ii. The fgdb folder must contain a FGDB for each county following this naming conven�on: stratmap[YR]-landparcels_[County FIPS Code]_[county name]_[date].gdb
1. For example: stratmap23-landparcels_48001_anderson_202301.gdb
2. For each county fgdb, a feature class should be created following this naming conven�on: stratmap[YR]_landparcels_[County FIPS Code]_[county name]_[date]
a. For example:
stratmap23_landparcels_48001_anderson_202301
iii. The statewide FGDB will follow this naming conven�on: stratmap[YR]-landparcels_48.gdb
1. For example: stratmap23-landparcels_48.gdb
2. The statewide fgdb should have one feature class containing all Texas land parcel data following this naming conven�on:
stratmap[YR]_landparcels_statewide
a. For example: stratmap23_landparcels_statewide
d. All data is to be delivered using the projec�on WGS 1984; WKID 4326
e. Esri Shapefiles and FGDB feature classes must be submited in TxGIO’s standardized schema (Appendix A; attached below)
Appendix A: TNRIS Land Parcel Schema
Descriptive Name FieldName Field type Length Description
Unique ID PROP_ID STRING 10 Source unique identifier that can be joined with other datasets
Unique ID GEO_ID STRING 50 Source unique identifier that can be joined with other datasets
Owner name OWNER_NAME STRING 254 Owner of the parcel Owner name in care of NAME_CARE STRING 254 Owner of the parcel Legal area LEGAL_AREA DOUBLE 8 Legal area per deed. The non-rounded value.
Legal area units LGL_AREA_UNIT STRING 8 Legal area units per deed.
GIS area GIS_AREA DOUBLE 8 The area calculated within GIS GIS area units GIS_AREA_UNIT STRING 8 The area calculated units within GIS Legal description LEGAL_DESC STRING 254 Legal description from deed Land use STAT_LAND_USE STRING 5 Legal land use utilizing State of Texas land use codes Land use LOC_LAND_USE STRING 5 Legal land use utilizing local land use codes Land value LAND_VALUE DOUBLE 8 Current value of land Improvement value IMP_VALUE DOUBLE 8 Current value of improvements Market value MKT_VALUE DOUBLE 8 Current market value
Situs address SITUS_ADDR STRING 254 The main address of this property. Data concatenated into one field
Situs house number SITUS_NUM STRING 15 The house number of the main property Situs street directional or unit SITUS_STRE STRING 10 The street directional or unit of the main property Situs street name SITUS_ST_1 STRING 60 The street name of the main property Situs street info SITUS_ST_2 STRING 60 The street name info of the main property Situs city SITUS_CITY STRING 60 The city of the main property Situs state SITUS_STAT STRING 2 The state of the main property Situs zip SITUS_ZIP STRING 5 The zip of the main property
Mailing address MAIL_ADDR STRING 254 The mailing address for the owner of the property. Data concatenated into one field
Mailing street, directional and unit MAIL_LINE1 STRING 60 The mailing street, directional and unit Additional mailing info MAIL_LINE2 STRING 60 Additional mailing info Mailing city MAIL_CITY STRING 60 The mailing city Mailing state MAIL_STAT STRING 2 The mailing state Mailing zip MAIL_ZIP STRING 5 The mailing zip code
Appendix A: TNRIS Land Parcel Schema
Descriptive Name FieldName Field type Length Description
Source SOURCE STRING 100 The source of this data. For example, appraisal district or name of vendor
Date acquired DATE_ACQ INTEGER 4 The date TNRIS acquired this data.
County identifier FIPS STRING 5 County jurisdiction 5-digit FIPS code County name COUNTY STRING 60 County name Tax year TAX_YEAR INTEGER 2 The year of this dataset Year structure built YEAR_BUILT INTEGER 2 Year structure built
File details come from the government source that posted it. Updated .