Tiller parcel coordinates & boundary files
Retrieved October 8, 2026 from Douglas County Oregon public GIS. The 31 requested identifiers came from https://tillywood.net/zoning/ . Exact PROP_ID matching found 28 property-account records representing 26 distinct TAXIDs. M87036 is separately verified as a manufactured-home account on the ranch tax lot. Two identifiers remain unresolved.
Coordinates are approximate area-weighted centroids of county GIS geometry in WGS84 decimal degrees. They are not surveyed monuments, drilling locations, building coordinates, or necessarily points inside irregular parcels. GeoJSON coordinates are longitude then latitude; the table displays latitude then longitude. Full source boundary coordinates are retained without simplification. County GIS requested output CRS was EPSG:4326; centroid calculation uses a local equirectangular plane centered at 43 N, 123 W. Six decimal places are display precision, not an accuracy claim.
Important reconciliation
- R17426 and R17442 share TAXID 30022400600 and identical geometry. Account acreages are 10 and 72.46 respectively; MTLACREAGE is 82.46. Do not count the two boundary files as separate survey areas.
- R18154 and R18170 share TAXID 300233BA00500 and identical geometry. Account acreages are 1.91 and 0.35; MTLACREAGE is 2.26.
- M87036 is a manufactured-home account linked by the assessor to 30-02W-24-00600. Its supplied file is explicitly an ASSOCIATED LAND BOUNDARY, identical to the ranch tax lot. The coordinate is that land geometry’s centroid, not the home’s position. No extra acreage is added.
- R143213 and R17850 were not found in either the county Parcels layer or Land Ownership Combined layer. No standalone coordinates or polygon are invented. Current R18186 has ACCT_ACREAGE 6.58, and current R17842 has 6.85. These are consistent with the website’s sums but do not prove legal consolidation or locate old subdivisions. Historical account crosswalks require assessor confirmation.
- R18122 currently reports 13.13 account acres, versus 13.3 on the supplied webpage.
- Acreage attributes are not interchangeable: ACCT_ACREAGE, MTLACREAGE and TotalAcreage are retained as county fields in matched-account files. TotalAcreage is not relabeled as a surveyed or independently measured acreage. Do not sum repeated tax-lot values.
Files and appropriate use on Mining PRO
UPload Parcel GeoSpatial Package on Mining PRO
Use survey_boundaries_unique_taxlots.geojson or .kml for the combined 26-tax-lot map without exact duplicate account polygons. These files preserve separate tax lots; they are not a dissolved or cadastral-certified survey. all_matched_accounts.geojson preserves all 28 matched accounts, including shared boundaries. Each matched ID has its own GeoJSON and KML. Two unresolved IDs have status text files only. The manufactured-home file has associated_land in its filename.
No ownership, mineral title, access permission, zoning approval, or deposit is certified. No data have been uploaded to Farmonaut. County GIS cautions that datasets differ in reliability and may not align exactly. Source feature metadata did not expose an editing date, so retrieval date is not a claim that every feature was updated that day. The assessor web interface blocked direct retrieval of the two unresolved accounts; independent county GIS searches returned no match. Oregon Forestry’s alternate layer did not support the attempted query.
Sources:
- County parcel layer: https://gis.co.douglas.or.us/server/rest/services/Parcel/Parcels/FeatureServer/0
- County GIS explanation: https://www.douglascountyor.gov/169/Geographic-Information-Systems-GIS
- Additional no-match check: https://gis.co.douglas.or.us/server/rest/services/Parcel/Land_Ownership_Parcels/MapServer/0
- Manufactured-home record: https://appraisal.douglascountyor.gov/Property-Detail/PropertyQuickRefID/M87036
Coordinate index
| Requested ID | Latitude | Longitude | County TAXID | Account acres | Files |
|---|---|---|---|---|---|
| R18186 | 42.929580 | -122.957221 | 300233BB00600 | 6.58 | GeoJSON / KML |
| R143213 | Unresolved | Unresolved | — | — | Status |
| R18162 | 42.928867 | -122.955023 | 300233BA00400 | 0.38 | GeoJSON / KML |
| R17682 | 42.928018 | -122.953733 | 300233BA00900 | 2.97 | GeoJSON / KML |
| R18146 | 42.927515 | -122.952618 | 30023300100 | 1.28 | GeoJSON / KML |
| R18114 | 42.927348 | -122.952064 | 300233A00600 | 0.65 | GeoJSON / KML |
| R18170 | 42.928667 | -122.955612 | 300233BA00500 | 0.35 | GeoJSON / KML |
| R18154 | 42.928667 | -122.955612 | 300233BA00500 | 1.91 | GeoJSON / KML |
| R18234 | 42.929093 | -122.957853 | 300233BB00900 | 0.81 | GeoJSON / KML |
| R18298 | 42.929819 | -122.961470 | 300233BB00400 | 0.76 | GeoJSON / KML |
| R17842 | 42.930406 | -122.962994 | 30023200100 | 6.85 | GeoJSON / KML |
| R17850 | Unresolved | Unresolved | — | — | Status |
| R17858 | 42.928399 | -122.963009 | 30023200200 | 5.51 | GeoJSON / KML |
| R18282 | 42.929743 | -122.962052 | 300233BB00300 | 0.08 | GeoJSON / KML |
| R18290 | 42.929732 | -122.961916 | 300233BB00301 | 0.01 | GeoJSON / KML |
| R18266 | 42.929898 | -122.962068 | 300233BB00202 | 0.09 | GeoJSON / KML |
| R18226 | 42.929433 | -122.959620 | 300233BB01100 | 1.22 | GeoJSON / KML |
| R18202 | 42.929238 | -122.958626 | 300233BB01000 | 1.29 | GeoJSON / KML |
| R17650 | 42.928711 | -122.954280 | 300233BA00300 | 0.57 | GeoJSON / KML |
| R17666 | 42.930125 | -122.952871 | 300233BA00100 | 5.46 | GeoJSON / KML |
| R17642 | 42.932927 | -122.954109 | 30022800600 | 54.2 | GeoJSON / KML |
| R18122 | 42.930314 | -122.955541 | 300233BA00200 | 13.13 | GeoJSON / KML |
| R18138 | 42.925794 | -122.957392 | 30023300200 | 78.72 | GeoJSON / KML |
| R18058 | 42.925317 | -122.951713 | 300233A00700 | 8.82 | GeoJSON / KML |
| R18194 | 42.928275 | -122.960118 | 300233BB01200 | 14.29 | GeoJSON / KML |
| R17658 | 42.927770 | -122.956647 | 300233BA00800 | 1.64 | GeoJSON / KML |
| R17826 | 42.929575 | -122.964630 | 30023200300 | 12.03 | GeoJSON / KML |
| R17674 | 42.933058 | -122.949254 | 30022800700 | 31 | GeoJSON / KML |
| R17426 | 42.955971 | -122.898253 | 30022400600 | 10 | GeoJSON / KML |
| M87036 | 42.955971 | -122.898253 | 30022400600 | — | GeoJSON / KML |
| R17442 | 42.955971 | -122.898253 | 30022400600 | 72.46 | GeoJSON / KML |
Per-account status
- R18186: Matched county property account
- R143213: No match in current queried county layers. R18186 now reports 6.58 acres; historical merger is unconfirmed.
- R18162: Matched county property account
- R17682: Matched county property account
- R18146: Matched county property account
- R18114: Matched county property account
- R18170: Matched county property account; shared tax-lot geometry with R18154
- R18154: Matched county property account; shared tax-lot geometry with R18170
- R18234: Matched county property account
- R18298: Matched county property account
- R17842: Matched county property account
- R17850: No match in current queried county layers. R17842 now reports 6.85 acres; historical merger is unconfirmed.
- R17858: Matched county property account
- R18282: Matched county property account
- R18290: Matched county property account
- R18266: Matched county property account
- R18226: Matched county property account
- R18202: Matched county property account
- R17650: Matched county property account
- R17666: Matched county property account
- R17642: Matched county property account
- R18122: Matched county property account
- R18138: Matched county property account
- R18058: Matched county property account
- R18194: Matched county property account
- R17658: Matched county property account
- R17826: Matched county property account
- R17674: Matched county property account
- R17426: Matched county property account; shared tax-lot geometry with R17442
- M87036: Associated land boundary only; manufactured-home account, not separate land or home location
- R17442: Matched county property account; shared tax-lot geometry with R17426
Tiller parcel coordinates and boundary files
County GIS retrieved October 8, 2026. 28 matched accounts, 26 unique tax lots, one associated manufactured-home account and two unresolved IDs.
Coordinates are approximate WGS84 parcel-geometry centroids, not surveyed points or building locations. Shared-account polygons must not be counted twice.
Methodology and limitations · Combined unique boundaries: GeoJSON / KML
| ID | Latitude | Longitude | TAXID | Account acres | Status | Files |
|---|---|---|---|---|---|---|
| R18186 | 42.92958 | -122.957221 | 300233BB00600 | 6.58 | Matched county property account | GeoJSON · KML |
| R143213 | — | — | — | — | No match in current queried county layers. R18186 now reports 6.58 acres; historical merger is unconfirmed. | No verified boundary |
| R18162 | 42.928867 | -122.955023 | 300233BA00400 | 0.38 | Matched county property account | GeoJSON · KML |
| R17682 | 42.928018 | -122.953733 | 300233BA00900 | 2.97 | Matched county property account | GeoJSON · KML |
| R18146 | 42.927515 | -122.952618 | 30023300100 | 1.28 | Matched county property account | GeoJSON · KML |
| R18114 | 42.927348 | -122.952064 | 300233A00600 | 0.65 | Matched county property account | GeoJSON · KML |
| R18170 | 42.928667 | -122.955612 | 300233BA00500 | 0.35 | Matched county property account; shared tax-lot geometry with R18154 | GeoJSON · KML |
| R18154 | 42.928667 | -122.955612 | 300233BA00500 | 1.91 | Matched county property account; shared tax-lot geometry with R18170 | GeoJSON · KML |
| R18234 | 42.929093 | -122.957853 | 300233BB00900 | 0.81 | Matched county property account | GeoJSON · KML |
| R18298 | 42.929819 | -122.96147 | 300233BB00400 | 0.76 | Matched county property account | GeoJSON · KML |
| R17842 | 42.930406 | -122.962994 | 30023200100 | 6.85 | Matched county property account | GeoJSON · KML |
| R17850 | — | — | — | — | No match in current queried county layers. R17842 now reports 6.85 acres; historical merger is unconfirmed. | No verified boundary |
| R17858 | 42.928399 | -122.963009 | 30023200200 | 5.51 | Matched county property account | GeoJSON · KML |
| R18282 | 42.929743 | -122.962052 | 300233BB00300 | 0.08 | Matched county property account | GeoJSON · KML |
| R18290 | 42.929732 | -122.961916 | 300233BB00301 | 0.01 | Matched county property account | GeoJSON · KML |
| R18266 | 42.929898 | -122.962068 | 300233BB00202 | 0.09 | Matched county property account | GeoJSON · KML |
| R18226 | 42.929433 | -122.95962 | 300233BB01100 | 1.22 | Matched county property account | GeoJSON · KML |
| R18202 | 42.929238 | -122.958626 | 300233BB01000 | 1.29 | Matched county property account | GeoJSON · KML |
| R17650 | 42.928711 | -122.95428 | 300233BA00300 | 0.57 | Matched county property account | GeoJSON · KML |
| R17666 | 42.930125 | -122.952871 | 300233BA00100 | 5.46 | Matched county property account | GeoJSON · KML |
| R17642 | 42.932927 | -122.954109 | 30022800600 | 54.2 | Matched county property account | GeoJSON · KML |
| R18122 | 42.930314 | -122.955541 | 300233BA00200 | 13.13 | Matched county property account | GeoJSON · KML |
| R18138 | 42.925794 | -122.957392 | 30023300200 | 78.72 | Matched county property account | GeoJSON · KML |
| R18058 | 42.925317 | -122.951713 | 300233A00700 | 8.82 | Matched county property account | GeoJSON · KML |
| R18194 | 42.928275 | -122.960118 | 300233BB01200 | 14.29 | Matched county property account | GeoJSON · KML |
| R17658 | 42.92777 | -122.956647 | 300233BA00800 | 1.64 | Matched county property account | GeoJSON · KML |
| R17826 | 42.929575 | -122.96463 | 30023200300 | 12.03 | Matched county property account | GeoJSON · KML |
| R17674 | 42.933058 | -122.949254 | 30022800700 | 31 | Matched county property account | GeoJSON · KML |
| R17426 | 42.955971 | -122.898253 | 30022400600 | 10 | Matched county property account; shared tax-lot geometry with R17442 | GeoJSON · KML |
| M87036 | 42.955971 | -122.898253 | 30022400600 | — | Associated land boundary only; manufactured-home account, not separate land or home location | GeoJSON · KML |
| R17442 | 42.955971 | -122.898253 | 30022400600 | 72.46 | Matched county property account; shared tax-lot geometry with R17426 | GeoJSON · KML |