Public ArcGIS MapServer endpoint for Ector County parcel data. URL, supported fields, and a working sample query, copy it, or open it directly in the UrbanKit parcel lookup tool.
This page is the endpoint reference. If you came here to find a specific property, the Ector County parcel search runs this same layer in your browser, no account and no API key.
Search Ector County parcelsHave a street address but not the parcel number? Find the parcel number by address.
https://gis11.cama.io/arcgis/rest/services/Ector/EctorCounty_Basemap/MapServer/0Field by field, whether any endpoint we index for Ector County answers it, and the evidence for each. We only call a field restricted when there is a stated reason we can cite. Everything else here is a fact about the services we index, not a claim about the law.
| Field | Status | Basis |
|---|---|---|
| APN | Answered | Documented in a field list on an endpoint we index. Not every row is populated. |
| Owner name | Answered | Documented in a field list on an endpoint we index. Not every row is populated. |
| Owner mailing address | Answered | Documented in a field list on an endpoint we index. Not every row is populated. |
| Site address | Not published | No endpoint we index for this county documents this field, so a query cannot ask for it. That is a fact about the services we index, not a legal restriction, and not a statement that the county holds no such record. Where to request it. |
| Geometry | Answered | Documented in a field list on an endpoint we index. Not every row is populated. |
| Land use | Answered | Documented in a field list on an endpoint we index. Not every row is populated. |
| Zoning | Not published | No endpoint we index for this county documents this field, so a query cannot ask for it. That is a fact about the services we index, not a legal restriction, and not a statement that the county holds no such record. Where to request it. |
PINParcel ID (Ector CAD PIN)strapAccount Number (strap)owner_nameOwner Nameowner_addrOwner Mailing Address (full line with city and state)curl -s 'https://gis11.cama.io/arcgis/rest/services/Ector/EctorCounty_Basemap/MapServer/0/query?where=UPPER(owner_name)%20LIKE%20UPPER('%25SMITH%25')%20AND%20CAST(conf_flg%20AS%20VARCHAR(255))%20NOT%20LIKE%20'%251%25'%20AND%20conf_flg%20IN%20(0)&outFields=PIN,owner_name,owner_addr,conf_flg&returnGeometry=false&f=json&resultRecordCount=10'https://gis11.cama.io/arcgis/rest/services/Ector/EctorCounty_Basemap/MapServer/0/query?where=UPPER(owner_name) LIKE UPPER('%SMITH%') AND CAST(conf_flg AS VARCHAR(255)) NOT LIKE '%1%' AND conf_flg IN (0)&outFields=PIN,owner_name,owner_addr,conf_flg&returnGeometry=false&f=json&resultRecordCount=10Open this URL in a browser tab to see the raw ArcGIS JSON response.
| Field name | Label | Searchable |
|---|---|---|
| PIN | Parcel ID (Ector CAD PIN) | YES |
| strap | Account Number (strap) | YES |
| owner_name | Owner Name | YES |
| owner_addr | Owner Mailing Address (full line with city and state) | YES |
| use_dscr | Land Use Description | NO |
| tax_val | Taxable Value | NO |
Ector County, Texas (county seat Odessa; FIPS 48135) was asked for through the free tools. The parcels are Ector County Appraisal District (Ector CAD) data, published as layer 0 ('ParcelFabric') of the Ector/EctorCounty_Basemap MapServer on gis11.cama.io, the server of the district's appraisal-software vendor (the layer is titled 'Ector County Appraisal District (public view)' on ArcGIS Online and the server's Ector folder also carries the district's aerials, features and thematic maps): 77,042 parcels on 2026-10-14, 76,779 of them with an owner (263 null). The owner is owner_name (the layer's display field); the owner mailing address is owner_addr, ONE line that includes the city and state (76,545 rows, 73,482 containing 'TX'); the parcel id is PIN (a formatted account number such as 5-5-5 digit groups, all 77,042 rows) with strap, dsp_strap and gis_parcel_id (76,779 rows each). NO SITUS COLUMN: the layer publishes no site-address field at all, so an address lookup cannot be answered from it; the registry therefore lists owner, mailing address and parcel id only, and an address-to-parcel lookup must go through a geocoded point query (inSR 4326 point intersect, verified: a point in downtown Odessa returned one parcel) rather than a text LIKE. CONFIDENTIAL OWNERS (Texas Tax Code §25.025): the layer carries a conf_flg column (smallint). Measured 2026-10-24, conf_flg = 0 on all 77,042 rows and no row carries a CONFIDENTIAL marker, so no value meaning 'confidential' has ever been observed here. The registry's confidentialFlag marker (conf_flg = 1) is a forward GUESS, not a measurement: it reads a future non-zero cell as flagged (the reader compares the cell as text, and a one-character value also matches inside the cell, so 10 or 21 would read as flagged too), at the cost of asserting a value Ector has never published. Re-measure before relying on it. In a where clause use AND CAST(conf_flg AS VARCHAR(255)) NOT LIKE '%1%' AND conf_flg IN (0), as the sampleQuery does: conf_flg is an integer, and the un-cast conf_flg NOT LIKE '%1%' answers with an ArcGIS error (code 400, inside an HTTP 200 response; 2026-10-25). The IN list is confidentialFlag.safeValues, the one distinct value the column holds (0, an integer, so it is not quoted; measured 2026-10-26 with returnDistinctValues): any other cell drops out, and the IN clause alone, or both clauses together, keep all 77,042 rows. 0 rows are flagged deleted. CORS answers Access-Control-Allow-Origin with the calling origin (checked with Origin https://urbankitstudio.com). maxRecordCount is only 1000 (pagination supported); the layer is Texas Central state plane (wkid 102739). Currency: the layer document carries no editing date; the newest dos_timestamp (date of sale) is 2026-08-05 and the newest last_rev_dt (last revision) is 2026-08-10. LICENSE AND DURABILITY: no license text; the host is a vendor server (ArcGIS 10.71) and not the district's own domain, so the URL can move when the vendor migrates the district; re-resolve from Ector CAD if the liveness probe flags it. The contact is Ector CAD. Verified 2026-10-14: a count, resultRecordCount=10 and an owner LIKE query (356 rows for %SMITH%) and a point query.
Ector County Appraisal District (Ector CAD), https://www.ectorcad.org/
Ector County's ParcelFabric layer exposes parcel identifiers (Parcel ID (Ector CAD PIN), Account Number (strap)) and owner names (Owner Name, Owner Mailing Address (full line with city and state)). Use it for owner-name lookups and PIN-keyed record pulls. 4 of 6 listed fields accept queries; the rest are returned on read but not indexed for search. Served as an ArcGIS MapServer layer, which supports query operations but not write operations; last verified 2026-10-25.
/query?where=…&outFields=*&f=jsonto the URL. The sample query above is a working example you can paste into a browser tab to see the raw JSON response.Counties publish parcel data through their own ArcGIS Server installations, each with its own schema. One county uses APN, another uses PIN, a third uses PARCEL_ID. Some expose owner names; others keep them on a separate assessor's portal. The searchable fields list above reflects what Ector County actually publishes, not what you might expect from a national standard (there isn't one).
For background, see What is an APN?
gis11.cama.io serves Ector County, Texas parcels over public ArcGIS REST, but, like most county servers, it may not send the CORS headers a browser needs for a cross-origin fetch. If a direct browser call fails, the layer still works from curl, Postman, or a server-side script; the UrbanKit parcel lookup tool proxies the request, so a search that succeeds there confirms the layer is genuinely public.
We last verified Ector County's MapServer layer on 2026-10-25. County GIS teams move services without notice, so if you hit a fresh 404, tell us and we'll re-check. Atlas entries are re-verified on a rolling basis.
Ector County's layer is hosted by the county on gis11.cama.io. Public ArcGIS endpoints rarely rate-limit individual reads, but gis11.cama.io can throttle heavy automated traffic at the host level. Page through results with resultOffset / resultRecordCount and request only the fields you need. There's no API key and no charge from the county.