Latest Contributions by alex_friant

Cut to the chase: If you attempt to import the arcgis module (or even parts of it) in your python script, then do not name your python script "pytest.py". You will see some very strange behavior and your script will fail. The name of your script will conflict with pandas initialization scripts, which just-so-happen to have a variable named "pytest". The Long Version (skip if you are squeamish): I have ArcGIS Pro 2.1 with the patch installed. I was troubleshooting a script and decided to create a simple python test script to figure out what was going on. I innocently named it "pytest.py". I suddenly started seeing strange errors I hadn't previously seen when attempting to execute my script. Okay, fine, I thought. Let me see if I can manually run these commands "import arcgis" in the Python Shell. What happened next made no sense at all - the Python Shell responds by re-running my "pytest.py" script and the same errors occurred! What? I was in a completely different session. So I uninstalled ArcGIS Pro, deleted the Python folder and reinstalled ArcGIS Pro. I opened the Python Shell and manually entered the command "import arcgis". Again, it responded by re-running my "pytest.py" script and errored out. This fried my brain. The day ended and I went home. After a long night of nightmares of Python acting weird, I came to work this morning and carefully examined the Traceback results. I saw that the Pandas package was reporting "AttributeError: module 'pytest' has no attribute 'mark'". It suddenly clicked: I decided to rename my script "mytest.py" and everything worked fine and the manual command errors also disappeared. It turns out that the name of your script will conflict with pandas initialization scripts, which is part of arcgis intialization, which just-so-happen have a variable named "pytest". I just thought I'd put this out there for the next poor soul who attempts to name a python test script "pytest.py" and import arcgis inside of it. And yes, I learned to pay more attention to traceback results 😉 ... View more

We would like to have a Hosted Feature Service (HFS) that we can have named AGOL users bring into ArcMap and do the "edit locally" and "sync back to server" workflow. However, we also need that HFS to be viewable as read-only to the Public. Is this possible? We've tried to set this up, but the only way to do the ArcMap local editing/sync thing is to make the HFS have the "Enable Editing" option turned on. And when you have Editing turned on with the HFS being available to the Public, then the anonymous Public can edit the data inside the HFS, which is not desireable. If you turn off Enable Editing, then we can't do the local editing/sync workflow. At this point, the only workflow that works is to have the GDB stored locally, permanently, and publish it out/overwrite the existing HFS with "Query" being the only capability checked, when we have updates. It works, but it's a one-way workflow, which we were hoping to avoid. ... View more

