initial naive structure for at_published_ts

[adamkorynta]

TODO:

• determine migration script and/or data sync trigger between old table and new
• determine backwards compatibility for old views
• decide if the notion of "TS_TYPE" needs to be carried forward
• determine support for ratings, notes, date-refreshed, etc

[MikeNeilson]

not sure you could, ..._STORE_FLOOD, etc are Location level identifiers.

That not all projects would have. Given it's different data, you might want to approach more of a star pattern (e.g. > 3rd normal)

at_publish holding the root location and possibly (maybe in the future) other meta data, and then a table for pure time series, and another for "levels".

One generally assigns the location level, not time series, those those anyways.