Latest Contributions by JohnMDye

Could use some help understanding Range Domains configured to use the 'Date' field type. Step 1. In ArcGIS Pro, I created a new Range Domain in a file gdb configured to use the Date field type. fgdb = r"C:\Users\johnmdye\Documents\ArcGIS\Projects\MyProject.gdb" arcpy.CreateDomain_management(     fgdb,     'DateDomain',     'My Date-Range Domain',     'DATE',     'RANGE')‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ Step 2. Next, I set the Range Domain values. I checked the documentation to see how I needed to format the date inputs but there was no information about formatting dates or passing in a date-time object. All of the examples showed text inputs only. arcpy.SetValueForRangeDomain_management(     fgdb,     'DateDomain',     '01/01/1980 12:00 AM',     '05/29/2018 12:00 AM')‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ When I checked the domain after running this, the time had automagically been set to 12:00am for both the minimum and maximum value. This made me assume that ArcGIS Pro had successfully converted my input strings for the min and max parameters to date-time objects. Step 3. Next, I assigned the domain to a field table = r"C:\\Users\johnmdye\Documents\ArcGIS\Projects\MyProject.gdb\TEST" arcpy.AssignDomainToField_management(     table,     'DateField',     'DateDomain') ‍‍‍‍‍‍‍‍‍‍ After that successfully completed, I tried to edit the 'DateField' with the 'DateDomain' assigned to ensure that I could only specify a date between the min and max range, but I was able to enter any date I wanted and save the table.  I then tried performing the workflow completely through the Pro UI and discovered that after I'd created the 'DateDomain' domain manually, I couldn't assign it to my 'DateField' through the Pro UI. (The circles are my mouse clicks) So, in this case I jumped back to Step 2 above and executed the SetValueForRangeDomain_management tool to set 'DateDomain' on 'DateField' and it worked, or at least didn't return an error and when I looked at the Field Design for the TEST table, 'DateDomain' was indeed showing as being assigned to 'DateField'. So, then I added 'TEST' table to a new map and attempted to edit the 'DateField' for a record. Lo and behold, I could enter any date I wanted and save the table.  I shouldn't be able to set the date to 5/30/2018 because the maximum value on the DateDomain which is assigned to the DateField is '5/29/2018 12:00 AM' What gives?! Am I doing something wrong? Can anyone else replicate this odd behavior? ... View more

The GeoForm app template does not currently support collecting form info in a Hosted Table Service. It requires the layer be a FeatureLayer. However, for my specific use case I don't care about location. I see no reason why I should be required to use a FeatureLayer versus a Hosted Table Service. One can store location, the other can't. Let me choose. ... View more

The GeoForm app template does not currently support collecting form info in a Hosted Table Service. It requires the layer be a FeatureLayer. However, for my specific use case I don't care about location. I see no reason why I should be required to use a FeatureLayer versus a Hosted Table Service. One can store location, the other can't. Let me choose. ... View more

A while back, Joseph Armbruster‌ created a wrapper for the Esri File Geodatabase API. Unfortunately, the last commit there was in 2014 so I think its safe to say its not being maintained any longer. I would really like to see a cross-platform python module for working with File Geodatabases.  Like many developers, my workstation is a Mac but since I work with ArcGIS heavily, I run a Windows VM with ArcGIS Pro loaded so that I can access arcpy functionality when there's simply no other way to accomplish a workflow. It's not the most performant setup but it keeps me from having to carry around two laptops. It would be great if the ArcGIS API for Python contained some functionalities for creating, editing and working with local File Geodatabases so that I could do it all from the Mac without having to fire up a VM to do some basic data management locally. Additionally, once that initial functionality to create, edit and manage file Geodatabases and Feature Classes through the Python API were in place, Esri could could support workflows that would allow users to manage their local data through the Python API. Such a workflow might look something like: Create a new File Geodatabase locally Create a Domain in the File Geodatabase created in step 1. Create a new Feature Class Apply the domain created in step 2 to one or more fields in the Feature Class created in step 3. Publish the Feature Class created in Step 3 to the ArcGIS Online/Portal or Server to create a Traditional or Hosted Feature Service Perform some analysis on the Feature Service created in Step 5, likely creating new content containing the result Download the resulting content produced from Step 6 to the File Geodatabase created in Step 1, using the ArcGIS for Python API's existing Create Replica functionality. Do more local data analysis using Pandas, Numpy, SciPy or whatever other python library you like. ... View more