Skip to main content
Solved

Help with getting my timestamp data merged correctly so ArcPro time slider will play nice with it

  • August 29, 2024
  • 3 replies
  • 62 views
schulte.a
Contributor
Forum|alt.badge.img+3

Hello, any help would be greatly appreciated with this idea I have:

 

I am trying to figure out the least convoluted way to take my current data and get it into the format ArcPro likes it to be in to take full advantage of the Time Slider.

 

My ultimate goal is to use the time slider in arcpro and the user can slide the time to show how a floor was occupied throughout time.

So, I have a large amount of motion detectors. The data is fed to me like so:

SensorName Timestamp SensorStatus
1 12:00 1/1/2024 On
2 12:05 1/1/2024 On
1 12:06 1/1/2024 Off
2 12:10 1/1/2024 Off

Then Sensor 1 could be triggered again and so forth

 

Arc seems to want the start and end times in the same row. like so:

SensorName Start End
1 12:00 1/1/2024 12:06 1/1/2024
2 12:05 1/1/2024 12:10 1/1/2024

 

It needs to organize 100s of results from numerous sensors and get the start/stop times on the same row, for the correct sensor, for the correct period of time. 

Best answer by bwn

OK, with sample data, something like this, using AttributeCreator Adjacent Feature Processing.

 

 

 

AttributeCreator Parameters

 

 

Start =

​​​​​​

 

End = 

 

 

Input
 


Output
 

 

    This post is closed to further activity.
    It may be an old question, an answered question, an implemented idea, or a notification-only post.
    Please check post dates before relying on any information in a question or answer.
    For follow-up or related questions, please post a new question or idea.
    If there is a genuine update to be made, please contact us and request that the post is reopened.

    3 replies

    bwn
    Evangelist
    Forum|alt.badge.img+26
    • bwnEvangelist
    • Evangelist
    • August 29, 2024

    This can be done with a Sorter (Sort By SensorName, Timestamp) and an AttributeCreator with Adjacent Feature Processing switched On (To look at next +1 Feature) with Conditional Value that where SensorName[+1] = SensorName then End = Timestamp[+1].  Finally remove the second superfluous row per Sensor with DuplicateFilter

     

    or alternatively, Sorter  as above  , + DuplicateFiter by SensorName (To split into start start and stop time) + 2x AttributeRenamer on the two DuplicateFilter ports to rename the first port Timestamp to Start and the the second port to End and join these back together with FeaureJoiner (join by SensorName)

    bwn
    Evangelist
    Forum|alt.badge.img+26
    • bwnEvangelist
    • Evangelist
    • Best Answer
    • August 29, 2024

    OK, with sample data, something like this, using AttributeCreator Adjacent Feature Processing.

     

     

     

    AttributeCreator Parameters

     

     

    Start =

    ​​​​​​

     

    End = 

     

     

    Input
     


    Output
     

     

    schulte.a
    Contributor
    Forum|alt.badge.img+3
    • schulte.aContributor
    • Author
    • Contributor
    • August 30, 2024

    I think that worked, thank you so much! I will learn more about the adjacent feature attribute option, I had no idea about it!

     

    I really appreciate your time/effort/help!

    Community Stats

    32,154
    Posts
    122,043
    Replies
    39,812
    Members

    Latest FME

    Terms & ConditionsCookie settingsAccessibility statement
    A product of
    Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.