Release doctor-visits geo refactor

[krivard]

• Link to PR
• Proposed release version: None; soon

This is another one just like #357:

We went from a custom geo mapping file (for aggregating from (source geo TBD)->(county, hrr, msa, state)) to a central geo file based on rigorously sourced US census data.

Date of change is TBD; should be imminent. @mariajahja can confirm what day the changes were / will first be run in production.

@chinandrew are there any specific changes (eg these) we should mention in the API docs changelog or mailing list notification?

• API documentation and/or changelog
• API mailing list notification

[chinandrew]

Doesn't hurt to mention we updated our geo mapping files for our indicators which may have very minor effects going forward, unless we think it'll add a bunch of unnecessary confusion

[mariajahja]

Just updated bigchunk-dev-03.delphi.cmu.edu, which runs the cron job to use the latest dv-package branch. New versions should be released tonight around 6:30p ET, unless any hiccups occur.

[krivard]

@chinandrew the standard message for these geo refactors has been brief; sounds like you don't think anything beyond that is necessary. 👍

[chinandrew]

@chinandrew the standard message for these geo refactors has been brief; sounds like you don't think anything beyond that is necessary.

lgtm

[krivard]

Mailing list notification went out this afternoon.

[chinandrew]

isn't this kind of dependent on #502 ("kind" of in the sense that it is refactored, but buggy?)