The spirit of this post is to gather other people's solutions, discuss ways of improving the suggested solution, and track future ArcGIS capabilities as they evolve for this problem. This all started because we had existing data in a GDB that contained a Relationship Class (RC) between a Feature Class  (FC) and a Table (TBL) using the FC's GlobalID field. We wanted to move that data into a new GDB that had a new schema (changes in domains, fields, etc.). The problem is that when you Append the old data into the new schema, the GlobalID in the new schema is different than the records from the old data. This breaks the relationship between the FC and the related TBL. UPDATE 2: I've got some bad news and I've got some good news. And some ugly details. But I also have steps/options. The BAD news The "New Solution" from my first update no longer works in Pro 3.x, as so kindly brought to our attention by @MichaelMannion a few days ago in this reply. Thanks Mike! Basically, ArcGIS Pro no longer allows you to change the datatype for step #8 in the solution below. This breaks the solution I originally provided. The GOOD news ArcGIS Pro 3.x now respects the "Preserve GlobalID" environment option in the Append tool, but with very specific parameters. It works if the target database is either Enterprise Geodatabases and Mobile Geodatabases, but not File Geodatabases. The UGLY details In order for the Append tool to actually preserve the GlobalID from your source to your target, you still need to check the "Preserve GlobalID" environment option in the Append tool.  You can only get it to work with Enterprise Geodatabases (EGDB) and Mobile Geodatabases (MGDB) as your targets, as no longer works with File Geodatabases (FGDB). Here's why. The target GlobalID field must have and index that is configured as "unique". You can't make a GlobalID field that has a unique index in a FGDB. Unique and ascending indexes are not supported for shapefiles or file geodatabases. These parameters are ignored when the tool is executed on a shapefile or file geodatabase data. A 'unique' index can only happen if: the table/feature class is in an EGDB /MGDB you add the GlobalID to the table/feature class using ArcGIS Pro (3.x+) alternatively, copy/pasting the empty target table/feature class into an EGDB or MGDB will automatically change the index to 'unique' for GlobalID in the paste target When you follow those two parameters, the index that gets automatically created for the GlobalID field that is has the unique setting. If your target field is a GUID datatype, it must also have a "unique index". You must use add the index in ArcGIS Pro, on an EGDB table/feature class, and make sure the "unique" checkbox is selected before you run the Add Attribute Index tool. The STEPS for Enterprise Geodatabases/Mobile Geodatabases Below I only refer to EGDB, but if you're using a MGDB the same steps apply. Make sure your target table/feature class is in an EGDB If you have an empty table/feature class sitting in a FGDB but the indexes are not "unique", just copy them over to the Enterprise Geodatabase using ArcGIS Pro (3.x+) Make sure your target field in the table/feature class has a "unique index" GlobalID If you already have a GlobalID field, but the index is not unique you need to replace your table/fc with a new one Export it to a local FGDB, but make sure to remove GlobalID following these steps. Delete the original target from the EGDB Replace the original target with a copy of your table/fc that has no GlobalID In ArcGIS Pro (3.x+) add GlobalID's to the target table/fc (right-click>Manage>check the box for  "Global IDs") Confirm that the index for the GlobalID field is in fact "unique" GUID If you already have a GUID, but the index is not unique, you need to delete the index Then you need to use the Add Attribute Index tool to create an index for the GUID, and make sure you check the box to have it be "unique" Confirm that the index for the GUID field is in fact "unique" Now your EGDB target table/fc fields are ready! Open the Append tool Under Environment, check the "Preserve GlobalID" box Under Parameters, append as usual Once your data is in the updated schema, you can copy/paste it over to a File Geodatabase if you need to (for a deliverable or something). The STEPS for File Geodatabases All hope is not lost for users who must be restricted to File Geodatabase only. (But really, there is no reason to be afraid of the Mobile Geodatabase as a in between step, it works well!). Thanks to user @DirtDogRoj in his excellently documented reply you can follow clearly outlined steps to achieve the same result. I think you could put it into Model Builder even as all the steps very systematic. You might like this method better just because! 😉   Pay no attention 2: UPDATE 1: I have a much, MUCH, better solution that I discovered and it doesn't appear to be documented anywhere. All the text below that has strikethrough you shouldn't pay attention to, as it was the old, convoluted solution. New Solution: Have your old data ready to load (your "loading" gdb - this is your source data) Have your empty geodatabase with the new schema. (your "new" gdb. It's okay that it has the "GlobalID" field, there is a new way to populate it with the GlobalID values from your loading geodatabase in ArcGIS Pro.) Open ArcGIS Pro Make sure your two geodatabases are added to the project (the "loading" gdb and the "new" gdb) Run the Append Tool Use your loading gdb feature class as the source, and your new gdb feature class as the target For the tool's Environment settings, make sure the "Preserve Global ID field" checkbox is checked In the Append tool's Field Mapping section, under the "Properties" tab, change the target feature class Data Type for the GlobalID field from "GlobalID" ---to----> "GUID". (I know, this seems strange. The data type is set in the target feature class schema as "GlobalID", but if you don't change this to GUID, then the GlobalID values from your source feature class will not migrate over to your new FC. If you change this setting to "GUID", they will magically migrate over to your new FC! I don't believe this is documented. If someone sees this documented anywhere, please share in the comments!) Repeat steps 4-8 for your related table. Pay no attention 1: After doing some searching, I discovered that there is a way to do this using and Enterprise Geodatabase (EGDB) and ArcGIS Pro.   I post my basic workflow here on how to preserve the FC's GlobalID values so that when you migrate the data over to the new schema, the GlobalID values stay the same in the new FC. This preserves the relationship between the FC and the TBL in the new schema.   Assumptions: You have a FC you need to migrate to a new schema and would like to preserve the GlobalIDs. You have access to an EGDB and ArcGIS Pro   Manual Steps: Copy the source FC (Feature Class) to an EGDB (Enterprise Geodatabase) Rename each class to have "_OLD" appended to them Note: You might need to deal with differences in domains at this point if they have the same name but have different contents You don't want your final domains to be appended with "_1". If so, then after you copy them over, you will need to turn off the domains where they are used, and delete them in the EGDB This doesn't affect final product because this is only happening in the source data Prepare your new schema of your target FC to have a "GlobalID" that can be preserved: Take a copy of the FC empty schema Use X-Ray in ArcCatalog to remove the GlobalID field in the FC Create a new GDB using this new FC design Create a new "GlobalID" field manually (don't use the GP Toolbox) in the FC Use "GUID" datatype Do this in the FCL for the Global ID's that need to be preserved - this is normally only necessary on the FC where there is a oneway relationship Copy the FC to the EGDB In the newly copied FC in the EGDB… Create a new index for this new "GlobalID" field Make sure that it has "Unique" box checked, and "Ascending" too Append records from the OLD FC to the NEW FC using ArcGIS Pro's Append tool Add the FC's to an ArcGIS Pro project Run the Append tool Make sure to have the "Preserve GlobalID" box checked under Environments For "Schema Type", use the "Use the Field Map to reconcile schema differences" option   At this point, you can now copy/paste that new FC back to your location of choice, and rebuild the RC so that it connects up with the new TBL. It turns out that the GUID's used in the related table to relate back to the FC are naturally preserved by using the Append tool in ArcCatalog, so performing the workflow above on the related TBL is unnecessary. Even though the TBL's GlobalID (not GUID) values change when moving the data, that's doesn't matter to us because they aren't used to create the relationship.   We don't do this often so we aren't going to take efforts to automate it, but I assume that might be possible. ... View more