Database Management Issues of interest to Address Databases. Database Overview Agenda. Database Components Example Data Types Table Indexes Domains Joins and Views Foreign and Primary Keys. Database Components. A database is the sum of all information you have obtained. Database.
A database is the sum of all information you have obtained.
Stores a maximum of 240 ASCII characters.
Stores an integer in a range -2,147,483,648 to 2,147,483,647
Stores an integer value in the range -32,768 to 32,767
Stores a real value in double precision floating point format
Stores a real number value as a single precision floating point
Stores a fixed point decimal number with a optional precision and scale
Stores a timestamp with ‘yyyy-mm-dd:hh:mm:ss’ format
Just Call them the “Record ID’s”
in a Database Table...
Essentially the “Linkage Columns”
between Database Tables...
CAD Graphics Table
“Old” DB Table ID
CAD File Graphics
record ID in “Old” Table
DMRS 8000 0004 0005 0000
DMRS 8000 0022 0014 0000
The Database software will interpret the
“old linkage code” to determine what table the
graphic elements “points” to.
CAD File Graphics
Segment TableJoining Tables (DBMS)
Foreign Keys in each
table are used to complete
the Join Relationships from
Table to Table.
Street Name Table
Segment TableJoining Tables (example)
Master Address File
Specific data entry recommendations include:
1) Zip code entry first, with automatic fill of State and (optionally) locality data.
2) Support on-line entry with help screens, pop-up valid values access, and immediate edits.
3) Secondary unit data entry separate from street address (optionally before street for emphasis).
4) Addresses entered with manual overrides of edits should be flagged for future review.
5) Allow search for Zip code given City and State (optional).
Several types and levels of edits may be practical, depending on circumstances and business purpose.
1) Check entered data for valid abbreviations. (Abbreviation standards used by the USPS are included in Appendix B.)
2) Compare entered location(City) and State to Zipcode (based on GCS or equivalent table information).
3) Check Zipcode for validity (based on GCS or equivalent table information).
4) Compare entered address against valid addresses: Against an existing database containing addresses (within the enterprise)
5) Verify and correct the standard use of state code, standard spelling for city; and presence of standard street type.
6) Inspect Street numbers that seem to represent ranges of addresses, such as street numbers in a range or the use of terms such as "scattered sites". (This only applies for those applications that receive addresses representing, for example, blocks of apartments).
7) Identify and correct building name substitutions for street addresses to the extent possible. Using COTS software modules, against a postal-service database of 140 million valid addresses.
8) If County Code is missing, generate County Code.
9) Identify where range of latitude or longitude is more than 5 miles. Inspect and correct.
(This is a way to measure if the geocoding center is of a Zip code, rather than to a specific street address. This is unnecessary if the geocoding level is specified in a code, as is recommended).
10) Identify and delete official verbiage. For example: "Township of", "The Commonwealth of", "The Great State of".
11) Comma Check. The USPS recommends not using commas or other dividers within addresses, except the hyphen in Zip+4. The USPS further recommends all capital letters, to aid machine readability.
12) Enforce Business Rules.
For example, it may be a rule that P.O. Box numbers (and equivalent) may not substitute for Street names (and equivalent) if the address is for a property in which the enterprise holds an interest (as opposed to the mailing address of an individual or organization).
X, Y coords. from DB
from graphics to the database!Database Loading Tools useful for enhancing your GBF data.