Latest Contributions by alex_friant

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

The data value changes is easy, no big deal. You can do that in Pro with very little effect on the end users. As for the map changes, I get it. I had to make massive changes to several maps because we changed the underlying schema design in a big way to improve analyzing the data later on. Good luck! ... View more

When you say "edit", do you mean the data values, the schema design, or the map itself? If it's the data values, then the answer is yes. You need to import the web map containing the data stored up in AGOL into Pro, and edit it like you would any other dataset. Keep in mind any edits you make are instantly saved with no options to "undo". If it's the schema design, the answer is "yes, but only small schema changes". Small schema design changes (deleting a field, adding a field), then you need to coordinate with your field workers to check in their edits (if they are taking data offline), let them know that the service will be unavailable for a period of time (30 minutes?). Unshare the map and HFL/VL. In Pro, import the map from AGOL, and add/delete fields as needed, save your changes to the fields. Edit data if you need to. Field additions will require you update the AGOL map accordingly, like turn on the new field in your pop-ups if you want users to see them. Field deletions will also require you to modify the AGOL map layer properties accordingly. None of this requires you overwrite anything. Once your changes are completed, just reshare the map/HFL with you users and send them a message telling them they are good to go. However, if you are doing massive changes to schema design, like creating relationship classes with layers, etc., then designing a new set up in Pro, loading old data into the new schema, and overwriting the old HFL might end up being easier. Some significant schema changes can make AGOL maps bug out, especially anything that messes with schema that feature templates depend on. Finally, if you need to edit the map design (layer order, labeling, symbology, etc.) then just do it in AGOL. Changes made to maps you import from AGOL into Pro don't effect the AGOL map you imported from. TL;DR: YES: data edits, small schema changes. NO: big schema changes, map configurations. ... View more

Seems like it would be trivial to create the pop, provide a "retrieving..." message, wait for all AJAX/XMLHttpRequess to return, and then populate the results in the pop-up in the order they appear in the TOC. Slap a timeout in there of 5 seconds so that slow or unresponsive servers get ignored and then added to the end of the popup list if they do respond eventually. It's 2020, I noticed that this Idea is "REVIEWED", which is promising, right? ... View more

You can do it, I just did doing these steps: Add source FC to map with map coordinate system matching the source. Add target FC (which has a different coordinate system from the source FC) to map, and make sure your Transformation gets set properly when you bring it in. Open the Append tool, using the instructions above, and run it. Create a new Model or open a pre-existing model Drag-and-drop that Append you did from your Catalog History Pane into the Model (IMPORTANT) Open the Append step in your model, and reset the datatype Property to "Guid" for the GlobalID field for the output (as explained in my comment above. For some reason that setting gets reset back to "GlobalID" when you drag it from History into the Model. I have no idea why it does that. Save your Model, and Run it. Those steps resulted in the data not only being properly projected into the target FC, but it also preserved the GlobalID value. Hope that works for you too! ... View more

Have you tried the Spatially Enabled DataFrame? Introduction to the Spatially Enabled DataFrame | ArcGIS for Developers  Import necessary modules read from a feature class into a dataframe write from dataframe to feature class ... View more

According to the bug report you linked to, it is resolved at ArcGIS Pro 2.4. ... View more

I would imagine it would if you have the agol hosted feature layer in Pro, but honestly never tried. ... View more

Erica, if you can use ArcGIS Pro, you might try this procedure to use the append tool to migrate data and preserve GlobalID's: https://community.esri.com/thread/202815-preserving-a-globalid-while-moving-data-between-feature-classes  ... View more

Yeah, there appears to be two types of .pitemx files, those automated kind with file names of item.pitemx, and those that are actual packages people create by exporting them from Pro and uploading them to AGOL (or your local portal). Those latter kinds seem to work, which is what I was referring to when I wrote that. I always get those item.pitemx to open Pro but they don't extract anything into Pro. But, that's probably because that's a vector tile layer, and you won't actually download the contents to your computer. VTL's are something you would just add to your Pro map by using the Add Data option. For that OSM VTL you provided, I just searched the Living Atlas in Pro Portal from the Add Data option for "OpenStreetMap", and bam, there are all your OSM VTL options to chose from to add to your map. ... View more

I'd say it's possible with some python for the arcgis api. https://developers.arcgis.com/python/guide/using-attachments-with-feature-layers/ Rough sketch of how to: Loop through all records in your hosted feature layer Query each record to see if it has an attachment Build an array logging all records which have zero attachments Put that array into a target table of your choice so you can use in your workflow ... View more