Improve related address matching/tag assignment

[bertday]

Currently the address_link table is only being used to 1) return the match_type in the API and 2) to do some merging of unit siblings in make_address_summary. Using it more robustly in both the engine and the API could resolve a few open issues around address matching and attribute assignment (see #2, #6, #7, #9, #74).

Objectives

• [x] Child addresses should be assigned "linked" address tags from the nearest parent with a good value for that tag. Test: 621 REED ST APT 2R should get a DOR parcel ID of 009S190092 from 621-25 REED ST via path 621 REED ST APT 2R has_base 621 REED ST in_range 621-25 REED ST.
• [x] Ranged addresses should use linked tags to get values from other overlapping ranges. Test: 921-29 E LYCOMING ST should return an OPA account of 777247710 from 921-39 E LYCOMING ST via path 921-29 E LYCOMING ST overlaps 921-39 E LYCOMING ST.
• [x] In the API, return complete set of related addresses by traversing address links in both parent => child and child => parent directions. Test: 1708 CHESTNUT ST is a condo building without an OPA address, but it should return two children with accounts: 1708-14 CHESTNUT #A and #B.
• [x] Given an unknown address, find the nearest relative and return data for that address. Test: made-up address 621 REED ST APT 2000 get a DOR parcel ID of 009S190092 from 621-25 REED ST via path 621 REED ST APT 2000 has_base 621 REED ST in_range 621-25 REED ST.

Project Outline

• [x] 1. Make sure all necessary relationships are being added to address_link during load_addresses. Add any that are missing.
• [x] 2. Create a new undirected address link type overlaps for ranges that intersect, e.g. 1708-10 and 1708-14.
• [x] 3. Add linked_address and linked_path fields to address_tag table.
• [x] 4. Add an attribute traverse_links to tag fields in config.py to designate if they should be inherited from parents or not.
• [x] 5. Write script make_linked_tags to calculate and store linked tag values.
• [x] 6. Modify API view to query and serialize address_tag values instead of address_summary.
• [x] 7. Run data integrity and performance tests to make sure this approach is working.
• [ ] 8. Deprecate address_property and address_parcel tables.

[bertday]

Mocked up API response with path-like match_type:

https://gist.github.com/rbrtmrtn/88c07f22d4e46e3d68c08621efd0d172

[bertday]

For step 1, we should make sure:

• [x] Ranges have all children split out into single addresses.
• [x] All unit addresses have a base address.

[bertday]

Query to select in range address links missing children:

select * from 
    (select 
        a.street_address,
        a.address_low,
        a.address_high,

        (a.address_high - a.address_low) / 2 + 1 as expected,
        al.count as actual,
        (al.count = (ceil((a.address_high - a.address_low) / 2) + 1)) as enough,
        ((a.address_high - a.address_low) / 2 + 1) - al.count as missing
    from address a
    join (select address_2, count(*) from address_link where relationship = 'in range' group by address_2) al
    on a.street_address = al.address_2
    ) b
where b.enough = false
order by b.missing desc