Workflow(y) pro sloučení úprav dat hostovaných na AGOL do Desktop FGDB

JeffreyWarren

<\/HEAD>

Dobré ráno všem,<\/P>

<\/P>

V současné době hostujeme všechny naše feature služby na AGOL.  Toto bude poprvé, co stáhnu data z AGOL zpět do ArcGIS Desktop.  Hledám nápady na workflow, jak dostat data z fgdb (vytvořené z AGOL) a sloučit je zpět do mého původního datasetu.  Terénní tým vyšel ven a aktualizoval mnoho atributů a chci je přenést.  Nechci dělat nic s geometrií, protože jsem jich několik přesunul.  Chci pouze atributaci a také přílohy/fotografie, které přiřadili.<\/P>

<\/P>

Někdo má nějaké nápady na workflow, které by byl ochoten sdílet?  Rád bych tento proces nakonec automatizoval, pokud to bude možné.<\/P>

<\/P>

Jediný způsob, který mě napadá hned teď, je vytvořit join (používající Facility ID) a provést field calc., ale nevím, jestli někdo nemá jiné nápady.  Naše data jsou ve schématu LGIM, ale zatím se zaměřuji na Waste Water.  Ale mám další utility čekající, až dokončím tento projekt.<\/P>

<\/P>

Předem děkuji,<\/P>

Jeff<\/P><\/BODY><\/HTML>

EmilieBrill-Duisberg

Hi Jeff,

This is a challenge that Enterprise geodatabases and ArcGIS for Server services are well-suited for.  However, when working with file geodatabases and hosted feature services, you can get your newly collected attributes from your Collector data into your old feature class using joins and field calculations.  Transferring the attachments is a bit trickier, but follows the same basic logic.  You can use the following workflow to port your Collector attachments over to your previous geometry without bringing along the geometry created in the Collector app.  This workflow could be made into a ModelBuilder model or Python script for automation.

1.  Export your ArcGIS Online feature service, edited in Collector, to a new file geodatabase and download it to your local machine.

2.  The file geodatabase contains a relationship class which connects the features to the attachments using a GlobalID and a REL_GLOBALID field:

3.  Perform an attribute join to append the attribute fields from the downloaded feature class to your original feature class.  This join is based on a unique ID that exists in both tables and is necessary because we need to get the GlobalID field created by ArcGIS Online when the photos were collected into your original feature class as shown below.  It is a good practice to export to a new feature class after the join has been created to prevent any unexpected behavior caused by an active join.

4.  Next, perform an attribute join to append the attribute fields from the downloaded attachment table to the output of Step 3 above.  This join is based on the Global ID and REL_GLOBALID fields:

5. It's a good idea once again to make the join permanent by copying the features to a new feature class.  Now, we have a single feature class containing your original geometry and containing the Attachment IDs and the Attachment Names from the Collector data downloaded from ArcGIS Online.  This will be critical for matching up the correct photos and features.

6. Create a file directory on your computer and batch download all your attachments using the instructions given at http://support.esri.com/technical-article/000011912.

7.  Add a new text field to the output of Step 5 for the filepaths of your attachments.

8. Populate the field with your attachment filepaths using Field Calculator.  In VB, the code would be:

"<path to the folder with your photos>\ATT" & [ATTACHMENTID] & "_" & [ATT_NAME]

9. You should end up with a complete filepath which matches those of the photos you batch downloaded in Step 6:

10.  Enable attachments on this feature class using the Enable Attachments tool.  Then use the Add Attachments tool to attach the photo/video attachments:

This will match your attachments to the correct feature and create a new relationship class between the final output of the above workflow and an attachment table containing your media.

Best wishes,

Emilie

Esri Support