Open NealHumphrey opened 6 years ago
This list is a good sampling of different reasons addresses might not match the MAR. A few examples:
Also: through our online application system we now collect information in a table about every address/SSL covered by the project. If I recall correctly, the first address listed is what gets pushed into the Pipeline App when a project is selected and moves from the Financing Application app (private) into the Pipeline App (Public). That seems like it should work fine for the purposes of this tool, but if you have ideas about how we could better take advantage of that data we are collecting we'd be happy to hear it.
@ChrisDickersinProkopp Thanks for the info - sounds like these are more complicated than I thought it would be for these cases.
The biggest way this is used currently is de-duplication of projects that are already in the PresCat for whatever reason. If we can use the table of every address/SSL that would definitely be an improvement. It would be good to get more info on where to access that data table.
For now let's mostly save this response for a more comprehensive review of the matching. A few quick notes though:
If it's a new development and doesn't have an address, we can use the intersection address as is. Would be great to get it updated when it does come through, though, so we can take advantage of the extra data that comes with matching w/ the mar id
It probably makes sense to add a 'won't fix' flag to anything that we think is too much effort to fix. Will think about where best to put this.
We also have a one-to-many project to address table, so the cleanest way is to get the list of all the addresses that ended up being created. But might be worth discussing if this is feasible.
We opted not to use the intersection-based MAR address lookup because it returned too many false positives. If there was a mistyped address or other error, it would say it was close enough and return a (wrong) MAR ID anyways. Using just the street address version was safer. If there are many cases that need intersections, we would need to add code in our side that could correctly identify an intersection-style address and only send those ones to the intersection-based MAR lookup.
Some of the addresses in the DHCD quickbase database that are being ingested into Housing Insights are not found in the Master Address Repository; typically this is because of an invalid address.
Solution steps:
Addresses: (Note - these have been pre-precessed by our code to split up different addresses so will be slightly different in the DHCD database)