GIS Wiki - User contributions [en]

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=Dogtaton GIS Wiki - User contributions [en] 2026-06-18T02:54:54Z User contributions MediaWiki 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=Printable_Maps&diff=530 Printable Maps 2015-09-11T19:17:46Z

Dogtaton: Created page with "Downloadable pdfs of large maps are available [http://www.cityofdenton.com/departments-services/utility-and-cip-engineering/printable-maps here]. To add or update maps on this..." <hr /> <div>Downloadable pdfs of large maps are available [http://www.cityofdenton.com/departments-services/utility-and-cip-engineering/printable-maps here]. To add or update maps on this page, you need to log in to [http://www.cityofdenton.com/admin the city's website admin page]. The login credentials are stored in a text file at S:\Technology Services\GIS\Chad\documents\website instructions for uploading maps.txt. ===Upload New Map=== Click the folder icon in the top bar to open Document Central, then scroll down and open Engineering Department » Maps. Click the Add Document button then follow the instructions. When it's uploaded, find the link to the document (will look like http://www.cityofdenton.com/home/showdocument?id=7285). Now click the page icon to go to the Pages section of the site. Expand Departments & Services » Engineering Services then click the arrow on the row for Printable Maps and select Edit (& View More Info). This will open the Printable Maps page. Mouse over the main body of the page and click the wrench in the upper right corner of the frame that appears. Copy and paste an existing link then click the copy and change the URL to the link from the previous step when you uploaded the map. Change the text of the link to the title of the new map and click Save, then click Save & Express Publish. ===Update Existing Map=== Go to Document Central » Engineering Department » Maps then click "<< Load More >>" until the map you want finally appears. Click the arrow on the right of the row for the map you want and select Update. Click the browse button and select the updated map file then click Save & Publish [[Category:Guides]]</div>

Dogtaton
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=Easement&diff=528 Easement 2015-09-09T18:24:03Z

Dogtaton: /* Drawing */ <hr /> <div>This is a replacement of the [[Easements|easements]] feature class. It stores all easements as well as right of way dedications. ==Fields== '''DateEdited''' - date of last edit to the feature '''EasementType1, EasementType2, EasementType3, EasementType4, EasementType5''' - Codes for the easement purposes such as Utility -> UTIL, Drainage -> DRAIN. To find all easements with a given type you need to select against all of the fields. '''Description''' - Full text of the easement types. An easement with types "ACCESS", "FIRE", and "UTIL" could have the description "Public Access, Firelane & Public Utility". '''DateFiled''' - Date the document was filed. '''DocumentNumber''' - City's code for the document, often looks like "A1234-567". The source and use of this code is an enigma, so I've been putting county clerk document numbers in this field. '''InstrumentNumber''' - County clerk's document number, good for finding the document. You also need to know the year since this number starts over each year '''Volume, Page''' - For looking up the document. For plats with a "cabinet"/page, Volume will be 'Cab X' '''Grantor, Grantee''' - The people giving up and receiving the easement rights. '''DocumentType''' - Type of document that describes the easement, e.g. EASEMENT, PLAT, WARRANTY DEED. ==Types== ===Common=== '''ABAND''' - Abandoned easements. These should be moved to the [[AbandonedEasements]] feature class, which is also in the [[:Category:RealEstate|RealEstate]] dataset. '''ACCESS''' - Sometimes attributed as INGRESS and EGRESS depending on how the legal document labels it. '''COMM''' - Communications. Not very common. '''DETEN''' - Water Detention, usually used in conjunction with DRAIN '''DME''' - Denton Municipal Electric '''DRAIN''' - Water Drainage '''DUE''' - Combination Drainage and Utility, because that combo is very common '''ELEC''' - Many UTIL easements are probably for electricity, but some are explicit about it '''FIRE''' - Firelane, typically is also an ACCESS easement '''GAS''' - For gas lines '''INGRESS''' - Always accompanied by EGRESS, considering changing these to ACCESS '''NO''' - When you can't verify the easement exists, but don't want to delete it for whatever reason '''PUE''' - Public Utility Easement, same as UTIL but "public". These can be changed to UTIL and only include the public distinction in the description. '''ROW''' - Right of Way dedications. These are not technically easements, but there is currently no better place to store them. '''SEWER''' - Sanitary Sewer '''SIDEWK''' - Sidewalk '''UTIL''' - Utilities '''WATER''' - Water lines ===Less Common=== '''ENVIRO''' - environmental inspection, only a few, all to First State Bank '''FENCE''' '''FLOOD''' - Floodplain '''GUY''' - Guy wires for poles/towers '''HYDRNT''' - Fire hydrants, presumably '''LAND''' - Landscape '''LIGHT''' - Street Light (for power line leading to light) '''MAINT''' - Too generic, probably have a more specific type if you can find the documentation '''PED''' - Pedestrian '''PIPE''' - Pipeline '''SIGN''' '''SLOPE''' '''SWB''' - unknown '''TREE''' - Tree preservation area '''VIS''' - Visibility '''WALL''' - Wall Maintenance ===Rare=== '''CONSRV''' - only 1, not sure what I could merge it with '''GREEN''' - not sure about this one '''LIFTST''' - No clue what it is; only 1 '''PARK''' - Parking, only 1 '''PLANE''' - Air traffic ==Finding documents== You can search the County Clerk's filings at http://216.60.44.147/TX/Denton/default.aspx If you have a document number or volume/page numbers, use Document search or Volume Search. To find new easements, do a date range search and select "EASEMENT" for type in the Advanced search options. Then you have to manually look through the results for ones in Denton, since the search results will be for all of Denton County. Easements that were filed between 3-29-2014 and 3-18-2015 have been entered. To expand this range, you would do a search starting 3-19-15 and ending a few weeks later. As you enter the easements you find in to GIS, keep track of your place. Update the dates in this paragraph from time to time. If you catch up to present day, start working backwards from 3-28-2014. ==Drawing== A common feature of easements is that they will run along the edge of parcels and have a certain width. To create a section of easement along a straight edge, first create the line along the parcel edge, then press ctrl+f to open the Deflection Angle dialog and enter "90" to do a right-angle turn. Then press ctrl+L to open the length dialog and enter the width of the easement. Do ctrl+f and "90" to create the third side, parallel to the first. Repeat this to create a feature for each different edge (shown in first image), then merge them all together (second image). Convex corners will merge correctly, for concave corners you will need to overshoot and then clean things up a bit (delete the two selected vertices in the second image). [[File:Easement step 1.PNG]] [[File:Easement step 2.PNG]] [[File:Easement step 3.PNG]] To draw curves, use the End Point Arc Segment tool, place the first and second points, then place the mouse on the middle of the curve and press 'r' to open the Radius dialog, as shown in the first image below. This tells you the radius of one side of the curve. Next, place the start and end points for the other side of the curve, then press 'r' again and enter the previous radius value +/- the width of the easement. So in this example, add 10 to 272.393. If the curve was convex, you would subtract 10 instead. In this example, the curve is conveniently book-ended by two straight segments, which provide the start and end points for the inside of the curve. ctrl+f, "90", ctrl+l, "width" works with curves too, for when things are not so convenient. [[File:Easement curve step 1.PNG]] [[File:Easement curve step 2.PNG]] Other useful editing tools are Intersection, Reshape Feature, Cut Polygons (reshape multiple polygons, delete the excess), Replace Geometry (when an attributed feature already exists but the geometry is bad), and the Traverse tool for when the easement does not follow parcel edges. If you enter the easements to spec and they don't fit the parcels, then the parcels in question may be a good candidate for [[Redrawing Parcels|redrawing]]. [[Category:RealEstate]] [[Category:Feature Class]] [[Category:Representable]] [[Category:Guides]]</div>

Dogtaton: short guide to drawing basic easements <hr /> <div>This is a replacement of the [[Easements|easements]] feature class. It stores all easements as well as right of way dedications. ==Fields== '''DateEdited''' - date of last edit to the feature '''EasementType1, EasementType2, EasementType3, EasementType4, EasementType5''' - Codes for the easement purposes such as Utility -> UTIL, Drainage -> DRAIN. To find all easements with a given type you need to select against all of the fields. '''Description''' - Full text of the easement types. An easement with types "ACCESS", "FIRE", and "UTIL" could have the description "Public Access, Firelane & Public Utility". '''DateFiled''' - Date the document was filed. '''DocumentNumber''' - City's code for the document, often looks like "A1234-567". The source and use of this code is an enigma, so I've been putting county clerk document numbers in this field. '''InstrumentNumber''' - County clerk's document number, good for finding the document. You also need to know the year since this number starts over each year '''Volume, Page''' - For looking up the document. For plats with a "cabinet"/page, Volume will be 'Cab X' '''Grantor, Grantee''' - The people giving up and receiving the easement rights. '''DocumentType''' - Type of document that describes the easement, e.g. EASEMENT, PLAT, WARRANTY DEED. ==Types== ===Common=== '''ABAND''' - Abandoned easements. These should be moved to the [[AbandonedEasements]] feature class, which is also in the [[:Category:RealEstate|RealEstate]] dataset. '''ACCESS''' - Sometimes attributed as INGRESS and EGRESS depending on how the legal document labels it. '''COMM''' - Communications. Not very common. '''DETEN''' - Water Detention, usually used in conjunction with DRAIN '''DME''' - Denton Municipal Electric '''DRAIN''' - Water Drainage '''DUE''' - Combination Drainage and Utility, because that combo is very common '''ELEC''' - Many UTIL easements are probably for electricity, but some are explicit about it '''FIRE''' - Firelane, typically is also an ACCESS easement '''GAS''' - For gas lines '''INGRESS''' - Always accompanied by EGRESS, considering changing these to ACCESS '''NO''' - When you can't verify the easement exists, but don't want to delete it for whatever reason '''PUE''' - Public Utility Easement, same as UTIL but "public". These can be changed to UTIL and only include the public distinction in the description. '''ROW''' - Right of Way dedications. These are not technically easements, but there is currently no better place to store them. '''SEWER''' - Sanitary Sewer '''SIDEWK''' - Sidewalk '''UTIL''' - Utilities '''WATER''' - Water lines ===Less Common=== '''ENVIRO''' - environmental inspection, only a few, all to First State Bank '''FENCE''' '''FLOOD''' - Floodplain '''GUY''' - Guy wires for poles/towers '''HYDRNT''' - Fire hydrants, presumably '''LAND''' - Landscape '''LIGHT''' - Street Light (for power line leading to light) '''MAINT''' - Too generic, probably have a more specific type if you can find the documentation '''PED''' - Pedestrian '''PIPE''' - Pipeline '''SIGN''' '''SLOPE''' '''SWB''' - unknown '''TREE''' - Tree preservation area '''VIS''' - Visibility '''WALL''' - Wall Maintenance ===Rare=== '''CONSRV''' - only 1, not sure what I could merge it with '''GREEN''' - not sure about this one '''LIFTST''' - No clue what it is; only 1 '''PARK''' - Parking, only 1 '''PLANE''' - Air traffic ==Finding documents== You can search the County Clerk's filings at http://216.60.44.147/TX/Denton/default.aspx If you have a document number or volume/page numbers, use Document search or Volume Search. To find new easements, do a date range search and select "EASEMENT" for type in the Advanced search options. Then you have to manually look through the results for ones in Denton, since the search results will be for all of Denton County. Easements that were filed between 3-29-2014 and 3-18-2015 have been entered. To expand this range, you would do a search starting 3-19-15 and ending a few weeks later. As you enter the easements you find in to GIS, keep track of your place. Update the dates in this paragraph from time to time. If you catch up to present day, start working backwards from 3-28-2014. ==Drawing== A common feature of easements is that they will run along the edge of parcels and have a certain width. To create a section of easement along a straight edge, first create the line along the parcel edge, then press ctrl+f to open the Deflection Angle dialog and enter "90" to do a right-angle turn. Then press ctrl+L to open the length dialog and enter the width of the easement. Do ctrl+f and "90" to create the third side, parallel to the first. Repeat this to create a feature for each different edge (shown in first image), then merge them all together (second image). Convex corners will merge correctly, for concave corners you will need to overshoot and then clean things up a bit (delete the two selected vertices in the second image). [[File:Easement step 1.PNG]] [[File:Easement step 2.PNG]] [[File:Easement step 3.PNG]] To draw curves, use the End Point Arc Segment tool, place the first and second points, then place the mouse on the middle of the curve and press 'r' to open the Radius dialog, as shown in the first image below. This tells you the radius of one side of the curve. Next, place the start and end points for the other side of the curve, then press 'r' again and enter the previous radius value +/- the width of the easement. So in this example, add 10 to 272.393. If the curve was convex, you would subtract 10 instead. In this example, the curve is conveniently book-ended by two straight segments, which provide the start and end points for the inside of the curve. ctrl+f, "90", ctrl+l, "width" works with curves too, for when things are not so convenient. [[File:Easement curve step 1.PNG]] [[File:Easement curve step 2.PNG]] Other useful editing tools are Intersection, Reshape Feature, Cut Polygons (reshape multiple polygons, delete the excess), Replace Geometry (when an attributed feature already exists but the geometry is bad), and the Traverse tool for when the easement does not follow parcel edges. If you enter the easements to spec and they don't fit the parcels, then the parcels in question may be a good candidate for [[Redrawing Parcels|redrawing]]. [[Category:RealEstate]][[Category:Feature Class]][[Category:Representable]]</div>

Dogtaton: <hr /> <div></div>

Dogtaton: <hr /> <div>Kind of a miscellaneous dataset, has feature classes for various categories of establishments e.g. Churches, Restaurants, multi-family dwellings, city facilities, libraries. [[Category:Datasets]]</div>

Dogtaton: Created page with "Kind of a miscellaneous dataset, has feature classes for various categories of establishments e.g. Churches, Restaurants, multi-family dwellings, city facilities, libraries." <hr /> <div>Kind of a miscellaneous dataset, has feature classes for various categories of establishments e.g. Churches, Restaurants, multi-family dwellings, city facilities, libraries.</div>

Dogtaton: <hr /> <div>Multi_families is a polygon layer of the land with apartments on it. Each Apartment complex has one entry except when it is addressed off of more than one street. In that case it is broken up to have one entry per street. The shapes are based on the parcel layer, but they're merged together into one per complex or building. ==Fields== Each record has the housing type, apartment name, number of units, address info, stcode of the street it's on, date built, and owner info. For apartment complexes that are split amongst multiple streets, the number of units is accordingly split up. Weston Place, for instance, has 22 units on W Hickory and 21 units on Stella. For some apartment complexes, the number of units couldn't be determined, in which case UNITS is set to -1 ==What's included== *Apartments *Townhomes *Duplexes *Mobile Home Parks *Hotels & Motels *Assisted Living *Dorms [[Category:Points_of_Interest]] [[Category:Feature Class]]</div>

Dogtaton: <hr /> <div>Accumulated data on the 2012 west nile epidemic. Positive traps, human cases (by date reported) and spraying areas: [[File:Traps,_spraying,_&_human_cases.gif]] [[Category:Datasets]]</div>

Dogtaton: Created page with "Feature Classes that describe DCTA assets. Category:Datasets" <hr /> <div>Feature Classes that describe DCTA assets. [[Category:Datasets]]</div>

Dogtaton: <hr /> <div>The Railroads layer contains all rail tracks in Denton County, or as many as could be identified. This includes the DCTA A-Train, part of the DART Green Line, and segments connecting to commercial/industrial sites. The layer was created mostly by looking at aerial imagery. Areas outside of the aerial extents were added from the DCTA A-Train and CountyRailRoads layers, the source of which isn't clear. ==Other Rail Layers== These layers contain different subsets of the data in Transportation/Railroads and are spread throughout the SDE *CountyRailRoads in the [[:Category:Transportation|Transportation]] dataset: currently contains no extra information. Railroads used to be constrained to the CityLimits in some places, though not in others, but now it contains all available rail data. *A_train_Route in the [[:Category:DCTA|DCTA]] dataset: which incorrectly(?) includes part of the green line. *RailsToTrails in the [[:Category:Parks|Parks]] dataset, which predates the planning and construction of the A-train [[Category:Transportation]] [[Category:Feature Class]]</div>

Dogtaton: <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. ==Attributes== *Fields pulled from DCAD ** PROP_ID, PROPERTY: 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]] ** SITUS_NUM, SITUS_PREF, SITUS_STRE, SITUS_SUFI, SITUS_ADDR: Address information ** OWNER_NAME, ADDRESS_1, ADDRESS_2, ADDR3, CITY, STATE, ZIP: Owner information ** LEGAL_DESC, PHASE, BLOCK, LOT: Legal description ** ABSTORSUBN, ABSTORSU_1, SUBNAME: Abstract/Subdivision information ** TOTALLAND, T_IMPROVE, TOTAL_PROP, APPRAISED_, ROLL_ASSD: Property values ** YEARBUILT: Year that current structure on the property was built ** PROP_TYPE, STATE_CD, CD_DESCRIP, LAND_TYPE, LANDTYPE: Descriptions of the land and it's usage ** LIVINGAREA, LAND_SQFT: Indoor and total?outdoor? area ** EXEMPTION: Tax status *City Fields ** LO_ADDRESS, HI_ADDRESS, STDIR, STNAME, STTYPE, SUITE, FULNAME, COD_SITUS, SITUS, SITE_CITY, SITE_STATE, SITE_ZIP: Address information ** ABST, ABSTNAMES: Abstract number and name ** COUNCIL_DI, ESN1, FIRE_DIST: Voter and emergency services districts ** STCODE: pulled from centerline the parcel is addressed off of ** FACILITYID: Identifier. [[Field Calculator#Parcels FACILITYID (python)|How to calculate for new fields.]] ** PLATTED: Y or N ** CNTY_NAME: Name of the city, or region of the city * other ** OBJECTID_1, OBJECTID: database identifiers ** CNTY_ZIPS: Matches SITE_ZIP more closely than ZIP (owner addr). Not sure why ** PIDNOTE, SUBDIV, METER: Mysterious ** SUP: Unused ==Improving feature geometry== See [[Redrawing Parcels]] ==Potential Table Improvements== *ADDRESS_1 -> ADDR_LINE1 to match CountyParcels so that these fields will transfer when copy and pasting features from that layer *ADDRESS_2 -> ADDR_LINE2 same reason *ADDR3 -> ADDR_LINE3 same reason, plus consistency *YEARBUILT -> YR_BLT same reason, though YEARBUILT is a better name *CNTY_ZIPS is redundant with SITE_ZIP. One is likely a more outdated version of the other *OBJECTID: supplanted by OBJECTID_1, but the best option is to delete both fields before reloading, then OBJECTID will be recreated *SUP: since unused, remove *CNTY_NAME: unclear utility *SUITE 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 *COD_SITUS and SITUS are duplicates *APPRAISED_ -> APPRAISED to match CountyParcels and just because [[Category:Planning]] [[Category:Feature Class]]</div>

Dogtaton: <hr /> <div>There are three annexation layers and then the CityLimits layer which for the most part reflects them. * Proposed_Annexations: contains areas that will be annexed. These should be the full area of an annexation and should not be updated as parts of it are annexed. * Recent_Annexations: contains the areas which are actually annexed (no non-annexation agreements) from 1998 onwards. This was the original feature class for tracking annexations and now it serves as extra work whenever you need to update an annexation and as a slightly more convenient way of only showing recent annexations in a map. * Recent_Annexations_Citywide_Historical: contains annexations from 1960 onwards. The 1960 annexation that starts it is a massive one that enclosed the whole city, so it provides a good basis for all the annexations that follow. Older annexation ordinances could not be found, and are now so far in the past that they don't matter. If you are entering new annexations, it's critical to read the annexation ordinance correctly. Triple check your reading. The latest ordinances have followed this formula: Describe a large area to be annexed (which gets added to Proposed_Annexations) Exclude certain parcels from that area (which get added to CityLimits as an NAA classed feature) Annex the remainder (add to both Recent_Annexations layer and to CityLimits as COD class) The trick step is figuring out which parcels to exclude. Create a new feature class (gdb or shapefile) and copy excluded parcels to it to keep track. New annexations will likely all include propid numbers, which makes this easier, but you still have to be careful of the wording. Tricky wording example of an exclusion (#5 from Exhibit C of ordinance 2015-182): <blockquote>Being 25.447 acres of land, more or less, situated in the S. Huizar Survey, Abstract No. 514 and the G. Barb Survey, Abstract No. 208, described in that Deed of Gift dated December 22, 1994, from James W. Wetzel and Freda J. Wetzel to Lisa K. Fergason and James Fergason, filed for record on December 27, 1994 and recorded in Instrument Number 94- R0093960 of the Real Property Records of Denton County, Texas; :SAVE AND EXCEPT that portion of the 25. 447 acre tract lying within the existing city limits, commonly known as DCAD Property ID 75052; :And further SAVE AND EXCEPT that portion of the 25. 447 acre tract of land previously conveyed to the State of Texas for Highway 380 right of way; Leaving 7. 535 acres, more or less, commonly known as DCAD Property ID 60782 and DCAD Property ID 36633.</blockquote> This begins by describing an overall shape of 25.447 acres that won't be annexed. Then it removes a parcel and some right-of-way from that tract. The remainder is 60782 and 36633, which means that those two parcels will NOT be annexed. Big shape not being annexed minus some stuff that will be annexed leaves a portion of the big shape to not be annexed. Maybe this seems clear to you, but when you're reading through dozens of descriptions like this it's easy to mess up. Read carefully and check your work. [[Category:CityBoundaries]] [[Category:Feature Class]] [[Category:Guides]]</div>

Dogtaton: <hr /> <div>{{Layer|AirportRoads|gif|Airport_Denton_Municipal|-}} All of the roads, taxiways, and runway at the airport, with attributes. [[Category:Airport_Denton_Municipal]] [[Category:Feature Class]]</div>

Dogtaton: <hr /> <div>{{Layer|AirportHangars|gif|Airport_Denton_Municipal|-}} Layer contains building footprints and available occupant information for all structures at the airport. [[Category:Airport_Denton_Municipal]] [[Category:Feature Class]]</div>

Dogtaton: <hr /> <div>{{Layer|Major_Road_1000ft_Buffers|gif|Emergency_Tier_2_Hazmat|-}} This single polygon represents areas at risk from their proximity to a major roadway. If a Hazmat incident occurs on a major roadway this can be used to quickly determine an evacuation area. [[Category:Emergency_Tier_2_Hazmat]] [[Category:Feature Class]]</div>

Dogtaton: <hr /> <div>{{Layer|Evacuation_Routes|gif|Emergency_Tier_2_Hazmat|-}}This layer shows the roads to use for evacuation in the event of an emergency. It was used for an evacuation route map but never included in the sde until recently. [[Category:Emergency_Tier_2_Hazmat]] [[Category:Feature Class]]</div>

Dogtaton: <hr /> <div>Clustered Dwellings is a version of the [[ClusteredDwellings | Planning/ClusteredDwellings]] layer that uses one point per apartment complex instead of 1 point per apartment unit. [[Category:Emergency_Tier_2_Hazmat]] [[Category:Feature Class]]</div>

Dogtaton: <hr /> <div>Parcels were originally created by tracing over paper maps with a digitizing tablet. Many of these original parcels shapes remain and are easy to spot for their not-straight lines and disagreement with the aerial imagery. DCAD's parcels are often of similar quality. It's ideal to redraw full blocks of parcels. If DATE_EDITE for the parcels is older than 2013 then there is probably room for significantly improvement. ==Traverse Tool== This is the tool for entering metes and bounds. When you enter a full circuit in the traverse tool you can check the "closed loop" box and then click the "Closure..." button, which is extremely useful for checking if you mis-entered any numbers. If the values for "Misclosure as X/Y" are greater than .01 feet, double check your work. Then 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 difficult, but it's very useful for catching data entry errors. ==Plats== If ABSTORSUBN doesn't start with an 'A', check the ABSTORSU_1 field and look up the plat in the Utilities Laserfiche under Design > Plats. Start with the newest and work backwards until you've entered all of the subdivision that is in the block you're working on. Enter the plat and block boundaries as temporary parcels, then redraw the parcels inside of it. A plat boundary is the only part of a plat that is certain to have complete measurements, including full descriptions of any curves. These temporary shapes then serves as a framework that makes filling in the individual parcels easier. If you are entering a plat boundary, you might not want to adjust it because then all the parcels will be 79.998' wide instead of 80'. I prefer to delete the last mete after checking the closure and then finish the shape instead of adjusting it. This will concentrate all of the mismatch in a single parcel, so it will be 79.9' and all the rest will be 80'. I'd rather have more parcels be exactly to spec than have all the parcels be equally off. It's personal preference, really, so don't worry too much if this isn't making sense. ==Deeds== 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. Instead of going back to the search page and clicking through to the details every time, you can just replace the number at the end of this URL : https://www.dentoncad.com/index.php?option=com_content&task=view&id=100&PropertyID=173423 Next go to the county clerk's document search site (http://216.60.44.147/TX/Denton/D/Default.aspx) The first dropdown should have "Real Property" selected. The document will be referenced in one of two ways: ===Document Number=== Ex: "2014-92284" Select "Document Number" from the second dropdown, enter "92284" and search, then click the result from 2014. ===Volume and Page=== Ex: "1034-678" 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 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 on the last or second to last page. Use the newest and work backwards if necessary until you find a readable document with a good description. Sometimes metes will have errors introduced when they are copied to newer deeds, so if a shape is not closing well, check older documents for differences. ==Fitting Everything together== When you're done redrawing each individual plat or deed you'll be left with a bunch of parcels that don't neatly fit together. The parcels will need to be rotated to fit together and some of them will need their geometry tweaked. Use the most accurate parcels in the block as a base. The most accurate will be ones that were recently GPS'd. The least accurate will be handwritten and use varas instead of feet. The first step is to rotate parcels so they have the same 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]]. This is a bit cumbersome, hopefully future versions of ArcMap have a better rotate tool. When you have everything rotated the same, things will still not fit together. This is the difficult and frustrating part. Start making judgement calls and moving vertices around, but try to limit the number of times you change any given parcel. If you move a vertex half a foot to match an adjacent parcel, that's not a huge deal, but if you keep coming back and moving it another half-foot then the accuracy will start to take a real hit. Rotating a feature is non-destructive of the basic geometry and necessary for almost every parcel, so try to get things to match as closely as possible with rotations before doing the final step of adjusting individual vertices. 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. As a final, somewhat optional step, you can trim the parcels back to the edge of road right-of-ways. If you are working from a plat which says "ROW dedication by this plat", create a ROW easement and attribute it with the plat's metadata. If you have no formal declaration of the ROW, you can just eyeball it and create unattributed ROW easements. Create one per parcel to fill the area of the parcel which overlaps the ROW and then trim that area off of the parcel. Is this a good system? Maybe. It yields good looking results and retains information about the full parcel shape, but it might not be very intuitive or maintainable. Save periodically if you're working on a large block. When you're satisfied with a block, delete any temporary features you made in the process, commit the changes, then export the block and send it to DCAD so they can benefit from your improved parcel geometry. This means you need to improve on DCAD's parcels for this to be worth doing. ==General Notes== *The older the measurements, the more they need to be corrected by rotating them counterclockwise. Newish stuff often needs rotating a little too. *Sometimes GPS coordinates will be wildly wrong. Coordinates from 2013 and later seem to be accurate [[Category:Ongoing Projects]] [[Category:Guides]]</div>

Dogtaton: /* Fitting Everything together */ <hr /> <div>Parcels were originally created by tracing over paper maps with a digitizing tablet. Many of these original parcels shapes remain and are easy to spot for their not-straight lines and disagreement with the aerial imagery. DCAD's parcels are of similar quality. It's ideal to redraw full blocks of parcels. If DATE_EDITE for the parcels is older than 2013 then there is probably room for significantly improvement. ==Traverse Tool== This is the tool for entering metes and bounds. When you enter a full circuit in the traverse tool you can check the "closed loop" box and then click the "Closure..." button, which is extremely useful for checking if you mis-entered any numbers. If the values for "Misclosure as X/Y" are greater than .01 feet, double check your work. Then 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 difficult, but it's very useful for catching data entry errors. ==Plats== If ABSTORSUBN doesn't start with an 'A', check the ABSTORSU_1 field and look up the plat in the Utilities Laserfiche under Design > Plats. Start with the newest and work backwards until you've entered all of the subdivision that is in the block you're working on. Enter the plat and block boundaries as temporary parcels, then redraw the parcels inside of it. A plat boundary is the only part of a plat that is certain to have complete measurements, including full descriptions of any curves. These temporary shapes then serves as a framework that makes filling in the individual parcels easier. If you are entering a plat boundary, you might not want to adjust it because then all the parcels will be 79.998' wide instead of 80'. I prefer to delete the last mete after checking the closure and then finish the shape instead of adjusting it. This will concentrate all of the mismatch in a single parcel, so it will be 79.9' and all the rest will be 80'. I'd rather have more parcels be exactly to spec than have all the parcels be equally off. It's personal preference, really, so don't worry too much if this isn't making sense. ==Deeds== 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. Instead of going back to the search page and clicking through to the details every time, you can just replace the number at the end of this URL : https://www.dentoncad.com/index.php?option=com_content&task=view&id=100&PropertyID=173423 Next go to the county clerk's document search site (http://216.60.44.147/TX/Denton/D/Default.aspx) The first dropdown should have "Real Property" selected. The document will be referenced in one of two ways: ===Document Number=== Ex: "2014-92284" Select "Document Number" from the second dropdown, enter "92284" and search, then click the result from 2014. ===Volume and Page=== Ex: "1034-678" 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 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 on the last or second to last page. Use the newest and work backwards if necessary until you find a readable document with a good description. Sometimes metes will have errors introduced when they are copied to newer deeds, so if a shape is not closing well, check older documents for differences. ==Fitting Everything together== When you're done redrawing each individual plat or deed you'll be left with a bunch of parcels that don't neatly fit together. The parcels will need to be rotated to fit together and some of them will need their geometry tweaked. Use the most accurate parcels in the block as a base. The most accurate will be ones that were recently GPS'd. The least accurate will be handwritten and use varas instead of feet. The first step is to rotate parcels so they have the same 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]]. This is a bit cumbersome, hopefully future versions of ArcMap have a better rotate tool. When you have everything rotated the same, things will still not fit together. This is the difficult and frustrating part. Start making judgement calls and moving vertices around, but try to limit the number of times you change any given parcel. If you move a vertex half a foot to match an adjacent parcel, that's not a huge deal, but if you keep coming back and moving it another half-foot then the accuracy will start to take a real hit. Rotating a feature is non-destructive of the basic geometry and necessary for almost every parcel, so try to get things to match as closely as possible with rotations before doing the final step of adjusting individual vertices. 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. As a final, somewhat optional step, you can trim the parcels back to the edge of road right-of-ways. If you are working from a plat which says "ROW dedication by this plat", create a ROW easement and attribute it with the plat's metadata. If you have no formal declaration of the ROW, you can just eyeball it and create unattributed ROW easements. Create one per parcel to fill the area of the parcel which overlaps the ROW and then trim that area off of the parcel. Is this a good system? Maybe. It yields good looking results and retains information about the full parcel shape, but it might not be very intuitive or maintainable. Save periodically if you're working on a large block. When you're satisfied with a block, delete any temporary features you made in the process, commit the changes, then export the block and send it to DCAD so they can benefit from your improved parcel geometry. This means you need to improve on DCAD's parcels for this to be worth doing. ==General Notes== *The older the measurements, the more they need to be corrected by rotating them counterclockwise. Newish stuff often needs rotating a little too. *Sometimes GPS coordinates will be wildly wrong. Coordinates from 2013 and later seem to be accurate [[Category:Ongoing Projects]] [[Category:Guides]]</div>

Dogtaton: Created page with "County-maintained counterpart to our City_Addresses feature class. Note that it is stored in the Transportation dataset instead of the Planning dataset with City_Addresses..." <hr /> <div>County-maintained counterpart to our [[City_Addresses]] feature class. Note that it is stored in the Transportation dataset instead of the Planning dataset with City_Addresses. [[Category:Transportation]] [[Category:Feature Class]]</div>

Dogtaton: <hr /> <div>{{Layer|AirportPavement|gif|Airport_Denton_Municipal|-}} Contains all pavement at the airport, traced from the [[NCTCOG]] aerial images. [[Category:Airport_Denton_Municipal]] [[Category:Feature Class]]</div>

Dogtaton: <hr /> <div>Boundary of city limits including the areas that have non-annexation agreements in effect. The non-annexations are attributed with the end date of the agreement e.g. "NAA 8/1/20" Most changes to this layer are the result of [[Redrawing_Parcels|redrawing parcels]] and then updating this layer and the [[Annexations|annexation layers]] to fit the newly accurate parcels. [[Category:CityBoundaries]] [[Category:Feature Class]]</div>

Dogtaton: Created page with "Contains roadways for the whole county, as opposed to Centerline which only contains roads in and near Denton city limits. Centerline is better if you don't need/want to s..." <hr /> <div>Contains roadways for the whole county, as opposed to [[Centerline]] which only contains roads in and near Denton city limits. Centerline is better if you don't need/want to show roads outside of city limits. I think it is maintained by the county. [[Category:Transportation]] [[Category:Feature Class]]</div>

Dogtaton: <hr /> <div>North Central Texas Council of Governments is the source of various data. They maintain an interactive map at [http://http://www.dfwmaps.com dfwmaps.com] Main page: [http://www.nctcog.org NCTCOG.org] [[Category:Data Sources]]</div>

Dogtaton: Created page with "When an easement is abandoned, it should be moved from the Easement feature class to this one. It has the same fields as Easement plus an AbandonedDate field. Category:R..." <hr /> <div>When an easement is abandoned, it should be moved from the [[Easement]] feature class to this one. It has the same fields as Easement plus an AbandonedDate field. [[Category:RealEstate]] [[Category:Feature Class]]</div>

Dogtaton: Created page with "Places to get information and data." <hr /> <div>Places to get information and data.</div>

Dogtaton: Created page with "The Denton Central Appraisal District offers useful things through their website *[https://www.dentoncad.com/index.php?option=com_docman&task=cat_view&gid=16&Itemid=62 GIS dat..." <hr /> <div>The Denton Central Appraisal District offers useful things through their website *[https://www.dentoncad.com/index.php?option=com_docman&task=cat_view&gid=16&Itemid=62 GIS data downloads]: The source of most of the components for creating our [[CountyParcels]]. *[https://www.dentoncad.com/index.php?option=com_content&task=view&id=98&Itemid=54 Property search]: Very useful for finding plat and deed information. *[https://gis.dentoncad.com/DentonCounty/ Interactive map] They also maintain a table of property values (used in CountyParcels), which is available on request. [[Category:Data Sources]]</div>

Dogtaton: /* Finding Documentation */ <hr /> <div>==COD GIS== Documentation mainly for data in the ArcSDE database. ==Finding Documentation== The available documentation for the SDE can be browsed by [[:Category:Datasets|dataset]] or you can view a list of all [[:Category:Feature Class|feature classes]]. Other categories of documentation *[[:Category:Recurring Projects|Recurring projects]]. *[[:Category:Ongoing Projects|Ongoing projects]]. *[[:Category:Guides|Guides]]: Instructions for doing and using various things. If the information you want isn't here, create the page or edit an existing page to ask for it. Please don't be afraid of being a bother, the best way to expand the documentation is to add what people need and the only way to know what's needed is for people to ask. ==Adding/Editing Documentation== Feel free to edit and add. If you create a new dataset or feature class, create a simple page to describe what it's for and give a brief description of the fields. Don't be afraid of messing things up; the software running this site is designed to be resilient and never lose information.</div>

Dogtaton: <hr /> <div>The Trimble device lets you use GPS to record features in the field. TerraSync is the program on the device that is used for recording and managing GPS'd data. Pathfinder is the program on a desktop computer that is used in tandem with the device. ==Advantages over the phone in your pocket== *It collects multiple measurements for each point feature(which requires standing still and waiting a bit) and averages/processes them to get better accuracy than a single reading would achieve. *It lets you record line and polygon features by moving along the line/perimeter. It logs the vertices automatically based on either distance moved or time elapsed since the last point. *Post-processing using known GPS base stations can be done to further improve accuracy *It allows you to define different feature types with different attributes and you can fill them in, rather than just recording the spots in Google Maps (or what have you) and entering them into a feature later. ==Disadvantages over the phone in your pocket== *weight *cost *old style touch screen (for most models the city currently has) ==TerraSync Organization== The TerraSync software is organized under 5 different groups: *[[Trimble_Map|Map]] *[[Trimble_Data|Data]] *[[Trimble_Navigation|Navigation]] *[[Trimble_Status|Status]] *[[Trimble_Setup|Setup]] 99% of the time you will be using either Map or Data ==Using TerraSync== *[[Trimble Create Dictionary|Create a dictionary]] that defines features you want to capture. Dictionaries are the schemas for data files *[[Trimble Data File|Create a data file]] for storing the features you capture. *[[Trimble Capturing Data|Capture data]] *[[Trimble View Data|View captured data]] *[[Trimble Import Export|Move the data to a PC]] for storage and further use/analysis. *[[Trimble Pathfinder|Use Pathfinder]] to correct the data. ==Further Documentation== A 233 page guide is available from [http://www.trimble.com/globalTRLTAB.asp?Nav=Collection-30232 Trimble documents] The version is 4.10: [http://trl.trimble.com/dscgi/ds.py/Get/File-478231/TerraSyncGettingStartedGuide.pdf TerraSync Getting Started Guide] A more brief guide, with much of the same information as this wiki: [http://www.dogtato.net/gis/TerraSync%20Basic%20Manual.pdf TerraSync Basic Manual] [[Category:Guides]]</div>

Dogtaton: <hr /> <div>To view features you've recorded to a data file, open the file and go to the map. Under Layers you can check/uncheck "Filtered Features" and "Unfiltered Features" to show the features. By default all features in the data file will be unfiltered. To adjust which features are filtered, click Options > Filter. You can set a feature type to be filtered, unfiltered, or filtered based on definable criteria. [[Category:Trimble]]</div>

Dogtaton: <hr /> <div>There are several good sources for plats (and other documents): *[[http://lfwebaccess/Laserfiche8/index.aspx?db=Utilities | Laserfiche]]: Requires a city account to access. Plats are under Engineering > Design > Plats. *[[http://www.dentoncad.com/index.php?option=com_content&task=view&id=98&Itemid=54 | DCAD]]: Look up the parcel (propid is usually the most convenvient way), click "View Details" for the result, then click "View Plat" to load a tiff of the plat. It works better if you right click and save the tiff to your computer vs. loading it in the browser. *[[http://216.60.44.147/TX/Denton/ | Denton County Clerk's Real Property Search]]: This is what you use to look up everything else. The search options are a bit confusing, but it allows you to look up things by different criteria than the other sites and it has every document. Different search types are selected by mousing over "Search Criteria" at the top of the page. **"Vol 1504, Pg 153" - Choose "Volume Search", enter 1504 and 153 in the first and second boxes **"File No. 94-R0011534" - Choose "Document Search", enter 11534 in the first search box, and then find the search result from 1994 **"CAB B, Pg 263" - Choose "Cabinet Search" (under Maps/Plats) and enter B and 263 [[Category:Guides]]</div>

Dogtaton: Created page with "These pages describe the steps to accomplish a task." <hr /> <div>These pages describe the steps to accomplish a task.</div>

Dogtaton: <hr /> <div>{{Layer|CountyParcels|gif|Planning|Dec 6, 2012}} The CountyParcels layer is assembled using data from [[DCAD]]. =Components= From [http://www.dentoncad.com/index.php?option=com_docman&task=cat_view&gid=16&Itemid=62 DCADs GIS Downloads page] * Denton County Parcels Map (shapefile) * GIS DCAD Data Then contact J.M. for the situs info and property value tables. It is recommended to use [[AveryDB]] to assemble the components, unless/until ESRI improves the process of doing it through their software. =Table Composition= <table bgcolor=white border=.1><tr><td colspan=39>CountyParcels</td></tr> <tr><td>target</td><td bgcolor=#00cc33>OBJECTID_1</td><td bgcolor=#00cc33>OBJECTID</td><td bgcolor=#00cc33>ABSTORSUBN</td><td bgcolor=#00cc33>ABSTORSU_1</td><td bgcolor=#00cc33>PROP_ID</td><td bgcolor=#00cc33>PROP_TYPE_</td><td bgcolor=#00cc33>BLOCK</td><td bgcolor=#00cc33>LOT</td><td bgcolor=#00cc33>LAND_SQFT</td><td bgcolor=#00cc33>LIVINGAREA</td><td bgcolor=#00cc33>EXEMPTION</td><td bgcolor=#00cc33>PROPERTY</td><td bgcolor=#00cc33>SITUS</td><td bgcolor=#00cc33>OWNER_NAME</td><td bgcolor=#00cc33>ADDR_LINE1</td><td bgcolor=#00cc33>ADDR_LINE2</td><td bgcolor=#00cc33>ADDR_LINE3</td><td bgcolor=#00cc33>CITY</td><td bgcolor=#00cc33>STATE</td><td bgcolor=#00cc33>ZIP</td><td bgcolor=#00cc33>LEGAL_DESC</td><td bgcolor=#00cc33>STATE_CD</td><td bgcolor=#00cc33>CD_DESCRIP</td><td bgcolor=#00cc33>TAXENTITY</td><td bgcolor=#00cc33>SITUS_PREF</td><td bgcolor=#00cc33>SITUS_NUM</td><td bgcolor=#ccffcc>SITUS_ST</td><td bgcolor=#00cc33>SITUS_SUFI</td><td bgcolor=#00cc33>YR_BLT</td><td bgcolor=#00cc33>AG_MARKET</td><td bgcolor=#00cc33>APPRAISED_</td><td bgcolor=#00cc33>AG_USE_VAL</td><td bgcolor=#ccffcc>ROLL_ASSD</td><td bgcolor=#ccffcc>T_IMPROVE</td><td bgcolor=#ccffcc>TOTALLAND</td><td bgcolor=#ccffcc>TOTAL_PROP</td><td bgcolor=#00cc33>Shape_area</td><td bgcolor=#00cc33>Shape_len</td></tr> <tr><td></td><td>1</td><td>1</td><td>SL0802A</td><td>THE HIGHLANDS PH 4</td><td>236721</td><td>R</td><td>Z</td><td>12</td><td>13328</td><td>1794</td><td>HS, OV65</td><td>R236721</td><td>2021 WOLF CREEK</td><td>GOURLIE, RONALD A & CONNIE M</td><td></td><td>2021 WOLF CREEK PASS</td><td></td><td>LEWISVILLE</td><td>TX</td><td>75077-7546</td><td>THE HIGHLANDS PH 4 BLK Z LOT 12</td><td>A1</td><td>Single Family</td><td>C12, CAD, G01, S09</td><td></td><td>2021</td><td>WOLF CREEK</td><td>PASS</td><td>2004</td><td>0</td><td>187600</td><td>0</td><td>184232</td><td>137463</td><td>50137</td><td>187600</td><td>13193.84953</td><td>456.78393</td></tr> <tr><td colspan=39>Parcel Shapefile</td></tr> <tr><td>source</td><td bgcolor=#00cc33>OBJECTID_1</td><td bgcolor=#00cc33>OBJECTID</td><td bgcolor=#00cc33>ABSTORSUBN</td><td bgcolor=#00cc33>ABSTORSU_1</td><td bgcolor=#00cc33>PROP_ID</td><td colspan=31><td bgcolor=#00cc33>Shape_area</td><td bgcolor=#00cc33>Shape_len</td></tr> <tr><td colspan=39>DCAD Data</td></tr> <tr><td>join PROP_ID</td><td colspan=4><td bgcolor=#ff3333>PROP_ID</td><td bgcolor=#00cc33>PROP_TYPE</td><td bgcolor=#00cc33>BLOCK</td><td bgcolor=#00cc33>LOT</td><td bgcolor=#00cc33>LAND_SQFT</td><td bgcolor=#00cc33>LIVINGAREA</td><td bgcolor=#00cc33>EXEMPTION</td><td></td><td bgcolor=#00cc33>SITUS</td><td bgcolor=#00cc33>OWNER_NAME</td><td bgcolor=#00cc33>ADDR_LINE1</td><td bgcolor=#00cc33>ADDR_LINE2</td><td bgcolor=#00cc33>ADDR_LINE3</td><td bgcolor=#00cc33>CITY</td><td bgcolor=#00cc33>STATE</td><td bgcolor=#00cc33>ZIP</td><td bgcolor=#00cc33>LEGAL_DESC</td><td bgcolor=#00cc33>STATE_CD</td><td></td><td bgcolor=#00cc33>TAXENTITY</td><td bgcolor=#ff3333>LAND_TYPE</td><td colspan=3><td bgcolor=#00cc33>YR_BLT</td><td colspan=9></td></tr> <tr><td colspan=39>TONYSMIT</td></tr> <tr><td>join PROP_ID</td><td bgcolor=#ff3333>DISPLAY</td><td colspan=3><td bgcolor=#ff3333>PROP_ID</td><td colspan=8></td><td bgcolor=#ff3333>FILE_AS_NA</td><td bgcolor=#ff3333>ADDR_LINE1</td><td bgcolor=#ff3333>ADDR_LINE2</td><td bgcolor=#ff3333>ADDR_LINE3</td><td bgcolor=#ff3333>ADDR_CITY</td><td bgcolor=#ff3333>ADDR_STATE</td><td></td><td bgcolor=#ff3333>LEGAL_DESC</td><td bgcolor=#ff3333>STATE_CD</td><td></td><td bgcolor=#ff3333>ENTITYCODE</td><td bgcolor=#00cc33>SITUS_PREF</td><td bgcolor=#00cc33>SITUS_NUM</td><td bgcolor=#00cc33>SITUS_STRE</td><td bgcolor=#00cc33>SITUS_SUFI</td><td bgcolor=#ff3333>YR_BLT</td><td colspan=9></td></tr> <tr><td colspan=34>VALUES<td bgcolor=#ccffcc>IMPRV_HSTD</td><td bgcolor=#ccffcc>LAND_HSTD_</td></tr> <tr><td>join PROP_ID</td><td colspan=4></td><td bgcolor=#ff3333>PROP_ID</td><td colspan=24></td><td bgcolor=#00cc33>AG_MARKET</td><td bgcolor=#00cc33>APPRAISED_</td><td bgcolor=#00cc33>AG_USE_VAL</td><td bgcolor=#ccffcc>ASSESSED_V</td><td bgcolor=#ccffcc>IMPRV_NON_</td><td bgcolor=#ccffcc>LAND_NON_H</td><td bgcolor=#ccffcc>MARKET</td><td bgcolor=#ff3333>TIMBER_MAR</td><td bgcolor=#ff3333>TIMBER_USE</td></tr> <tr><td colspan=39>state-codes-3</td></tr> <tr><td>join STATE_CD</td><td colspan=21></td><td bgcolor=#ff3333>STATE_CD</td><td bgcolor=#00cc33>CD_DESCRIP</td><td colspan=15></td></tr> <tr><td>Other source</td><td colspan=11></td><td bgcolor=#00cc33>calc from PROP_ID</td><td colspan=26></td></tr> <tr><td>Legend</td><td bgcolor=#00cc33>direct match</td><td bgcolor=#ccffcc>partial match</td><td bgcolor=#ff3333>unneeded</td><td colspan=35></td></tr> </table> T_IMPROVE and TOTTALLAND are calculated by "IMPRV_HSTD + IMPRV_NON_" and "LAND_HSTD_ + LAND_NON_H", respectively. SITUS_STRE is changed to SITUS_ST. PROPERTY is calculated with the following input to Field Calculator: <table border=.1><tr><td>Pre-Logic Script Code:</td></tr> <tr><td> tval = Len ( [PROP_ID] ) if tval > 4 then rval = "R" elseif tval > 3 then rval = "R0" elseif tval > 2 then rval = "R00" else rval = "R000" end if </td></tr> <tr><td>PROPERTY =</td></tr> <tr><td>rval& [PROP_ID]</td></tr> </table> [[Category:Planning]] [[Category:Feature Class]] [[Category:Recurring Projects]] [[Category:Guides]]</div>

Dogtaton: <hr /> <div>Parcels were originally created by tracing over paper maps with a digitizing tablet. Many of these original parcels shapes remain and are easy to spot for their not-straight lines and disagreement with the aerial imagery. DCAD's parcels are of similar quality. It's ideal to redraw full blocks of parcels. If DATE_EDITE for the parcels is older than 2013 then there is probably room for significantly improvement. ==Traverse Tool== This is the tool for entering metes and bounds. When you enter a full circuit in the traverse tool you can check the "closed loop" box and then click the "Closure..." button, which is extremely useful for checking if you mis-entered any numbers. If the values for "Misclosure as X/Y" are greater than .01 feet, double check your work. Then 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 difficult, but it's very useful for catching data entry errors. ==Plats== If ABSTORSUBN doesn't start with an 'A', check the ABSTORSU_1 field and look up the plat in the Utilities Laserfiche under Design > Plats. Start with the newest and work backwards until you've entered all of the subdivision that is in the block you're working on. Enter the plat and block boundaries as temporary parcels, then redraw the parcels inside of it. A plat boundary is the only part of a plat that is certain to have complete measurements, including full descriptions of any curves. These temporary shapes then serves as a framework that makes filling in the individual parcels easier. If you are entering a plat boundary, you might not want to adjust it because then all the parcels will be 79.998' wide instead of 80'. I prefer to delete the last mete after checking the closure and then finish the shape instead of adjusting it. This will concentrate all of the mismatch in a single parcel, so it will be 79.9' and all the rest will be 80'. I'd rather have more parcels be exactly to spec than have all the parcels be equally off. It's personal preference, really, so don't worry too much if this isn't making sense. ==Deeds== 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. Instead of going back to the search page and clicking through to the details every time, you can just replace the number at the end of this URL : https://www.dentoncad.com/index.php?option=com_content&task=view&id=100&PropertyID=173423 Next go to the county clerk's document search site (http://216.60.44.147/TX/Denton/D/Default.aspx) The first dropdown should have "Real Property" selected. The document will be referenced in one of two ways: ===Document Number=== Ex: "2014-92284" Select "Document Number" from the second dropdown, enter "92284" and search, then click the result from 2014. ===Volume and Page=== Ex: "1034-678" 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 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 on the last or second to last page. Use the newest and work backwards if necessary until you find a readable document with a good description. Sometimes metes will have errors introduced when they are copied to newer deeds, so if a shape is not closing well, check older documents for differences. ==Fitting Everything together== When you're done redrawing each individual plat or deed you'll be left with a bunch of parcels that don't neatly fit together. The parcels will need to be rotated to fit together and some of them will need their geometry tweaked. Use the most accurate parcels in the block as a base. The most accurate will be ones that were recently GPS'd. The least accurate will be handwritten and use varas instead of feet. The first step is to rotate parcels so they have the same 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]]. This is a bit cumbersome, hopefully future versions of ArcMap have a better rotate tool. When you have everything rotated the same, things will still not fit together. This is the difficult and frustrating part. Start making judgement calls and moving vertices around, but try to limit the number of times you change any given parcel. If you move a vertex half a foot to match an adjacent parcel, that's not a huge deal, but if you keep coming back and moving it another half-foot then the accuracy will start to take a real hit. Rotating a feature is non-destructive of the basic geometry and necessary for almost every parcel, so try to get things to match as closely as possible with rotations before doing the final step of adjusting individual vertices. 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. Save periodically if you're working on a large block. When you're satisfied with a block, delete any temporary features you made in the process, commit the changes, then export the block and send it to DCAD so they can benefit from your improved parcel geometry. This means you need to improve on DCAD's parcels for this to be worth doing. ==General Notes== *The older the measurements, the more they need to be corrected by rotating them counterclockwise. Newish stuff often needs rotating a little too. *Sometimes GPS coordinates will be wildly wrong. Coordinates from 2013 and later seem to be accurate [[Category:Ongoing Projects]] [[Category:Guides]]</div>

Dogtaton: <hr /> <div>A map index is used with a grid to locate features in a map. This will describe a process to generate the index for the street map. The street map index looks like this: *ABBOT'S LN: 17K, 17L *ABBY WAY: 15O *ACME ST: 15J *ACORN BEND: 20L, 20M It's a list of street names followed by a list of the grid cells that contain the street. First, dissolve on the feature class being indexed. Dissolve is in the toolbox under Data Management Tools > Generalization. Select the centerline layer for Input Features and select FULNAME for the dissolve field. Other settings can be left as defaults. Next, do a spatial join of the dissolved class to the grid. Spatial join is in the toolbox under Analysis Tools > Overlay. Select the dissolved layer for Target Features, select the grid for Join Features, leave it as a 1-to-1 join. In the field map of join features, right click the field with the grid cell id ("Grid_Num" in this example) and open the properties. For Merge Rule select "Join" and for a delimiter enter ", " You might also need to increase the length of the field to accommodate a long list. If you get an error like "ERROR 001156: Failed on input OID 507, could not write value '13K, 13L, 14L, 14M, 14N, 14O, 14P, 15P, 15Q, 16Q, 16R' to output field Grid_Num" then the field was not long enough. I set it to 1000 so it will succeed and then later I'll manually cull the culprits like "PRIVATE DR" and "PUBLIC ALLEY". Export the table to a text or dbf file then open it in excel. Get rid of all the columns except street name and the list of grid cells. Add a column and fill it with "=len([address of grid cell list])". Sort descending on this length column and remove the top entries for major roads and the common generic names like "PRIVATE DR". For roads with more than 3 or 4 cells listed, you can edit it down to the start and end cells e.g. "08F to 14F". Consolidate N/S/E/W streets in to a single entry. Once you've cleaned up the data you can format it for export. In a 4th column enter the formula "=concatenate([street name], ': ', [grid cell list])" then copy the column and "paste special" it as values. The goal of the next step is to get a good balance of number of columns vs column length in order for the index to fill all the available space in the map so the text is as large (thereby readable) as possible. Break the single column up in to side-by-side columns of 100 or so. Once you've done that, copy and paste them in to arcmap then resize. Check whether the resulting table is too narrow or wide, adjust, and repeat. This is a cumbersome process, so edit in a better way if you know one. [[Category:Guides]]</div>

Dogtaton: /* Improving feature geometry */ <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. ==Attributes== *Fields pulled from DCAD ** PROP_ID, PROPERTY: 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]] ** SITUS_NUM, SITUS_PREF, SITUS_STRE, SITUS_SUFI, SITUS_ADDR: Address information ** OWNER_NAME, ADDRESS_1, ADDRESS_2, ADDR3, CITY, STATE, ZIP: Owner information ** LEGAL_DESC, PHASE, BLOCK, LOT: Legal description ** ABSTORSUBN, ABSTORSU_1, SUBNAME: Abstract/Subdivision information ** TOTALLAND, T_IMPROVE, TOTAL_PROP, APPRAISED_, ROLL_ASSD: Property values ** YEARBUILT: Year that current structure on the property was built ** PROP_TYPE, STATE_CD, CD_DESCRIP, LAND_TYPE, LANDTYPE: Descriptions of the land and it's usage ** LIVINGAREA, LAND_SQFT: Indoor and total?outdoor? area ** EXEMPTION: Tax status *City Fields ** LO_ADDRESS, HI_ADDRESS, STDIR, STNAME, STTYPE, SUITE, FULNAME, COD_SITUS, SITUS, SITE_CITY, SITE_STATE, SITE_ZIP: Address information ** ABST, ABSTNAMES: Abstract number and name ** COUNCIL_DI, ESN1, FIRE_DIST: Voter and emergency services districts ** STCODE: pulled from centerline the parcel is addressed off of ** FACILITYID: Identifier. [[Field Calculator#Parcels FACILITYID (python)|How to calculate for new fields.]] ** PLATTED: Y or N ** CNTY_NAME: Name of the city, or region of the city * other ** OBJECTID_1, OBJECTID: database identifiers ** CNTY_ZIPS: Matches SITE_ZIP more closely than ZIP (owner addr). Not sure why ** PIDNOTE, SUBDIV, METER: Mysterious ** SUP: Unused ==Improving feature geometry== See [[Redrawing Parcels]] ==Potential Table Improvements== *ADDRESS_1 -> ADDR_LINE1 to match CountyParcels so that these fields will transfer when copy and pasting features from that layer *ADDRESS_2 -> ADDR_LINE2 same reason *ADDR3 -> ADDR_LINE3 same reason, plus consistency *YEARBUILT -> YR_BLT same reason, though YEARBUILT is a better name *CNTY_ZIPS is redundant with SITE_ZIP. One is likely a more outdated version of the other *OBJECTID: supplanted by OBJECTID_1, but the best option is to delete both fields before reloading, then OBJECTID will be recreated *SUP: since unused, remove *CNTY_NAME: unclear utility *SUITE 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 *COD_SITUS and SITUS are duplicates *APPRAISED_ -> APPRAISED to match CountyParcels and just because [[Category:Planning]]</div>

Dogtaton: <hr /> <div>Parcels were originally created by tracing over paper maps with a digitizing tablet. Many of these original parcels shapes remain and are easy to spot for their not-straight lines and disagreement with the aerial imagery. DCAD's parcels are of similar quality. It's ideal to redraw full blocks of parcels. If DATE_EDITE for the parcels is older than 2013 then there is probably room for significantly improvement. ==Traverse Tool== This is the tool for entering metes and bounds. When you enter a full circuit in the traverse tool you can check the "closed loop" box and then click the "Closure..." button, which is extremely useful for checking if you mis-entered any numbers. If the values for "Misclosure as X/Y" are greater than .01 feet, double check your work. Then 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 difficult, but it's very useful for catching data entry errors. ==Plats== If ABSTORSUBN doesn't start with an 'A', check the ABSTORSU_1 field and look up the plat in the Utilities Laserfiche under Design > Plats. Start with the newest and work backwards until you've entered all of the subdivision that is in the block you're working on. Enter the plat and block boundaries as temporary parcels, then redraw the parcels inside of it. A plat boundary is the only part of a plat that is certain to have complete measurements, including full descriptions of any curves. These temporary shapes then serves as a framework that makes filling in the individual parcels easier. If you are entering a plat boundary, you might not want to adjust it because then all the parcels will be 79.998' wide instead of 80'. I prefer to delete the last mete after checking the closure and then finish the shape instead of adjusting it. This will concentrate all of the mismatch in a single parcel, so it will be 79.9' and all the rest will be 80'. I'd rather have more parcels be exactly to spec than have all the parcels be equally off. It's personal preference, really, so don't worry too much if this isn't making sense. ==Deeds== 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. Instead of going back to the search page and clicking through to the details every time, you can just replace the number at the end of this URL : https://www.dentoncad.com/index.php?option=com_content&task=view&id=100&PropertyID=173423 Next go to the county clerk's document search site (http://216.60.44.147/TX/Denton/D/Default.aspx) The first dropdown should have "Real Property" selected. The document will be referenced in one of two ways: ===Document Number=== Ex: "2014-92284" Select "Document Number" from the second dropdown, enter "92284" and search, then click the result from 2014. ===Volume and Page=== Ex: "1034-678" 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 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 on the last or second to last page. Use the newest and work backwards if necessary until you find a readable document with a good description. Sometimes metes will have errors introduced when they are copied to newer deeds, so if a shape is not closing well, check older documents for differences. ==Fitting Everything together== When you're done redrawing each individual plat or deed you'll be left with a bunch of parcels that don't neatly fit together. The parcels will need to be rotated to fit together and some of them will need their geometry tweaked. Use the most accurate parcels in the block as a base. The most accurate will be ones that were recently GPS'd. The least accurate will be handwritten and use varas instead of feet. The first step is to rotate parcels so they have the same 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]]. This is a bit cumbersome, hopefully future versions of ArcMap have a better rotate tool. When you have everything rotated the same, things will still not fit together. This is the difficult and frustrating part. Start making judgement calls and moving vertices around, but try to limit the number of times you change any given parcel. If you move a vertex half a foot to match an adjacent parcel, that's not a huge deal, but if you keep coming back and moving it another half-foot then the accuracy will start to take a real hit. Rotating a feature is non-destructive of the basic geometry and necessary for almost every parcel, so try to get things to match as closely as possible with rotations before doing the final step of adjusting individual vertices. 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. Save periodically if you're working on a large block. When you're satisfied with a block, delete any temporary features you made in the process, commit the changes, then export the block and send it to DCAD so they can benefit from your improved parcel geometry. This means you need to improve on DCAD's parcels for this to be worth doing. ==General Notes== *The older the measurements, the more they need to be corrected by rotating them counterclockwise. Newish stuff often needs rotating a little too. *Sometimes GPS coordinates will be wildly wrong. Coordinates from 2013 and later seem to be accurate [[Category:Ongoing Projects]]</div>

Dogtaton: /* Components */ <hr /> <div>{{Layer|CountyParcels|gif|Planning|Dec 6, 2012}} The CountyParcels layer is assembled using data from [[DCAD]]. =Components= From [http://www.dentoncad.com/index.php?option=com_docman&task=cat_view&gid=16&Itemid=62 DCADs GIS Downloads page] * Denton County Parcels Map (shapefile) * GIS DCAD Data Then contact J.M. for the situs info and property value tables. It is recommended to use [[AveryDB]] to assemble the components, unless/until ESRI improves the process of doing it through their software. =Table Composition= <table bgcolor=white border=.1><tr><td colspan=39>CountyParcels</td></tr> <tr><td>target</td><td bgcolor=#00cc33>OBJECTID_1</td><td bgcolor=#00cc33>OBJECTID</td><td bgcolor=#00cc33>ABSTORSUBN</td><td bgcolor=#00cc33>ABSTORSU_1</td><td bgcolor=#00cc33>PROP_ID</td><td bgcolor=#00cc33>PROP_TYPE_</td><td bgcolor=#00cc33>BLOCK</td><td bgcolor=#00cc33>LOT</td><td bgcolor=#00cc33>LAND_SQFT</td><td bgcolor=#00cc33>LIVINGAREA</td><td bgcolor=#00cc33>EXEMPTION</td><td bgcolor=#00cc33>PROPERTY</td><td bgcolor=#00cc33>SITUS</td><td bgcolor=#00cc33>OWNER_NAME</td><td bgcolor=#00cc33>ADDR_LINE1</td><td bgcolor=#00cc33>ADDR_LINE2</td><td bgcolor=#00cc33>ADDR_LINE3</td><td bgcolor=#00cc33>CITY</td><td bgcolor=#00cc33>STATE</td><td bgcolor=#00cc33>ZIP</td><td bgcolor=#00cc33>LEGAL_DESC</td><td bgcolor=#00cc33>STATE_CD</td><td bgcolor=#00cc33>CD_DESCRIP</td><td bgcolor=#00cc33>TAXENTITY</td><td bgcolor=#00cc33>SITUS_PREF</td><td bgcolor=#00cc33>SITUS_NUM</td><td bgcolor=#ccffcc>SITUS_ST</td><td bgcolor=#00cc33>SITUS_SUFI</td><td bgcolor=#00cc33>YR_BLT</td><td bgcolor=#00cc33>AG_MARKET</td><td bgcolor=#00cc33>APPRAISED_</td><td bgcolor=#00cc33>AG_USE_VAL</td><td bgcolor=#ccffcc>ROLL_ASSD</td><td bgcolor=#ccffcc>T_IMPROVE</td><td bgcolor=#ccffcc>TOTALLAND</td><td bgcolor=#ccffcc>TOTAL_PROP</td><td bgcolor=#00cc33>Shape_area</td><td bgcolor=#00cc33>Shape_len</td></tr> <tr><td></td><td>1</td><td>1</td><td>SL0802A</td><td>THE HIGHLANDS PH 4</td><td>236721</td><td>R</td><td>Z</td><td>12</td><td>13328</td><td>1794</td><td>HS, OV65</td><td>R236721</td><td>2021 WOLF CREEK</td><td>GOURLIE, RONALD A & CONNIE M</td><td></td><td>2021 WOLF CREEK PASS</td><td></td><td>LEWISVILLE</td><td>TX</td><td>75077-7546</td><td>THE HIGHLANDS PH 4 BLK Z LOT 12</td><td>A1</td><td>Single Family</td><td>C12, CAD, G01, S09</td><td></td><td>2021</td><td>WOLF CREEK</td><td>PASS</td><td>2004</td><td>0</td><td>187600</td><td>0</td><td>184232</td><td>137463</td><td>50137</td><td>187600</td><td>13193.84953</td><td>456.78393</td></tr> <tr><td colspan=39>Parcel Shapefile</td></tr> <tr><td>source</td><td bgcolor=#00cc33>OBJECTID_1</td><td bgcolor=#00cc33>OBJECTID</td><td bgcolor=#00cc33>ABSTORSUBN</td><td bgcolor=#00cc33>ABSTORSU_1</td><td bgcolor=#00cc33>PROP_ID</td><td colspan=31><td bgcolor=#00cc33>Shape_area</td><td bgcolor=#00cc33>Shape_len</td></tr> <tr><td colspan=39>DCAD Data</td></tr> <tr><td>join PROP_ID</td><td colspan=4><td bgcolor=#ff3333>PROP_ID</td><td bgcolor=#00cc33>PROP_TYPE</td><td bgcolor=#00cc33>BLOCK</td><td bgcolor=#00cc33>LOT</td><td bgcolor=#00cc33>LAND_SQFT</td><td bgcolor=#00cc33>LIVINGAREA</td><td bgcolor=#00cc33>EXEMPTION</td><td></td><td bgcolor=#00cc33>SITUS</td><td bgcolor=#00cc33>OWNER_NAME</td><td bgcolor=#00cc33>ADDR_LINE1</td><td bgcolor=#00cc33>ADDR_LINE2</td><td bgcolor=#00cc33>ADDR_LINE3</td><td bgcolor=#00cc33>CITY</td><td bgcolor=#00cc33>STATE</td><td bgcolor=#00cc33>ZIP</td><td bgcolor=#00cc33>LEGAL_DESC</td><td bgcolor=#00cc33>STATE_CD</td><td></td><td bgcolor=#00cc33>TAXENTITY</td><td bgcolor=#ff3333>LAND_TYPE</td><td colspan=3><td bgcolor=#00cc33>YR_BLT</td><td colspan=9></td></tr> <tr><td colspan=39>TONYSMIT</td></tr> <tr><td>join PROP_ID</td><td bgcolor=#ff3333>DISPLAY</td><td colspan=3><td bgcolor=#ff3333>PROP_ID</td><td colspan=8></td><td bgcolor=#ff3333>FILE_AS_NA</td><td bgcolor=#ff3333>ADDR_LINE1</td><td bgcolor=#ff3333>ADDR_LINE2</td><td bgcolor=#ff3333>ADDR_LINE3</td><td bgcolor=#ff3333>ADDR_CITY</td><td bgcolor=#ff3333>ADDR_STATE</td><td></td><td bgcolor=#ff3333>LEGAL_DESC</td><td bgcolor=#ff3333>STATE_CD</td><td></td><td bgcolor=#ff3333>ENTITYCODE</td><td bgcolor=#00cc33>SITUS_PREF</td><td bgcolor=#00cc33>SITUS_NUM</td><td bgcolor=#00cc33>SITUS_STRE</td><td bgcolor=#00cc33>SITUS_SUFI</td><td bgcolor=#ff3333>YR_BLT</td><td colspan=9></td></tr> <tr><td colspan=34>VALUES<td bgcolor=#ccffcc>IMPRV_HSTD</td><td bgcolor=#ccffcc>LAND_HSTD_</td></tr> <tr><td>join PROP_ID</td><td colspan=4></td><td bgcolor=#ff3333>PROP_ID</td><td colspan=24></td><td bgcolor=#00cc33>AG_MARKET</td><td bgcolor=#00cc33>APPRAISED_</td><td bgcolor=#00cc33>AG_USE_VAL</td><td bgcolor=#ccffcc>ASSESSED_V</td><td bgcolor=#ccffcc>IMPRV_NON_</td><td bgcolor=#ccffcc>LAND_NON_H</td><td bgcolor=#ccffcc>MARKET</td><td bgcolor=#ff3333>TIMBER_MAR</td><td bgcolor=#ff3333>TIMBER_USE</td></tr> <tr><td colspan=39>state-codes-3</td></tr> <tr><td>join STATE_CD</td><td colspan=21></td><td bgcolor=#ff3333>STATE_CD</td><td bgcolor=#00cc33>CD_DESCRIP</td><td colspan=15></td></tr> <tr><td>Other source</td><td colspan=11></td><td bgcolor=#00cc33>calc from PROP_ID</td><td colspan=26></td></tr> <tr><td>Legend</td><td bgcolor=#00cc33>direct match</td><td bgcolor=#ccffcc>partial match</td><td bgcolor=#ff3333>unneeded</td><td colspan=35></td></tr> </table> T_IMPROVE and TOTTALLAND are calculated by "IMPRV_HSTD + IMPRV_NON_" and "LAND_HSTD_ + LAND_NON_H", respectively. SITUS_STRE is changed to SITUS_ST. PROPERTY is calculated with the following input to Field Calculator: <table border=.1><tr><td>Pre-Logic Script Code:</td></tr> <tr><td> tval = Len ( [PROP_ID] ) if tval > 4 then rval = "R" elseif tval > 3 then rval = "R0" elseif tval > 2 then rval = "R00" else rval = "R000" end if </td></tr> <tr><td>PROPERTY =</td></tr> <tr><td>rval& [PROP_ID]</td></tr> </table> [[Category:Planning]] [[Category:Feature Class]] [[Category:Recurring Projects]]</div>

Dogtaton: <hr /> <div>{{Layer|CountyParcels|gif|Planning|Dec 6, 2012}} The CountyParcels layer is assembled using data from [[DCAD]]. =Components= From [http://www.dentoncad.com/index.php?option=com_docman&task=cat_view&gid=16&Itemid=62 DCADs GIS Downloads page] * Denton County Parcels Map (shapefile) * GIS DCAD Data Then contact J.M. for the situs info and property value tables. =Table Composition= <table bgcolor=white border=.1><tr><td colspan=39>CountyParcels</td></tr> <tr><td>target</td><td bgcolor=#00cc33>OBJECTID_1</td><td bgcolor=#00cc33>OBJECTID</td><td bgcolor=#00cc33>ABSTORSUBN</td><td bgcolor=#00cc33>ABSTORSU_1</td><td bgcolor=#00cc33>PROP_ID</td><td bgcolor=#00cc33>PROP_TYPE_</td><td bgcolor=#00cc33>BLOCK</td><td bgcolor=#00cc33>LOT</td><td bgcolor=#00cc33>LAND_SQFT</td><td bgcolor=#00cc33>LIVINGAREA</td><td bgcolor=#00cc33>EXEMPTION</td><td bgcolor=#00cc33>PROPERTY</td><td bgcolor=#00cc33>SITUS</td><td bgcolor=#00cc33>OWNER_NAME</td><td bgcolor=#00cc33>ADDR_LINE1</td><td bgcolor=#00cc33>ADDR_LINE2</td><td bgcolor=#00cc33>ADDR_LINE3</td><td bgcolor=#00cc33>CITY</td><td bgcolor=#00cc33>STATE</td><td bgcolor=#00cc33>ZIP</td><td bgcolor=#00cc33>LEGAL_DESC</td><td bgcolor=#00cc33>STATE_CD</td><td bgcolor=#00cc33>CD_DESCRIP</td><td bgcolor=#00cc33>TAXENTITY</td><td bgcolor=#00cc33>SITUS_PREF</td><td bgcolor=#00cc33>SITUS_NUM</td><td bgcolor=#ccffcc>SITUS_ST</td><td bgcolor=#00cc33>SITUS_SUFI</td><td bgcolor=#00cc33>YR_BLT</td><td bgcolor=#00cc33>AG_MARKET</td><td bgcolor=#00cc33>APPRAISED_</td><td bgcolor=#00cc33>AG_USE_VAL</td><td bgcolor=#ccffcc>ROLL_ASSD</td><td bgcolor=#ccffcc>T_IMPROVE</td><td bgcolor=#ccffcc>TOTALLAND</td><td bgcolor=#ccffcc>TOTAL_PROP</td><td bgcolor=#00cc33>Shape_area</td><td bgcolor=#00cc33>Shape_len</td></tr> <tr><td></td><td>1</td><td>1</td><td>SL0802A</td><td>THE HIGHLANDS PH 4</td><td>236721</td><td>R</td><td>Z</td><td>12</td><td>13328</td><td>1794</td><td>HS, OV65</td><td>R236721</td><td>2021 WOLF CREEK</td><td>GOURLIE, RONALD A & CONNIE M</td><td></td><td>2021 WOLF CREEK PASS</td><td></td><td>LEWISVILLE</td><td>TX</td><td>75077-7546</td><td>THE HIGHLANDS PH 4 BLK Z LOT 12</td><td>A1</td><td>Single Family</td><td>C12, CAD, G01, S09</td><td></td><td>2021</td><td>WOLF CREEK</td><td>PASS</td><td>2004</td><td>0</td><td>187600</td><td>0</td><td>184232</td><td>137463</td><td>50137</td><td>187600</td><td>13193.84953</td><td>456.78393</td></tr> <tr><td colspan=39>Parcel Shapefile</td></tr> <tr><td>source</td><td bgcolor=#00cc33>OBJECTID_1</td><td bgcolor=#00cc33>OBJECTID</td><td bgcolor=#00cc33>ABSTORSUBN</td><td bgcolor=#00cc33>ABSTORSU_1</td><td bgcolor=#00cc33>PROP_ID</td><td colspan=31><td bgcolor=#00cc33>Shape_area</td><td bgcolor=#00cc33>Shape_len</td></tr> <tr><td colspan=39>DCAD Data</td></tr> <tr><td>join PROP_ID</td><td colspan=4><td bgcolor=#ff3333>PROP_ID</td><td bgcolor=#00cc33>PROP_TYPE</td><td bgcolor=#00cc33>BLOCK</td><td bgcolor=#00cc33>LOT</td><td bgcolor=#00cc33>LAND_SQFT</td><td bgcolor=#00cc33>LIVINGAREA</td><td bgcolor=#00cc33>EXEMPTION</td><td></td><td bgcolor=#00cc33>SITUS</td><td bgcolor=#00cc33>OWNER_NAME</td><td bgcolor=#00cc33>ADDR_LINE1</td><td bgcolor=#00cc33>ADDR_LINE2</td><td bgcolor=#00cc33>ADDR_LINE3</td><td bgcolor=#00cc33>CITY</td><td bgcolor=#00cc33>STATE</td><td bgcolor=#00cc33>ZIP</td><td bgcolor=#00cc33>LEGAL_DESC</td><td bgcolor=#00cc33>STATE_CD</td><td></td><td bgcolor=#00cc33>TAXENTITY</td><td bgcolor=#ff3333>LAND_TYPE</td><td colspan=3><td bgcolor=#00cc33>YR_BLT</td><td colspan=9></td></tr> <tr><td colspan=39>TONYSMIT</td></tr> <tr><td>join PROP_ID</td><td bgcolor=#ff3333>DISPLAY</td><td colspan=3><td bgcolor=#ff3333>PROP_ID</td><td colspan=8></td><td bgcolor=#ff3333>FILE_AS_NA</td><td bgcolor=#ff3333>ADDR_LINE1</td><td bgcolor=#ff3333>ADDR_LINE2</td><td bgcolor=#ff3333>ADDR_LINE3</td><td bgcolor=#ff3333>ADDR_CITY</td><td bgcolor=#ff3333>ADDR_STATE</td><td></td><td bgcolor=#ff3333>LEGAL_DESC</td><td bgcolor=#ff3333>STATE_CD</td><td></td><td bgcolor=#ff3333>ENTITYCODE</td><td bgcolor=#00cc33>SITUS_PREF</td><td bgcolor=#00cc33>SITUS_NUM</td><td bgcolor=#00cc33>SITUS_STRE</td><td bgcolor=#00cc33>SITUS_SUFI</td><td bgcolor=#ff3333>YR_BLT</td><td colspan=9></td></tr> <tr><td colspan=34>VALUES<td bgcolor=#ccffcc>IMPRV_HSTD</td><td bgcolor=#ccffcc>LAND_HSTD_</td></tr> <tr><td>join PROP_ID</td><td colspan=4></td><td bgcolor=#ff3333>PROP_ID</td><td colspan=24></td><td bgcolor=#00cc33>AG_MARKET</td><td bgcolor=#00cc33>APPRAISED_</td><td bgcolor=#00cc33>AG_USE_VAL</td><td bgcolor=#ccffcc>ASSESSED_V</td><td bgcolor=#ccffcc>IMPRV_NON_</td><td bgcolor=#ccffcc>LAND_NON_H</td><td bgcolor=#ccffcc>MARKET</td><td bgcolor=#ff3333>TIMBER_MAR</td><td bgcolor=#ff3333>TIMBER_USE</td></tr> <tr><td colspan=39>state-codes-3</td></tr> <tr><td>join STATE_CD</td><td colspan=21></td><td bgcolor=#ff3333>STATE_CD</td><td bgcolor=#00cc33>CD_DESCRIP</td><td colspan=15></td></tr> <tr><td>Other source</td><td colspan=11></td><td bgcolor=#00cc33>calc from PROP_ID</td><td colspan=26></td></tr> <tr><td>Legend</td><td bgcolor=#00cc33>direct match</td><td bgcolor=#ccffcc>partial match</td><td bgcolor=#ff3333>unneeded</td><td colspan=35></td></tr> </table> T_IMPROVE and TOTTALLAND are calculated by "IMPRV_HSTD + IMPRV_NON_" and "LAND_HSTD_ + LAND_NON_H", respectively. SITUS_STRE is changed to SITUS_ST. PROPERTY is calculated with the following input to Field Calculator: <table border=.1><tr><td>Pre-Logic Script Code:</td></tr> <tr><td> tval = Len ( [PROP_ID] ) if tval > 4 then rval = "R" elseif tval > 3 then rval = "R0" elseif tval > 2 then rval = "R00" else rval = "R000" end if </td></tr> <tr><td>PROPERTY =</td></tr> <tr><td>rval& [PROP_ID]</td></tr> </table> [[Category:Planning]] [[Category:Feature Class]] [[Category:Recurring Projects]]</div>

Dogtaton: <hr /> <div>Zip codes within Denton county. [[Category:CityBoundaries]] [[Category:Feature Class]]</div>

Dogtaton: <hr /> <div>Local voting districts within city limits. [[Category:CityBoundaries]] [[Category:Feature Class]]</div>

Dogtaton: <hr /> <div>Voting precincts across the county ==Fields== *VOTE_, VOTE_ID: Probably leftover ID fields. No meaning *CONGRESS: Federal Congressional district *SENATE State Senate district *HSE_REP: State House of Representatives district *ED_DIST: Texas State Board of Education district *COMMISH: County Commissioners Court precinct *JP_C: Justice of the Peace precinct *POLL_SITE: Name of polling location *BOUNDARY_D: Link to pdf showing boundary. Link is to a local drive (presumably at the county) and not accessible *Temp_Prec_: May relate to the recent redistricting process which wasn't resolved in time for the 2012 election *Prec_N: same *Prec_N_1: same *PRECINCT_N: Local voting precinct *Precinct: same as PRECINCT_N except 5 records are unattributed and 1 is different *PRECINCT_1: same as PRECINCT_N except 4 records are unattributed and 1 is different (value matches Precinct's) *Small: Y or N. uncertain criteria *Reg_Voters: Total registered voters in the precinct *Early_[R|D|L|G]: Early votes for [republican|democrat|libertarian|green] *Election_[R|D|L|G]: Election day votes for [republican|democrat|libertarian|green] *Absentee_[R|D|L|G]: Absentee votes for [republican|democrat|libertarian|green] *Total_[R|D|L|G]: Total votes for [republican|democrat|libertarian|green] *Total: Total votes cast [[Category:Feature Class]] [[Category:CityBoundaries]]</div>

Dogtaton: <hr /> <div>Vacant lots is created by using the following selection query on [[CountyParcels]]: <blockquote>STATE_CD = 'C1' OR STATE_CD = 'C2' OR STATE_CD = 'C3' OR STATE_CD = 'C5' OR STATE_CD = 'OC1' OR STATE_CD = 'OC2' OR STATE_CD = 'OC3' OR STATE_CD = 'OC5'</blockquote> Then export the selected features to a gdb. From there, Tony will load them in to the database when it's convenient. This should be done once or twice a year after creating an updated county parcels. Code Enforcement uses this layer. Last updated June 26, 2015 [[Category:Planning]] [[Category:Feature Class]] [[Category:Recurring Projects]]</div>

Dogtaton: <hr /> <div>Subdivisions is created by dissolving [[CountyParcels]] on ABSTORSUBN and ABSTORSU_1. ABSTORSU_1 is then renamed to SUBD_NAME. This should be done once or twice a year using a newly updated county parcels. Alternately, you can dissolve on ABSTORSUBN alone and then join it back to get ABSTORSU_1/SUBD_NAME. Some subdivision numbers will have multiple values for the subdivision name. Sometimes it's a punctuation or spacing difference and sometimes they're completely different. That's the reason for dissolving on only the number and then joining it back. It takes a bit more time to do the extra joining and field editing but then you don't need to manually check for discrepancies in the names. Last full update: June 26, 2015 [[Category:Planning]] [[Category:Feature Class]] [[Category:Recurring Projects]]</div>

Dogtaton: <hr /> <div>Annexations from 1998 onwards. [[Category:CityBoundaries]] [[Category:Feature Class]]</div>

Dogtaton