Select to view content in your preferred language

How to store historic or archived data.

08-04-2022 09:21 AM
by Anonymous User
Not applicable

I have a group that has a boundary feature that they update on an annual basis. These boundaries are used to determine permits and applications for that year. I am wondering how to make an authoritative dataset for this type of data, that changes on an annual basis, but previous versions of the data are still relevant. I would like to maintain the most current boundary on Enterprise, and have that published and available publicly, but am not sure I want to be maintaining multiple very similar boundaries.

How do other organizations handle and organize data of this nature? Currently we have file geodatabases in "archival" folders that are read only to hold the previous iterations of the data, with the newest boundary being saved on Enterprise.

0 Kudos
3 Replies
MVP Esteemed Contributor

I would consider using a Parcel Fabric dataset. It has built-in capabilities for tracking historic changes, and makes it very easy to create an attribute-based filter to only show current features. It's meant more for cadastral boundaries, but there's no reason you couldn't use it for something a bit more general.

- Josh Carlson
Kendall County GIS
0 Kudos
New Contributor III

If you have access to a maintenance account you could explore the archiving workflows shown in this web course:


0 Kudos
Esri Contributor