Hello - Any guidance on how to create a time-enabled layer to work with GeoAnalytics Desktop tools (ArcGIS Pro 2.7.0) in a standalone Python script? I see the code samples for the Reconstruct Tracks and Find Dwell Locations tools, but when I try to run these samples, cannot seem to find a way to set or make the input layer time-enabled. I'd like to run my script without having to open a map.
Any suggestions?
Hey ET,
Thank you for your question.
I've added a sample script below that will set time on the input features you want to use. However, you will have to open your map to prepare the data initially. After that first step in the map, you'll be able to use the data in a standalone Python script.
import arcpy # To create the lyrx: add your layer to a map, open the layer properties and enable time, then right-click on the layer and choose to Share As Layer File input_lyrx = r'C:\data\layer_files\L0ubersf_subset.lyrx' # Make Feature Layer converts the lyrx to features make_feature_layer_output = arcpy.MakeFeatureLayer_management(input_lyrx, "make_feature_layer_output") # Apply symbology sets the time on the feature layer based on the lyrx file definition arcpy.ApplySymbologyFromLayer_management(make_feature_layer_output, input_lyrx) # Now you can use the make feature layer output as time enabled points arcpy.gapro.FindDwellLocations(input_features=make_feature_layer_output, output=r'C:\data\output.gdb\MyOutputLayerName', track_fields="id", distance_method="PLANAR", distance_tolerance="250 Feet", time_tolerance="3 Minutes", output_type="DWELL_CONVEX_HULLS", summary_statistics="latitude SUM;latitude VAR")
Please let me know if this works for you or if you have any questions.
Thank you!
Bethany
For records, posts left on 04-26-2021 09:18 AM, 06-09-2022 12:37 PM, 06-09-2022 02:39 PM, and 06-09-2022 02:41 PM belong to @BethanyScott.
Thanks for the user name compliment - I totally just threw the first thing that came to mind in the user name field...it being pride month and all might have been a factor.
Sooo...there's a lot of backstory on how I got to these 91 features. But to answer your questions first:
- Are they shapefiles or geodatabase feature layers?
- Did the AIS data come from CSV files originally and do you still have them?
- Is it required for your workflow that you run analysis on each layer separately?
A little more backstory on my work flow - I began with AIS from Marine Cadastre and from my own internal USCG process (which only provides AIS up to 3 years ago on a rolling basis.) I mashed those files up in to a uniform schema, ran some validation against authoritative sources for ship type and then built a BDC for my project years - 2015 through 2021.
The BDC object(s) served me well until I tried to filter and export points by ship type which wound up choking my machine (soooo slow) to the point where I opted to mash up the csvs in the BDC source directory using pandas and exporting the filtered annual csvs to a new directory and importing them back in to the gdb.
Everything was proceeding well when I hit the snag with having to enable time on the layers for Reconstruct Tracks to work. And here's the other part - I've got an open support ticket in on this issue related to Reconstruct Tracks yelling at me that my input features do not have time enabled. I can get Reconstruct Tracks to work with small files or big new files, but the second I try to feed it older (projects that have maybe been saved more than a dozen times) or big features (like I'm doing now) it seems like it times out when trying to get a grasp on the time extent of the large files.
Always open to smarter ways of accomplishing what I need to deliver to the operational commanders...hoping you might have a silver bullet!
Thanks,
Amilynn
(aka SemperGumby, BohemianUnicorn, RainbowUnicorn...)
Hey @RainbowUnicorn (great username!),
Yes as far as I know this is still the required workflow.I'm wondering if you could tell me more about the layers you're working with? Maybe we can find a better solution!
These questions will help me to determine if you could use a Big Data Connection (BDC) instead - it will save you tons of time by accessing all of the CSV or shapefiles at once, instead of multiple shp/FGDB layers as you describe in your workflow. Most importantly, big data connection datasets can have time set on them directly (no need for extra time-enabling steps in your script, you can just point to the dataset).Here is some doc on Big Data Connections (conceptual): https://pro.arcgis.com/en/pro-app/latest/help/data/big-data-connections/big-data-connections.htmAnd the following doc outlines how to create one: https://pro.arcgis.com/en/pro-app/latest/help/data/big-data-connections/new-big-data-connection-dialog.htm
Thanks!
Hey Bethany - is this solution still valid? Do I *really* have to go in to the application to set time on my layers first in order to get reconstruct tracks to work in an arcpy script?
I'm using 2.9.3 and was hoping against hope that I could use something as simple as this:
for lyr in maps.listLayers(): lyr.enableTime("DateTime") maps.isTimeEnabled = True
to skip having to set time on nearly 100 layers of AIS data. I want to avoid all that clicking, but alas if that's what's required, I guess I'm launching the program instead of working in my notebook.
Aangemelde leden kunnen berichten plaatsen, updates volgen en meer. Nieuw hier? Registreer een gratis account.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
