Are there any best practice / advice on storing multiple temporal attributes in geodatabases (SQL or file)?
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?