Set up a DynamoDB instance

[gordonje]

For storing election night, as well as historic data.

[NathanLawrence]

Set up table "StateGeo" on Access Missouri's AWS.

Fields:

• year (mandatory, Partition Key) - The year the data was relevant for.
• divisions (mandatory, Sort Key) - The kind of division the topography draws, for example "counties," "municipalities"
• topo (optional, AttributeValue flex type) - TopoJSON version of the object, if applicable.
• geo (optional, AttributeValue flex type) - GeoJSON version of the object, if applicable.

[NathanLawrence]

Set up table "CountyGeo" on Access Missouri's AWS.

Fields:

• year (mandatory, Partition Key) - The year the data was relevant for.
• county (mandatory, Sort Key) - The county name: I'm thinking we'll use the same name formatting as the field named "NAMELSAD" in @gordonje's converted USGS TopoJSON file.
• geo (optional, AttributeValue flex type) - GeoJSON version of the object, if applicable.
• topo (optional, AttributeValue flex type) - TopoJSON version of the object, if applicable. (But it won't be. Because there can't be shared topology in singular objects. I just wanted to write this in to emphasize that all these objects are more or less structured the same way.)

[NathanLawrence]

Proposed structure of the live elections data table:

• race (mandatory, Partition Key) - Race name, which we'll define standards for together.
• time (mandatory, Sort Key) - Time data was pulled and created, which we'll also choose conventions for together.
  ...and other stuff?