Export data

[adrian-lara]

Blocked by Sequelize connection and schema built.

Design is needed here.

What data will be exported, and in what format(s)?

The original plan was to either:

• export 2 CSV files, one with property data & one with tax lot data. The property file will have "Jurisdiction Tax Lot ID" or some other field that identifies tax lot pairing(s).
• export 1 CSV file with each row representing a property and tax lot data pairing

This could have changed since work began.

[adrian-lara]

After some consideration, I'm thinking it would be appropriate to scope this down to 2 export files in geojson format - 1 for property data and 1 for tax lot data, each without UBID or ULID populated but the property data has parcel_number appended if available.

Considerations and reasoning is as follows:

• It was fairly straightforward to run a raw SQL query to append parcel_number to property records after a LEFT JOIN.
• Enabling filtering, say, on square footage, would first require that we find data that has square footage on properties. Easily accessible (i.e. I can easily scope it down for Seedling to manage) public data with square footage and and footprints for both properties and tax lots is a bit harder to find.
• Getting UBID and ULIDs from footprints takes non-negligible effort.
• Even though the outputs will be largely similar to the inputs, the example files should serve as a suitable example/talking point when Seedling and some example files are shared with users