Boston code enforcement data gets messy fast

[Dominic Mazzarella]

The first problem with Boston code enforcement data is that the raw list is huge.

One export had 5,519 properties with open code issues. Almost half had only 1 open case.

The more useful cut was smaller:

2,753 had 2+ open cases
1,368 had 3+ open cases
512 had 5+ open cases
123 had 10+ open cases

Dorchester had the most volume in the pull, followed by Boston proper, Roxbury, Brighton, South Boston, and East Boston.

For sourcing, I’d rather start with the smaller group of properties showing multiple open issues than try to work a giant raw code list.

Volume is nice, but a huge list with no prioritization just creates another calling problem. Thoughts?