Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Overview

This page lists various types of address input scenarios that the Bulk Loader can encounter.

TODO: This table currently assumes empty block/lot values are submitted. Extend this table to include combinations of possible scenarios such as valid block/lot values; invalid values; same block/lot as EAS; different block/lot than EAS; etc.

Initial Table Form


Base Address ScenarioInput ScenarioInput GeometryExampleCurrent Bulk Loader BehaviorDesired Changes to Bulk Loader BehaviorNotes
A.Base address does not exist in EASAddress with no unitsValid (within N-foot threshold)



B.Base address does not exist in EASAddress with one unitValid



C.Base address does not exist in EASAddress with two+ unitsValid



D.

Base address does not exist in EAS

Address with no unitsInvalid (exceeds N-foot threshold)



E.Base address does not exist in EASAddress with no unitsInvalid or None



F.

Base address exists, but does not have any units

Address with no unitsValid105 10TH AVEIgnored record.New status column with value indicating that the record was ignored because it already exists.See Example 1
G.

Base address exists, but does not have any units

Address with one unitValid1377 03RD AVE 1337VAdded unit (no parcel association). Set default status/disposition value to 'official' (vs the other possible value: 'provisional').Populate new status column accordingly. (Also, maybe set status/disposition to a value other than 'official'.)See Example 2
H.

Base address exists, but does not have any units

Address with two+ unitsValid



I.

Base address exists, but does not have any units

Address with no unitsInvalid or None



J.

Base address exists and has existing unit(s)

Address with no units

Valid





K.

Base address exists and has existing unit(s)

Address with one unit that does not exists in EAS

Valid





L.

Base address exists and has existing unit(s)

Address with one unit that does exists in EAS

Valid





M.

Base address exists and has existing unit(s)

Address with two+ units where some but not all exist in EAS

Valid





N.

Other ScenariosInput address uses valid street name aliasValid



O.Other ScenariosInput address exists as a retired addressValid



P.Other ScenariosStatus/Disposition considerations




Q.

Other ScenariosConsiderations for dataset details ("More" tab in UI)




Truth Table Form


ROW
BULK LOADER INPUT FIELDS


SCENARIO


OUTCOME


EXCEPTION TEXT

st_numst_num_sfxst_pfxst_namest_typest_sfxunitunit_sfxblocklotsourceshape
1NULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLN/ANull record.

2any valueNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLN/AOnly the Complete Street Number was submitted.

3NULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNull record.

4any valueNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLNULLOnly the Complete Street Number was submitted.

Examples

Example 1 Scenario F. 105 10TH AVE: Input address with no units. Base address exists, but does not have any units.

Input address was ignored. No changes made.


Example 2 Scenario G. 1377 03RD AVE 1337V: Input address and unit. Base address exists, but does not have any units.

Unit was added. 'More' tab reflects last change.

Section X

Filter by label

There are no items with the selected labels at this time.



  • No labels