Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/vendor/mediawiki/at-ease/src/Functions.php on line 48
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/includes/exception/MWExceptionHandler.php on line 179
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/vendor/mediawiki/at-ease/src/Functions.php on line 48
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/includes/exception/MWExceptionHandler.php on line 179
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/vendor/mediawiki/at-ease/src/Functions.php on line 48
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/includes/exception/MWExceptionHandler.php on line 179
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/vendor/mediawiki/at-ease/src/Functions.php on line 48
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/includes/exception/MWExceptionHandler.php on line 179
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/vendor/mediawiki/at-ease/src/Functions.php on line 48
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/includes/exception/MWExceptionHandler.php on line 179
Deprecated: Return type of MediaWiki\Session\PHPSessionHandler::open($save_path, $session_name) should either be compatible with SessionHandlerInterface::open(string $path, string $name): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dogtaton/public_html/giswiki/includes/session/PHPSessionHandler.php on line 199
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/includes/exception/MWExceptionHandler.php on line 179
Deprecated: Return type of MediaWiki\Session\PHPSessionHandler::close() should either be compatible with SessionHandlerInterface::close(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dogtaton/public_html/giswiki/includes/session/PHPSessionHandler.php on line 214
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/includes/exception/MWExceptionHandler.php on line 179
Deprecated: Return type of MediaWiki\Session\PHPSessionHandler::read($id) should either be compatible with SessionHandlerInterface::read(string $id): string|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dogtaton/public_html/giswiki/includes/session/PHPSessionHandler.php on line 228
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/includes/exception/MWExceptionHandler.php on line 179
Deprecated: Return type of MediaWiki\Session\PHPSessionHandler::write($id, $dataStr) should either be compatible with SessionHandlerInterface::write(string $id, string $data): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dogtaton/public_html/giswiki/includes/session/PHPSessionHandler.php on line 256
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/includes/exception/MWExceptionHandler.php on line 179
Deprecated: Return type of MediaWiki\Session\PHPSessionHandler::destroy($id) should either be compatible with SessionHandlerInterface::destroy(string $id): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dogtaton/public_html/giswiki/includes/session/PHPSessionHandler.php on line 362
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/includes/exception/MWExceptionHandler.php on line 179
Deprecated: Return type of MediaWiki\Session\PHPSessionHandler::gc($maxlifetime) should either be compatible with SessionHandlerInterface::gc(int $max_lifetime): int|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dogtaton/public_html/giswiki/includes/session/PHPSessionHandler.php on line 383
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/includes/exception/MWExceptionHandler.php on line 179
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/vendor/mediawiki/at-ease/src/Functions.php on line 48
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/includes/exception/MWExceptionHandler.php on line 179
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/vendor/mediawiki/at-ease/src/Functions.php on line 48
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/includes/exception/MWExceptionHandler.php on line 179
Deprecated: Return type of Wikimedia\Rdbms\IResultWrapper::current() should either be compatible with Iterator::current(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dogtaton/public_html/giswiki/includes/libs/rdbms/database/resultwrapper/IResultWrapper.php on line 70
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/includes/exception/MWExceptionHandler.php on line 179
Deprecated: Return type of Wikimedia\Rdbms\IResultWrapper::next() should either be compatible with Iterator::next(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dogtaton/public_html/giswiki/includes/libs/rdbms/database/resultwrapper/IResultWrapper.php on line 80
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/includes/exception/MWExceptionHandler.php on line 179
Deprecated: Return type of Wikimedia\Rdbms\IResultWrapper::key() should either be compatible with Iterator::key(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dogtaton/public_html/giswiki/includes/libs/rdbms/database/resultwrapper/IResultWrapper.php on line 75
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/includes/exception/MWExceptionHandler.php on line 179
Deprecated: Return type of Wikimedia\Rdbms\ResultWrapper::valid() should either be compatible with Iterator::valid(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dogtaton/public_html/giswiki/includes/libs/rdbms/database/resultwrapper/ResultWrapper.php on line 117
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/includes/exception/MWExceptionHandler.php on line 179
Deprecated: Return type of Wikimedia\Rdbms\ResultWrapper::rewind() should either be compatible with Iterator::rewind(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dogtaton/public_html/giswiki/includes/libs/rdbms/database/resultwrapper/ResultWrapper.php on line 90
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/includes/exception/MWExceptionHandler.php on line 179
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/vendor/mediawiki/at-ease/src/Functions.php on line 48
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/includes/exception/MWExceptionHandler.php on line 179
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/vendor/mediawiki/at-ease/src/Functions.php on line 48
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/includes/exception/MWExceptionHandler.php on line 179
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/vendor/mediawiki/at-ease/src/Functions.php on line 48
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/includes/exception/MWExceptionHandler.php on line 179
Deprecated: Return type of MediaWiki\Session\Session::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dogtaton/public_html/giswiki/includes/session/Session.php on line 624
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/includes/exception/MWExceptionHandler.php on line 179
Deprecated: Return type of MediaWiki\Session\Session::current() should either be compatible with Iterator::current(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dogtaton/public_html/giswiki/includes/session/Session.php on line 629
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/includes/exception/MWExceptionHandler.php on line 179
Deprecated: Return type of MediaWiki\Session\Session::next() should either be compatible with Iterator::next(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dogtaton/public_html/giswiki/includes/session/Session.php on line 639
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/includes/exception/MWExceptionHandler.php on line 179
Deprecated: Return type of MediaWiki\Session\Session::key() should either be compatible with Iterator::key(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dogtaton/public_html/giswiki/includes/session/Session.php on line 634
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/includes/exception/MWExceptionHandler.php on line 179
Deprecated: Return type of MediaWiki\Session\Session::valid() should either be compatible with Iterator::valid(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dogtaton/public_html/giswiki/includes/session/Session.php on line 649
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/includes/exception/MWExceptionHandler.php on line 179
Deprecated: Return type of MediaWiki\Session\Session::rewind() should either be compatible with Iterator::rewind(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dogtaton/public_html/giswiki/includes/session/Session.php on line 644
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/includes/exception/MWExceptionHandler.php on line 179
Deprecated: Return type of MediaWiki\Session\Session::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dogtaton/public_html/giswiki/includes/session/Session.php on line 659
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/includes/exception/MWExceptionHandler.php on line 179
Deprecated: Return type of & MediaWiki\Session\Session::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dogtaton/public_html/giswiki/includes/session/Session.php on line 672
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/includes/exception/MWExceptionHandler.php on line 179
Deprecated: Return type of MediaWiki\Session\Session::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dogtaton/public_html/giswiki/includes/session/Session.php on line 681
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/includes/exception/MWExceptionHandler.php on line 179
Deprecated: Return type of MediaWiki\Session\Session::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dogtaton/public_html/giswiki/includes/session/Session.php on line 685
Deprecated: ApiBase::makeMessage(): Implicitly marking parameter $params as nullable is deprecated, the explicit nullable type must be used instead in /home/dogtaton/public_html/giswiki/includes/api/ApiBase.php on line 1701
Deprecated: ApiBase::errorArrayToStatus(): Implicitly marking parameter $user as nullable is deprecated, the explicit nullable type must be used instead in /home/dogtaton/public_html/giswiki/includes/api/ApiBase.php on line 1726
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/includes/exception/MWExceptionHandler.php on line 179
Deprecated: Creation of dynamic property ApiMain::$mCommit is deprecated in /home/dogtaton/public_html/giswiki/includes/api/ApiMain.php on line 300 Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/includes/exception/MWExceptionHandler.php on line 179
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/vendor/mediawiki/at-ease/src/Functions.php on line 48
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/includes/exception/MWExceptionHandler.php on line 179
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/vendor/mediawiki/at-ease/src/Functions.php on line 48
http://dogtato.net/giswiki/api.php?action=feedcontributions&feedformat=atom&user=63.249.36.73GIS Wiki - User contributions [en]2026-04-16T07:58:36ZUser contributionsMediaWiki 1.30.0 Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/includes/exception/MWExceptionHandler.php on line 179
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/vendor/mediawiki/at-ease/src/Functions.php on line 48
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/includes/exception/MWExceptionHandler.php on line 179
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/vendor/mediawiki/at-ease/src/Functions.php on line 48
http://dogtato.net/giswiki/index.php?title=Redrawing_Parcels&diff=382Redrawing Parcels2014-09-30T11:00:25Z<p>63.249.36.73: Created page with "When redrawing parcels, it's ideal to redraw the full block unless measurements and/or visual comparison show that the parcels of the block already match their documented form..."</p>
<hr />
<div>When redrawing parcels, it's ideal to redraw the full block unless measurements and/or visual comparison show that the parcels of the block already match their documented form. If DATE_EDITE is older than 2013 then you can most likely improve it significantly by doing a redraw of the full block at once.<br />
<br />
==Plats==<br />
If ABSTORSUBN doesn't start with an 'A', check the ABSTORSU_1 field and look that up in the Utilities laserfiche under Design > Plats. Start with the newest and work backwards until you've entered the full subdivision.<br />
<br />
It's convenient to enter as large of shapes as possible first, such as entering the plat or a block boundary as a temporary parcel. then you can draw in all the parcels more easily.<br />
<br />
When you enter a full circuit in the traverse tool you can check the "closed loop" box and then check the mismatch, which is useful for checking if you misentered any numbers. If the numbers are small (less than .01 feet is good, higher is fine after checking for mistakes) click the adjust button and hit ok so that it will adjust all of the metes so that the start and end point match. This feature only works if you create the whole thing with the traverse tool, which is sometimes an issue, but it's very useful for catching data entry errors.<br />
<br />
==Deeds==<br />
For parcels with an abstract for their subdivision, do a property search on dcad's website using PROP_ID, view the details, then hit end to scroll to the bottom where there is usually a Deed section. Use the newest<br />
<br />
Go to the county clerk's document search site, which is not easy to find since it has no domain.<br />
<br />
===Document Number===<br />
Ex: "2014-92284"<br />
Select "Document Number" from the second dropdown, enter "92284" and search, then click the result from year 2014.<br />
<br />
===Volume and Page===<br />
Ex: "1034-678"<br />
Select "Volume/Page" from the second dropdown, enter "1034" in the first box, "678" in the second, search, and there's usually just one result to click<br />
<br />
Then you have to click the "View Image" tab above the document info on the right. The metes and bounds of the tract are usually referred to as Exhibit A and on the second to last page.<br />
<br />
==Fitting Everything together==<br />
Use your most accurate parcel[s] in the block as a base. A good metric is parcels from plats that had gps coordinates, then by age. I don't have a great solution for keeping track of age, so it's good to fit things together as you go so you remember which parcel was from a barely readable 1972 deed and which was from the crisp 2006 deed.<br />
<br />
The first step is to rotate two parcels or parcel groups to correct for the difference in their orientation. When one document says "N 88-49-50 E" and another describes the same segment as "N 87-56-14 E", you'll need to rotate one. There is an excel spreadsheet set up as a [[Rotation calculator]]<br />
<br />
Then you have to start fudging things together. Again, favor new over old and split some differences until you've got a sparkly mass.<br />
<br />
Now symbolize the parcels as just a thin black outline and turn off all other layers. This will let you see where you have mismatched vertices on boundaries between parcels. These lines will appear thicker in places because they will alias differently due to not being perfectly identical. Add and adjust vertices until it looks clean.<br />
<br />
You should have been saving throughout. Now commit the changes, then export the block and send it to DCAD so they can benefit from your improved parcel geometry. There are several good reasons to do this last step.<br />
<br />
==General Notes==<br />
*The older the measurements, the more they need to be corrected by rotating them counterclockwise. Newish stuff often needs rotating a little too.<br />
*Sometimes GPS coordinates will be wildly wrong. Coordinates from 2013 and later seem to be accurate</div>63.249.36.73 Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/includes/exception/MWExceptionHandler.php on line 179
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/vendor/mediawiki/at-ease/src/Functions.php on line 48
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/includes/exception/MWExceptionHandler.php on line 179
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/vendor/mediawiki/at-ease/src/Functions.php on line 48
http://dogtato.net/giswiki/index.php?title=Rotation_Calculator&diff=381Rotation Calculator2014-09-30T10:55:46Z<p>63.249.36.73: Redirected page to Rotation calculator</p>
<hr />
<div>#REDIRECT [[Rotation calculator]]</div>63.249.36.73 Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/includes/exception/MWExceptionHandler.php on line 179
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/vendor/mediawiki/at-ease/src/Functions.php on line 48
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/includes/exception/MWExceptionHandler.php on line 179
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/vendor/mediawiki/at-ease/src/Functions.php on line 48
http://dogtato.net/giswiki/index.php?title=Parcels&diff=380Parcels2014-09-30T10:09:45Z<p>63.249.36.73: </p>
<hr />
<div>{{Layer|Parcels|gif|Planning|-}}The parcel layer is maintained independently of the [[CountyParcels]] layer. Many of the attributes come from CountyParcel ([[DCAD]]). Along with [[Centerline]] it's the backbone of the GIS data. It has some extraneous fields.<br />
==Attributes==<br />
*Fields pulled from DCAD<br />
** <b>PROP_ID, PROPERTY</b>: Unique identifier, PROPERTY has the letter 'R' prepended along with 0's to pad out shorter ID's. [[Field Calculator#Parcels/CountyParcels PROPERTY (vb)|How to calculate PROPERTY]]<br />
** <b>SITUS_NUM, SITUS_PREF, SITUS_STRE, SITUS_SUFI, SITUS_ADDR</b>: Address information<br />
** <b>OWNER_NAME, ADDRESS_1, ADDRESS_2, ADDR3, CITY, STATE, ZIP</b>: Owner information<br />
** <b>LEGAL_DESC, PHASE, BLOCK, LOT</b>: Legal description<br />
** <b>ABSTORSUBN, ABSTORSU_1, SUBNAME</b>: Abstract/Subdivision information<br />
** <b>TOTALLAND, T_IMPROVE, TOTAL_PROP, APPRAISED_, ROLL_ASSD</b>: Property values<br />
** <b>YEARBUILT</b>: Year that current structure on the property was built<br />
** <b>PROP_TYPE, STATE_CD, CD_DESCRIP, LAND_TYPE, LANDTYPE</b>: Descriptions of the land and it's usage<br />
** <b>LIVINGAREA, LAND_SQFT</b>: Indoor and total?outdoor? area<br />
** <b>EXEMPTION</b>: Tax status<br />
*City Fields<br />
** <b>LO_ADDRESS, HI_ADDRESS, STDIR, STNAME, STTYPE, SUITE, FULNAME, COD_SITUS, SITUS, SITE_CITY, SITE_STATE, SITE_ZIP</b>: Address information<br />
** <b>ABST, ABSTNAMES</b>: Abstract number and name<br />
** <b>COUNCIL_DI, ESN1, FIRE_DIST</b>: Voter and emergency services districts<br />
** <b>STCODE</b>: pulled from centerline the parcel is addressed off of<br />
** <b>FACILITYID</b>: Identifier. [[Field Calculator#Parcels FACILITYID (python)|How to calculate for new fields.]]<br />
** <b>PLATTED</b>: Y or N<br />
** <b>CNTY_NAME</b>: Name of the city, or region of the city<br />
* other<br />
** <b>OBJECTID_1, OBJECTID</b>: database identifiers<br />
** <b>CNTY_ZIPS</b>: Matches SITE_ZIP more closely than ZIP (owner addr). Not sure why<br />
** <b>PIDNOTE, SUBDIV, METER</b>: Mysterious<br />
** <b>SUP</b>: Unused<br />
<br />
==Improving feature geometry==<br />
[[Redrawing Parcels]]<br />
<br />
==Potential Table Improvements==<br />
*<b>ADDRESS_1</b> -> <b>ADDR_LINE1</b> to match CountyParcels so that these fields will transfer when copy and pasting features from that layer<br />
*<b>ADDRESS_2</b> -> <b>ADDR_LINE2</b> same reason<br />
*<b>ADDR3</b> -> <b>ADDR_LINE3</b> same reason, plus consistency<br />
*<b>YEARBUILT</b> -> <b>YR_BLT</b> same reason, though <b>YEARBUILT</b> is a better name<br />
*<b>CNTY_ZIPS</b> is redundant with <b>SITE_ZIP</b>. One is likely a more outdated version of the other<br />
*<b>OBJECTID</b>: supplanted by <b>OBJECTID_1</b>, but the best option is to delete both fields before reloading, then <b>OBJECTID</b> will be recreated<br />
*<b>SUP</b>: since unused, remove<br />
*<b>CNTY_NAME</b>: unclear utility<br />
*<b>SUITE</b> remove since a parcel with a suite is likely to have multiple suites, and fine grain addressing is now done with [[City_Addresses]] instead of with cutouts of the parcel<br />
*<b>COD_SITUS</b> and <b>SITUS</b> are duplicates<br />
*<b>APPRAISED_</b> -> <b>APPRAISED</b> to match CountyParcels and just because<br />
[[Category:Planning]]</div>63.249.36.73 Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/includes/exception/MWExceptionHandler.php on line 179
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/vendor/mediawiki/at-ease/src/Functions.php on line 48
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/includes/exception/MWExceptionHandler.php on line 179
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/vendor/mediawiki/at-ease/src/Functions.php on line 48
http://dogtato.net/giswiki/index.php?title=Parcels&diff=379Parcels2014-09-30T10:07:39Z<p>63.249.36.73: /* Potential Improvements */</p>
<hr />
<div>{{Layer|Parcels|gif|Planning|-}}The parcel layer is maintained independently of the [[CountyParcels]] layer. Many of the attributes come from CountyParcel ([[DCAD]]). Along with [[Centerline]] it's the backbone of the GIS data. It has some extraneous fields.<br />
==Attributes==<br />
*Fields pulled from DCAD<br />
** <b>PROP_ID, PROPERTY</b>: Unique identifier, PROPERTY has the letter 'R' prepended along with 0's to pad out shorter ID's. [[Field Calculator#Parcels/CountyParcels PROPERTY (vb)|How to calculate PROPERTY]]<br />
** <b>SITUS_NUM, SITUS_PREF, SITUS_STRE, SITUS_SUFI, SITUS_ADDR</b>: Address information<br />
** <b>OWNER_NAME, ADDRESS_1, ADDRESS_2, ADDR3, CITY, STATE, ZIP</b>: Owner information<br />
** <b>LEGAL_DESC, PHASE, BLOCK, LOT</b>: Legal description<br />
** <b>ABSTORSUBN, ABSTORSU_1, SUBNAME</b>: Abstract/Subdivision information<br />
** <b>TOTALLAND, T_IMPROVE, TOTAL_PROP, APPRAISED_, ROLL_ASSD</b>: Property values<br />
** <b>YEARBUILT</b>: Year that current structure on the property was built<br />
** <b>PROP_TYPE, STATE_CD, CD_DESCRIP, LAND_TYPE, LANDTYPE</b>: Descriptions of the land and it's usage<br />
** <b>LIVINGAREA, LAND_SQFT</b>: Indoor and total?outdoor? area<br />
** <b>EXEMPTION</b>: Tax status<br />
*City Fields<br />
** <b>LO_ADDRESS, HI_ADDRESS, STDIR, STNAME, STTYPE, SUITE, FULNAME, COD_SITUS, SITUS, SITE_CITY, SITE_STATE, SITE_ZIP</b>: Address information<br />
** <b>ABST, ABSTNAMES</b>: Abstract number and name<br />
** <b>COUNCIL_DI, ESN1, FIRE_DIST</b>: Voter and emergency services districts<br />
** <b>STCODE</b>: pulled from centerline the parcel is addressed off of<br />
** <b>FACILITYID</b>: Identifier. [[Field Calculator#Parcels FACILITYID (python)|How to calculate for new fields.]]<br />
** <b>PLATTED</b>: Y or N<br />
** <b>CNTY_NAME</b>: Name of the city, or region of the city<br />
* other<br />
** <b>OBJECTID_1, OBJECTID</b>: database identifiers<br />
** <b>CNTY_ZIPS</b>: Matches SITE_ZIP more closely than ZIP (owner addr). Not sure why<br />
** <b>PIDNOTE, SUBDIV, METER</b>: Mysterious<br />
** <b>SUP</b>: Unused<br />
<br />
==Potential Improvements==<br />
*<b>ADDRESS_1</b> -> <b>ADDR_LINE1</b> to match CountyParcels so that these fields will transfer when copy and pasting features from that layer<br />
*<b>ADDRESS_2</b> -> <b>ADDR_LINE2</b> same reason<br />
*<b>ADDR3</b> -> <b>ADDR_LINE3</b> same reason, plus consistency<br />
*<b>YEARBUILT</b> -> <b>YR_BLT</b> same reason, though <b>YEARBUILT</b> is a better name<br />
*<b>CNTY_ZIPS</b> is redundant with <b>SITE_ZIP</b>. One is likely a more outdated version of the other<br />
*<b>OBJECTID</b>: supplanted by <b>OBJECTID_1</b>, but the best option is to delete both fields before reloading, then <b>OBJECTID</b> will be recreated<br />
*<b>SUP</b>: since unused, remove<br />
*<b>CNTY_NAME</b>: unclear utility<br />
*<b>SUITE</b> remove since a parcel with a suite is likely to have multiple suites, and fine grain addressing is now done with [[City_Addresses]] instead of with cutouts of the parcel<br />
*<b>COD_SITUS</b> and <b>SITUS</b> are duplicates<br />
*<b>APPRAISED_</b> -> <b>APPRAISED</b> to match CountyParcels and just because<br />
[[Category:Planning]]</div>63.249.36.73 Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/includes/exception/MWExceptionHandler.php on line 179
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/vendor/mediawiki/at-ease/src/Functions.php on line 48
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/includes/exception/MWExceptionHandler.php on line 179
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/vendor/mediawiki/at-ease/src/Functions.php on line 48
http://dogtato.net/giswiki/index.php?title=Parcels&diff=378Parcels2014-09-30T10:06:37Z<p>63.249.36.73: </p>
<hr />
<div>{{Layer|Parcels|gif|Planning|-}}The parcel layer is maintained independently of the [[CountyParcels]] layer. Many of the attributes come from CountyParcel ([[DCAD]]). Along with [[Centerline]] it's the backbone of the GIS data. It has some extraneous fields.<br />
==Attributes==<br />
*Fields pulled from DCAD<br />
** <b>PROP_ID, PROPERTY</b>: Unique identifier, PROPERTY has the letter 'R' prepended along with 0's to pad out shorter ID's. [[Field Calculator#Parcels/CountyParcels PROPERTY (vb)|How to calculate PROPERTY]]<br />
** <b>SITUS_NUM, SITUS_PREF, SITUS_STRE, SITUS_SUFI, SITUS_ADDR</b>: Address information<br />
** <b>OWNER_NAME, ADDRESS_1, ADDRESS_2, ADDR3, CITY, STATE, ZIP</b>: Owner information<br />
** <b>LEGAL_DESC, PHASE, BLOCK, LOT</b>: Legal description<br />
** <b>ABSTORSUBN, ABSTORSU_1, SUBNAME</b>: Abstract/Subdivision information<br />
** <b>TOTALLAND, T_IMPROVE, TOTAL_PROP, APPRAISED_, ROLL_ASSD</b>: Property values<br />
** <b>YEARBUILT</b>: Year that current structure on the property was built<br />
** <b>PROP_TYPE, STATE_CD, CD_DESCRIP, LAND_TYPE, LANDTYPE</b>: Descriptions of the land and it's usage<br />
** <b>LIVINGAREA, LAND_SQFT</b>: Indoor and total?outdoor? area<br />
** <b>EXEMPTION</b>: Tax status<br />
*City Fields<br />
** <b>LO_ADDRESS, HI_ADDRESS, STDIR, STNAME, STTYPE, SUITE, FULNAME, COD_SITUS, SITUS, SITE_CITY, SITE_STATE, SITE_ZIP</b>: Address information<br />
** <b>ABST, ABSTNAMES</b>: Abstract number and name<br />
** <b>COUNCIL_DI, ESN1, FIRE_DIST</b>: Voter and emergency services districts<br />
** <b>STCODE</b>: pulled from centerline the parcel is addressed off of<br />
** <b>FACILITYID</b>: Identifier. [[Field Calculator#Parcels FACILITYID (python)|How to calculate for new fields.]]<br />
** <b>PLATTED</b>: Y or N<br />
** <b>CNTY_NAME</b>: Name of the city, or region of the city<br />
* other<br />
** <b>OBJECTID_1, OBJECTID</b>: database identifiers<br />
** <b>CNTY_ZIPS</b>: Matches SITE_ZIP more closely than ZIP (owner addr). Not sure why<br />
** <b>PIDNOTE, SUBDIV, METER</b>: Mysterious<br />
** <b>SUP</b>: Unused<br />
<br />
==Potential Improvements==<br />
*<b>ADDRESS_1</b> -> <b>ADDR_LINE1</b> to match CountyParcels so that these fields will transfer when copy and pasting features from that layer<br />
*<b>ADDRESS_2</b> -> <b>ADDR_LINE2</b> same reason<br />
*<b>ADDR3</b> -> <b>ADDR_LINE3</b> same reason, plus consistency<br />
*<b>YEARBUILT</b> -> <b>YR_BLT</b> same reason, though <b>YEARBUILT</b> is a better name<br />
*<b>CNTY_ZIPS</b> is redundant with <b>SITE_ZIP</b><br />
*<b>OBJECTID</b>: supplanted by <b>OBJECTID_1</b>, but the best option is to delete both fields before reloading, then <b>OBJECTID</b> will be recreated<br />
*<b>SUP</b>: since unused, remove<br />
*<b>CNTY_NAME</b>: unclear utility<br />
*<b>SUITE</b> remove since a parcel with a suite is likely to have multiple suites, and fine grain addressing is now done with [[City_Addresses]] instead of with cutouts of the parcel<br />
*<b>COD_SITUS</b> and <b>SITUS</b> are duplicates<br />
*<b>APPRAISED_</b> -> <b>APPRAISED</b> to match CountyParcels and just because<br />
[[Category:Planning]]</div>63.249.36.73 Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/includes/exception/MWExceptionHandler.php on line 179
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/vendor/mediawiki/at-ease/src/Functions.php on line 48
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/includes/exception/MWExceptionHandler.php on line 179
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/vendor/mediawiki/at-ease/src/Functions.php on line 48
http://dogtato.net/giswiki/index.php?title=Parcels&diff=377Parcels2014-09-30T10:05:52Z<p>63.249.36.73: /* Needed Changes */</p>
<hr />
<div>{{Layer|Parcels|gif|Planning|-}}The parcel layer is maintained independently of the [[CountyParcels]] layer. Many of the attributes come from CountyParcel ([[DCAD]]). Along with [[Centerline]] it's the backbone of the GIS data. It has some extraneous fields.<br />
==Attributes==<br />
*Fields pulled from DCAD<br />
** <b>PROP_ID, PROPERTY</b>: Unique identifier, PROPERTY has the letter 'R' prepended along with 0's to pad out shorter ID's. [[Field Calculator#Parcels/CountyParcels PROPERTY (vb)|How to calculate PROPERTY]]<br />
** <b>SITUS_NUM, SITUS_PREF, SITUS_STRE, SITUS_SUFI, SITUS_ADDR</b>: Address information<br />
** <b>OWNER_NAME, ADDRESS_1, ADDRESS_2, ADDR3, CITY, STATE, ZIP</b>: Owner information<br />
** <b>LEGAL_DESC, PHASE, BLOCK, LOT</b>: Legal description<br />
** <b>ABSTORSUBN, ABSTORSU_1, SUBNAME</b>: Abstract/Subdivision information<br />
** <b>TOTALLAND, T_IMPROVE, TOTAL_PROP, APPRAISED_, ROLL_ASSD</b>: Property values<br />
** <b>YEARBUILT</b>: Year that current structure on the property was built<br />
** <b>PROP_TYPE, STATE_CD, CD_DESCRIP, LAND_TYPE, LANDTYPE</b>: Descriptions of the land and it's usage<br />
** <b>LIVINGAREA, LAND_SQFT</b>: Indoor and total?outdoor? area<br />
** <b>EXEMPTION</b>: Tax status<br />
*City Fields<br />
** <b>LO_ADDRESS, HI_ADDRESS, STDIR, STNAME, STTYPE, SUITE, FULNAME, COD_SITUS, SITUS, SITE_CITY, SITE_STATE, SITE_ZIP</b>: Address information<br />
** <b>ABST, ABSTNAMES</b>: Abstract number and name<br />
** <b>COUNCIL_DI, ESN1, FIRE_DIST</b>: Voter and emergency services districts<br />
** <b>STCODE</b>: pulled from centerline the parcel is addressed off of<br />
** <b>FACILITYID</b>: Identifier. [[Field Calculator#Parcels FACILITYID (python)|How to calculate for new fields.]]<br />
** <b>PLATTED</b>: Y or N<br />
** <b>CNTY_NAME</b>: Name of the city, or region of the city<br />
* other<br />
** <b>OBJECTID_1, OBJECTID</b>: database identifiers<br />
** <b>CNTY_ZIPS</b>: Matches SITE_ZIP more closely than ZIP (owner addr). Not sure why<br />
** <b>PIDNOTE, SUBDIV, METER</b>: Mysterious<br />
** <b>SUP</b>: Unused<br />
<br />
==Potential Improvements==<br />
*<b>ADDRESS_1</b> -> <b>ADDR_LINE1</b> to match CountyParcels so that these fields will transfer when copy and pasting features from that layer<br />
*<b>ADDRESS_2</b> -> <b>ADDR_LINE2</b> same reason<br />
*<b>ADDR3</b> -> <b>ADDR_LINE3</b> same reason, plus consistency<br />
*<b>YEARBUILT</b> -> <b>YR_BLT</b> same reason, though <b>YEARBUILT</b> is a better name<br />
*<b>CNTY_ZIPS</b> is redundant with <b>SITE_ZIP</b><br />
*<b>OBJECTID</b>: supplanted by <b>OBJECTID_1</b>, but the best option is to delete both fields before reloading, then <b>OBJECTID</b> will be recreated<br />
*<b>SUP</b>: unused<br />
*<b>CNTY_NAME</b>: unclear utility<br />
*<b>SUITE</b> remove since a parcel with a suite is likely to have multiple suites, and fine grain addressing is now done with [[City_Addresses]] instead of with cutouts of the parcel<br />
*<b>COD_SITUS</b> and <b>SITUS</b> are duplicates<br />
*<b>APPRAISED_</b> -> <b>APPRAISED</b> to match CountyParcels and just because<br />
[[Category:Planning]]</div>63.249.36.73 Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/includes/exception/MWExceptionHandler.php on line 179
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/vendor/mediawiki/at-ease/src/Functions.php on line 48
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/includes/exception/MWExceptionHandler.php on line 179
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/vendor/mediawiki/at-ease/src/Functions.php on line 48
http://dogtato.net/giswiki/index.php?title=Rotation_calculator&diff=376Rotation calculator2014-09-30T09:56:22Z<p>63.249.36.73: </p>
<hr />
<div>This is a spreadsheet that's useful for calculating the angle difference between two bearings. This is particularly useful when redrawing parcels and rotating parcels from different plats/deeds to fit together.<br />
<br />
=Location=<br />
S:Technology Services/Chad/various spreadsheets<br />
soon available for download<br />
<br />
=A good and thorough workflow=<br />
#Select and "start editing" the shape you want to rotate<br />
#Drag a box to select all the vertices (or open the vertex list, click the number area of a vertex, hit ctrl+a, then check one of the boxes)<br />
#Drag a vertex to its counterpart on the feature you're matching<br />
#Switch to the "create feature" tool for either a line or polygon class<br />
#Add a vertex on the matched corner<br />
#Bring the excel spreadsheet in to focus<br />
#In arcmap, mouse over a different shared vertex on the feature you'll rotate, which is still selected<br />
#Enter the bearing from the status bar in to the spreadsheet<br />
#Mouse over the counterpart to the second vertex<br />
#Enter the second bearing<br />
#Select the rotate tool in arcmap<br />
#Hit ctrl+z to undo adding the vertex<br />
#Hit 'a' to bring up the angle entry for the rotate tool<br />
#Enter the numbers from the highlighted row, with dashes between them<br />
#Hit enter<br />
#Edit and reselect all the vertices and move the vertex so it's coincident again<br />
#Adjust other vertices as needed, which is likely<br />
<br />
=Tips=<br />
*The negative sign is in the field in front of the first number, so don't miss it<br />
*Choose an initial vertex that is part of a good long common line, if possible<br />
<br />
[[Category:Scripts]]</div>63.249.36.73 Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/includes/exception/MWExceptionHandler.php on line 179
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/vendor/mediawiki/at-ease/src/Functions.php on line 48
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/includes/exception/MWExceptionHandler.php on line 179
Deprecated: Constant E_STRICT is deprecated in /home/dogtaton/public_html/giswiki/vendor/mediawiki/at-ease/src/Functions.php on line 48
http://dogtato.net/giswiki/index.php?title=Rotation_calculator&diff=375Rotation calculator2014-09-30T09:39:37Z<p>63.249.36.73: Created page with "This is a spreadsheet that's useful for calculating the angle difference between two bearings. This is particularly useful when redrawing parcels and rotating parcels from dif..."</p>
<hr />
<div>This is a spreadsheet that's useful for calculating the angle difference between two bearings. This is particularly useful when redrawing parcels and rotating parcels from different plats/deeds to fit together.<br />
<br />
Here's a good workflow:<br />
"start editing" one of the shapes<br />
select all the vertices<br />
drag one vertex to its counterpart on the feature you're matching<br />
switch to the "create feature" tool for either a line or polygon class<br />
add a vertex on the matched corner<br />
bring the excel spreadsheet in to focus<br />
in arcmap, mouse over a different shared vertex on the feature you'll rotate<br />
enter the letters/numbers from the status bar in to the spreadsheet<br />
mouse over the counterpart to the second vertex<br />
enter the second row of letters/numbers<br />
select the rotate tool in arcmap<br />
hit ctrl-z to undo adding the vertex<br />
hit 'a' to bring up the angle entry for the rotate tool<br />
enter the numbers from the highlighted row, with dashes between them<br />
the negative sign is in the field in front of the first number, so don't miss it<br />
<br />
The file is stored in S:Technology Services/Chad/various spreadsheets<br />
probably</div>63.249.36.73