Since this project is moving forward so quickly (hooray!) I just want to reiterate an idea that I think I mentioned early on:

Is BIP data going to be stored as one table within the Civi DB (on the same level as tables like civi_address ... civi_contact ... etc.)? In browsing the PHP pages I wasn't sure. I hope so. BIP sends us new data 4 times per year as an XLSX file, and when they do, I hope to be able to upload the new XLSX and overwrite the old table. Thank you!

@clhenrick hey can you set up a new repo to host the BIP import civix extension? Want to keep it separate from the geocoding one.

@agirlnamedsophia if the BIP data must be converted to CSV prior to importing it to CiviCRM each quarter it would be helpful to have a script that converts the Excel file to a CSV.

Or does CiviCRM accept xls & xlsx files for data importing?

• list Sophia & Jon as authors
• mention support from the New School / New Challenge
• add license (MIT?)

Via @PalanteJon

Two notes I found during testing:

• If you disable the NYC Geocoder extension, but do not change your Geocoder to NOT be the NYC Geocoder extension, Civi will crash when the geocoder is called with "Geocoder not found". This shouldn't affect normal usage, of course, but heads up!
• When importing, I'm not sure why, but even if you don't check the "geocode imported contacts" box, they're still geocoded. To import some test addresses WITHOUT geocoding them so I could test the batch geocoder, I had to disable the extension temporarily.

BIP's fields are abbreviated and not very human readable. We need to change the "label" attribute for each field to be their human readable representation inxml/auto_install.xml. I don't mind doing this.

@danieljweinberg do you have metadata for BIP that spells out which each field is? I want to make sure I'm not guessing and that the labels are correct in CiviCRM.