My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
2006-193A.
CBCC
>
Official Documents
>
2000's
>
2006
>
2006-193A.
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/27/2017 1:55:21 PM
Creation date
10/1/2015 12:14:26 AM
Metadata
Fields
Template:
Official Documents
Official Document Type
Plan
Approved Date
06/06/2006
Control Number
2006-193A.
Agenda Item Number
10.A.
Entity Name
Geographic Technologies Group
Subject
three year implementaion plan and assessment
GIS Geographic Information System
Supplemental fields
SmeadsoftID
7366
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
41
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
10 foot <br /> offset <br /> 50 foot offsets <br /> Depending on address - matching logic used during geocoding, an <br /> address interpolated near an intersection (or sheet segment end) <br /> will be placed at a different offset. If the specified 50 foot offset <br /> were to be used in this case, the address point would be placed <br /> near the end of the line segment and offset by 50 feet, thereby <br /> placing the point close to the middle of the intersecting street. <br /> Other limitations of geocoding include the interpolation logic used for address matching . <br /> Interpolated addresses are subject to address matching rules, which in some instances may <br /> place a point within a block group centroid , or even within a Zip Code centroid , if address <br /> information is ambiguous and/or incomplete . For example, if a record does not have all <br /> n relevant address information , such as an incomplete street number or a misspelled street <br /> name , that record may be geocoded to a Zip Code centroid . <br /> The following describes the suggested methodology for creating a master address point <br /> layer for the County . <br /> F Phase 1 <br /> Creation of Master Address Database <br /> Two alternatives exist for this phase : <br /> 1 . Indian River County has an MSAG database in the Emergency Services <br /> Department, which is used for E911 purposes . If this database stores specific <br /> information about the address such as house number, street name, street <br /> type, and street direction , then it can be used as a reference for the <br /> geocoding of addresses . <br /> 2. If, however, the MSAG database lacks this information , another database <br /> within the County should be used in conjunction with the existing parcel layer <br /> as a base listing of all the addresses in the County ( e . g . , utility billing <br /> database) . The creation of a master address database will provide a <br /> resource for geocoding addresses and for the field verification phase . Once <br /> all data sources are collected , the geocoding phase can begin . <br /> Geocodina of Addresses <br /> Once the addresses that need to be generated on the map are determined , the <br /> cumulative physical address field in the database can be address matched ( also <br /> known as geocoded ) against the attributed street centerline file . The database and <br /> centerline file should be processed through the ArcGIS 9 Geocoding Service in <br /> ArcCatalog . <br /> 4- 14 <br /> GIS Needs Assessment and Implementation Plan Chapter 4 - Base Map Creation and Consideration <br />
The URL can be used to link to this page
Your browser does not support the video tag.