AnsweredAssumed Answered

Advice on Storing Multiple Temporal/Time-Aware Attributes

Question asked by henry@ame on Aug 9, 2016
Latest reply on Aug 15, 2016 by Dan_Patterson

Are there any best practice / advice on storing multiple temporal attributes in geodatabases (SQL or file)?


We have a feature class that have multiple attributes that change over time. For example, a "Cities" feature class can have attributes of "Population Size", "Pollution", "Accident Counts"... etc that change over time (per year). We want to show the attribute changes over time as a time-aware layer in ArcMap and a JavaScript API app.


What would be the best way of storing such information? So I will have a "Cities" feature class. Should I have separate tables such as "CitiesPopulationSize" and "CitiesAccidentCounts", or should I use one single table storing all the time-based attributes? We can have many time-aware attributes for the several feature classes.


Anyone got any ideas/experience with this?