History/Record of edits in ESRI - Ideas for maintaining a sacred timeline. (edited)
Image by Freepik

History/Record of edits in ESRI - Ideas for maintaining a sacred timeline. (edited)

The question quoted below is from Amy Roust, GISP also tagging Cody M. Erwin as mentioned in the comments he is curious about the answer also. You can find a link to the post from Amy below please give her original post and the comments a read also. I wanted to do this article to have enough room to expand beyond what a simple comment allows. I will pick up below the quote:

I've got a few projects that involve collecting "snapshots" of the official record every year. As an example, we're looking to track changes in zoning districts over time. How do you handle historical spatial data? One feature class with definition queries? One feature class for each year? I'm looking for pros and cons.

These types of workflows and questions are quite common. Kudos to Amy for asking the question without worry as to how it might be looked upon by others. Simply put there is no "this is always the best way to do this" answer. What I will give here are some basic guidelines for how to build out a blueprint for not just this workflow but others you may need. I will also highlight the differences when working between ArcMap and ArcPRO. I will be using links throughout the rest of the writing and ask you to please use them to get a deeper understanding of the topics under discussion here. This is not intended to be a step by step guide. Rather I hope to get you thinking about the tools available and how to apply them to the work needed completed and the workers who will be completing that work.

Initial assumptions:

1) - you have an enterprise deployment of ESRI software

2) - You have a need to track and report historical edits to your data

3) - you have a desire to learn and grow and a good understanding of the work processes and questions needed answered

FOR ALL ENTERPRISE USERS:

Step one: Turn on Temporal data - see the link from the 2018 Arcuser article here - Working with Temporal Data.

As you will learn turning on temporal data will track the history of changes. You will not have to have someone remembering to take that snapshot before starting to edit. The article gives a great overview of using temporal data and applying it to your work. ESRI help documentation will cover the rest. I am also available to help explain and walk you through examples of how it might work if you need further assistance.

Step two: Now that you can look back in time you need to take a few precautions. You do not want a worker to go back into the historical data and forgetting to come back to the present to start making edits. Think variations from the sacred timeline for any Loki fans reading this. As in Loki those "variants" will end up needing to be "pruned". The longer it takes you to discover them the harder they may be to remove.

You will need to build in a method of ensuring no one looking back in history can edit that history. Achieving this task can be approached in various ways, the decisions will be based upon your particular setup.

FOR ArcPRO USERS:

Look into using Task. Task are a great way to "automate" workflows and especially ones that are not preformed all that often. They can help both new and seasoned users recall steps in a process.

FOR ArcMap USERS:

Look into using Task Assistant. Task Assistant Manager is like task in PRO above.

FOR EVERYONE:

After enabling and setting up some of the above recommendations you are now in a position to generate ongoing standard reports or one off reports of data as needed. You can have layers generated that only show changes for high growth. You can save just the changed areas without saving a large area that has no changes. This allows for multiple long term gains. If there are questions on this. Improvements? Observations. Please comment, DM, call. Always up for further discussion desired on how to leverage your deployments to get the most of them for you.


https://www.dhirubhai.net/posts/amy-roust-gisp-54871821_ive-got-a-few-projects-that-involve-collecting-activity-7194371309114470402-uxBr?utm_source=share&utm_medium=member_desktop

<a href="https://www.freepik.com/free-photo/people-working-as-team-company_19534504.htm#fromView=image_search_similar&page=1&position=2&uuid=b67de395-8c7b-4527-af68-fcd5f58f5289">Image by freepik</a>



要查看或添加评论,请登录

Richard Koch的更多文章

  • Value - Day 22 of 365

    Value - Day 22 of 365

    I listened as the client said we have trouble making the case for the value of switching to the Utility Network. IN all…

    4 条评论
  • Value - Day 21 of 365

    Value - Day 21 of 365

    Sticking to my area of utilities with this one but hoping others see ways to apply the principals to the work they are…

    2 条评论
  • Value Day 20 of 365

    Value Day 20 of 365

    The deadline is looming. Will you make it? Of course you will.

    2 条评论
  • Value - Day 19 0f 365 STOPPING SCOPE CREEP

    Value - Day 19 0f 365 STOPPING SCOPE CREEP

    Thank you to Erjola Tona for the fantastic post embedded here and permission to springboard off it as well as the…

    5 条评论
  • Value - Day 18 of 365

    Value - Day 18 of 365

    Comparisons part 2. Seems everything has a part two anymore doesn't it.

  • Value - Day 17 of 365

    Value - Day 17 of 365

    Is there value in comparison? If you are comparing things like software, food, vehicles then yes there likely is. When…

  • Value - Day 16 of 365

    Value - Day 16 of 365

    The value of being FIRST. If you are in an outright race it is a wonderful thing.

  • Value - Day 15 of 365

    Value - Day 15 of 365

    Today we can discuss illusionary value. The idea of getting something from nothing.

  • Value - Day 14 of 365

    Value - Day 14 of 365

    Wine and Bourbon. People will pay princely sums for them the older they are.

  • Value - Day 13 of 365

    Value - Day 13 of 365

    For day 12 I wrote about names. The meaning they carried and how quickly it can be lost.

    5 条评论

社区洞察

其他会员也浏览了