Latest Contributions by alex_friant

@WendyHarrison - I could have swore I already tried that and it didn't work, but I must be mistaken. That did exactly what I needed. Thank you! ... View more

If you're not in Pro, but rather in a stand-alone jupyter notebook, can you still designate a "scratch" gdb? ... View more

Not even all gp tools work with memory workspaces. Like try to do it with arcpy.conversion.WFStoFeatureClass. Instead of writing it to memory\somefc, it writes it to disk as memory.gdb\somefc ... View more

I support this user story. Dynamic Label Masking is a very basic cartographic tool that can really speed up workflows. ... View more

Are the field names the same or different? If the field names are different then you'll need to set up the Field Mapping in the Editor Settings per these instructions: Copy and paste features using the clipboard—ArcGIS Pro | Documentation  If the field names are the same, and you have the box checked to Keep Source Attribute Values, then that's a mystery. ... View more

I never tested this out by using an AGOL HFL as my target. Let us know if you find a solution. ... View more

Here are the steps to do this particular thing: : ... View more

Yes you can, sort of. You can't directly view the Feature Class (FC), but if you want to see what the data looks like in a map, you can convert it to a Spatially Enabled DataFrame (SeDF), and then plot that on a map in Jupyter Notebooks. Just keep in mind that your FC and the SeDF are disconnected. If you make changes to your FC then you will need to update the SeDF. This is one way to do it that I use: # import modules import pandas as pd from arcgis.features import GeoAccessor, GeoSeriesAccessor from arcgis.gis import GIS # create map gis = GIS() my_map = gis.map(location = 'San Francisco, CA', zoomlevel = 12) # load your feature class into a spatially enabled dataframe (sedf) fc = r'c:\gis\my_geodatabase.gdb\firestations' my_sedf = pd.DataFrame.spatial.from_featureclass(fc) # plot the sedf on your map my_sedf.spatial.plot(map_widget = my_map) # show the map my_map ... View more

I couldn't replicate those index related issues, however, did you try Kyle Kaskie‌'s solution from higher up in this thread? I quote Kyle: UPDATED: My solution turned out I needed to add an index to my archived feature class (Target Dataset) as the GlobalID field and set as unique. The append will run without making adjustments to the field map.  ... View more

Well there you go!  ... View more

I don't know if something changed in the interim, but the update service URL option in AGO Assist didn't complete the job. It certainly updated the URL's but the Maps's JSON also has a 'item id' value which that tool doesn't change. The result is that the map ignores the URL change and still pulls in the old reference using the original item id. The solution is to use the Edit JSON option for the map, and also update the item id value which matches your new map source. I noticed this because when I clicked on "view item details" for the updated layer, it took me to the old item instead of the new one. I think the layer in the map pulls the data from the service URL, but if you don't change the "item ID" in the JSON, then people could get super confused about why they are getting taken to an differnt or deleted item. ... View more

Thanks for your help Amanda! ... View more

Technically that's easy to do, however, I have a feeling that would be difficult to do considering the ethical implications of sharing health information. Also, data quality and completeness would be very difficult to validate, so I'm not sure how useful the dataset would be. ... View more