Overview...
| Stage Number | Stage | Category | Summary | Environment | Iterations | Estimated Person Time | Estimated Computer Time |
|---|
| 1 | Import and parse reference dataset (Optional) | Parsing | This optional step in the Bulk Loader process is to cross check an address for a match in a reference data set. If a source address is found in the reference dataset the address makes it to the next step. If not found the address is put aside in an exclusion set for later review. | Python 3 PostgreSQL / pgAdmin | Once per Bulk Loader process | 1 hour | 10 minutes |
| 2 | Import, parse and filter source dataset | Parsing | Import the dataset destined for the EAS. Parse and filter the set. | Python 3 PostgreSQL / pgAdmin | Once per Bulk Loader process | 90 minutes | 15 minutes |
3 | Geocode and filter | Geocoding | Geocode the set and filter further based on the geocoder score and status. | ArcMap | Once per Bulk Loader process | 1 hour | 5 minutes |
| 4 | Export full set (single batch) or subset (multiple batches) | Geocoding | For large datasets, create one of many subsets that will be run through the Bulk Loader in multiple batches. | ArcMap | One or more batches for each Bulk Loader process | 30 minutes per batch | 5 minutes per batch |
| 5 | Bulk Load batch (full set or subset) | Bulk Loading | Run the entire batch or each subset batch through the Bulk Loader. | EAS <environment>(+) PostgreSQL / pgAdmin | One or more batches for each Bulk Loader process | 1 hour per batch | 5 minutes per batch |
| 6 | Extract results | Bulk Loading | Extract and archive the list of addresses that were added to the EAS . Also archive the unique EAS 'change request id' associated with this batch. Also archive the addresses that were rejected by the Bulk Loader in this batch. | PostgreSQL / pgAdmin | One or more batches for each Bulk Loader process | 1 hour per batch | 5 minutes per batch |
| 7 | Cleanup and Restoration | Bulk Loading | Clean up database, restore services and in the event of a failure, restore from backup. | PostgreSQL / pgAdmin | One or more batches for each Bulk Loader process | 1 hour per batch | 5 minutes per batch |
...
| Warning |
|---|
|
When releasing in the production environment pick a time outside core work hours that does not conflict with any cron jobs running on the production server. |
Suggested folder layout
Artifacts are generated throughout the stages of the Bulk Loader Process. Below is a suggested folder and file layout for the various artifacts.
| Info |
|---|
| title | Folder and file layout for artifacts collected |
|---|
|
./ # root (YYYYMMDD-tag e.g. 20190510-3x10k)
./gap # Artifacts from the General Address Parser stage
./geocoder # input csv and output shapefiles
./bulkload_001 # artifacts from the first batch
./bulkload_00N # artifacts from the Nth batch, if any
./excluded_records # records from all stages set aside for later review
./excluded_records/gap
./excluded_records/geocoder
./excluded_records/bulkload_001
./excluded_records/bulkload_00N |
Details for each Bulk Loader StageStage 1 -
Import and parse reference dataset (Optional) This optional stage is run once per Bulk Loader process. This stage can be skipped if the reference dataset is already available or if the optional 'filter by reference' step (Step 2.5) is skipped.
...
Stage 3 - Geocode and filter
-
Step 3.1 - Geocode source dataset
...
Stage 4 - Export full set (single batch) or subset (multiple batches)
| Note |
|---|
| title | A note about batches |
|---|
|
Stages 4, 5 and 6 can be run one time with the results from Stage 3, or they can be run in multiple batches of subsets. A major consideration of when to run the full set at once versus in batches is the number of records being Bulk Loaded. The size of each Bulk Loader operation affects the following aspects of the EAS: - The disk space consumed by the database server
- The EAS user interface section that lists addresses loaded in a given Bulk Loader operation
- The weekly email attachment listing new addresses added to the EAS
For medium-to-large datasets (input sets with over 1,000 records) it is recommended that the process first be run on a development server to assess the implications of the operation. Where appropriate, perform the Bulk Loading process in batches over several days or weeks. The remaining steps will document a single batch example iteration of a multi-batch process. |
...
Stage 5 - Run the Bulk Loader
For a complete set of steps and background about the Bulk Loader, see also Running the Bulk Loader, a page dedicated to its input, operation and results.
...
-
Step 6.1 - Archive exceptions
...
- If the Bulk Loader Process was run on the production server then restore services
Turn on production-to-replication service
Turn on downstream database propagation service(s)
Enable front-end access to EAS
...