|
97 | 97 | "cell_type": "markdown", |
98 | 98 | "metadata": {}, |
99 | 99 | "source": [ |
100 | | - "### Make a GIS Connection\n", |
| 100 | + "## Make a GIS Connection\n", |
101 | 101 | "\n", |
102 | 102 | "You can make a GIS connection with the following syntax to continue running through the notebook:\n", |
103 | 103 | "`gis = GIS(\"https://www.arcgis.com\", \"username\", \"password\")`" |
|
116 | 116 | "cell_type": "markdown", |
117 | 117 | "metadata": {}, |
118 | 118 | "source": [ |
119 | | - "## Append new features from File Geodatabase\n", |
| 119 | + "## Append New Features from a File Geodatabase\n", |
120 | 120 | "\n", |
121 | 121 | "This first example appends new features from a File Geodatabase into a hosted feature layer. For best performance and reducing the chance of errors when using [`append()`](https://developers.arcgis.com/python/api-reference/arcgis.features.toc.html#arcgis.features.FeatureLayer.append), Esri strongly recommends the schema for the source file (source) to upload matches the schema of the hosted feature service layer (target). \n", |
122 | 122 | "\n", |
|
127 | 127 | "cell_type": "markdown", |
128 | 128 | "metadata": {}, |
129 | 129 | "source": [ |
130 | | - "#### Download the Downingtown target feature layer data\n", |
| 130 | + "### Download the target feature layer data\n", |
131 | 131 | "\n", |
132 | 132 | "The Downingtown Parcels File Geodatabase item exists in the GIS. You'll download the file geodatabase item containing the data you want to publish as a feature layer. " |
133 | 133 | ] |
|
228 | 228 | "cell_type": "markdown", |
229 | 229 | "metadata": {}, |
230 | 230 | "source": [ |
231 | | - "#### Publish the target Downingtown hosted feature layer\n", |
| 231 | + "### Publish the target feature layer\n", |
232 | 232 | "Set properties for a new item, then add it to the portal with the zip file as the `data` argument. Publish the item to create a hosted feature layer your login owns to work though this guide. " |
233 | 233 | ] |
234 | 234 | }, |
|
280 | 280 | "cell_type": "markdown", |
281 | 281 | "metadata": {}, |
282 | 282 | "source": [ |
283 | | - "#### Visualize the Downingtown feature layer" |
| 283 | + "### Visualize the feature layer" |
284 | 284 | ] |
285 | 285 | }, |
286 | 286 | { |
|
406 | 406 | "cell_type": "markdown", |
407 | 407 | "metadata": {}, |
408 | 408 | "source": [ |
409 | | - "#### Get the source Downingtown subdivision item for appending\n", |
| 409 | + "### Get the source item for appending\n", |
410 | 410 | "For the append workflow to work, you need to add the source file containing the new features as an Item in your GIS. In this case this file is already uploaded as an Item for you. Next, get the item id value for this file geodatabase item containing features you want to append to the feature layer. In this case, the Schema from the file geodatabase you'll append matches the hosted feature layer." |
411 | 411 | ] |
412 | 412 | }, |
|
444 | 444 | "cell_type": "markdown", |
445 | 445 | "metadata": {}, |
446 | 446 | "source": [ |
447 | | - "#### `Append` the features\n", |
| 447 | + "### `Append` the features\n", |
448 | 448 | "To update the target `FeatureLayer` object with a new set of features, you can call the `append()` method on it and give it the source `Item` containing the new set of features.\n", |
449 | 449 | "\n", |
450 | 450 | "Run `append` with the appropriate parameters to add the subdivision features from the file geodatabase item . Since the file geodatabase schema matches the schema of Downingtown parcels Feature Layer, only the `source_table_name` from the file geodatabase item is needed to insert new features." |
|
483 | 483 | "cell_type": "markdown", |
484 | 484 | "metadata": {}, |
485 | 485 | "source": [ |
486 | | - "#### Verify the append \n", |
| 486 | + "### Verify the append \n", |
487 | 487 | "We see a message of `True`.\n", |
488 | 488 | "\n", |
489 | 489 | "Query the feature layer and then visualize it to verify results." |
|
566 | 566 | "cell_type": "markdown", |
567 | 567 | "metadata": {}, |
568 | 568 | "source": [ |
569 | | - "## Append attribute values from a CSV into a new column on a Feature Layer\n", |
| 569 | + "## Append Attribute Values from a CSV\n", |
570 | 570 | "You'll now use `append` to update attribute values in a hosted feature layer from a `csv` item. In this case, the schemas **do not** match between the `csv` file (that you will upload as an item) and the hosted feature service layer you want to append values into. \n", |
571 | 571 | "\n", |
572 | 572 | "Instead, you will add a new attribute field to the existing hosted feature service layer, and then use the `append()` parameter `field_mappings` to indicate how fields align between the source item and target feature service layer. In addition to the `field_mappings` parameter to indicate which fields align, you'll also use the `append_fields` parameter to further restrict the operation to indicate which field you want to update." |
|
592 | 592 | "cell_type": "markdown", |
593 | 593 | "metadata": {}, |
594 | 594 | "source": [ |
595 | | - "#### Download the source `csv` data" |
| 595 | + "### Download the source `csv` data" |
596 | 596 | ] |
597 | 597 | }, |
598 | 598 | { |
|
670 | 670 | "cell_type": "markdown", |
671 | 671 | "metadata": {}, |
672 | 672 | "source": [ |
673 | | - "#### Add the source `csv` item to the GIS" |
| 673 | + "### Add the source `csv` item to the GIS" |
674 | 674 | ] |
675 | 675 | }, |
676 | 676 | { |
|
710 | 710 | "cell_type": "markdown", |
711 | 711 | "metadata": {}, |
712 | 712 | "source": [ |
713 | | - "#### Analyze the source `csv` item \n", |
| 713 | + "### Analyze the source `csv` item \n", |
714 | 714 | "The `publishParameters` key value resulting from analyzing the csv file is necessary as the `source_info` parameter when `appending` from a csv file." |
715 | 715 | ] |
716 | 716 | }, |
|
921 | 921 | "cell_type": "markdown", |
922 | 922 | "metadata": {}, |
923 | 923 | "source": [ |
924 | | - "#### Download the target feature layer data \n", |
| 924 | + "### Download the target feature layer data \n", |
925 | 925 | "Search for a shapefile on the portal named `International Boundaries`. You'll download this shapefile, perform some cleanup to simplify the data, and create a spatially enabled dataframe from it. You will publish a unique hosted feature layer that you own to investigate appending values from a csv file into a hosted feature layer." |
926 | 926 | ] |
927 | 927 | }, |
|
1021 | 1021 | "cell_type": "markdown", |
1022 | 1022 | "metadata": {}, |
1023 | 1023 | "source": [ |
1024 | | - "#### Manage target feature layer schema" |
| 1024 | + "### Manage target feature layer schema" |
1025 | 1025 | ] |
1026 | 1026 | }, |
1027 | 1027 | { |
|
1422 | 1422 | "cell_type": "markdown", |
1423 | 1423 | "metadata": {}, |
1424 | 1424 | "source": [ |
1425 | | - "#### Publish target countries hosted feature layer \n", |
| 1425 | + "### Publish target countries hosted feature layer \n", |
1426 | 1426 | "Use the `to_featurelayer()` method on the spatially enabled dataframe, then move the Feature Layer and underlying File Geodatabase item to the desired folder in the GIS.\n", |
1427 | 1427 | "\n", |
1428 | 1428 | "> **NOTE:** The first time you use the `to_featurelayer()` method to publish a Spatially Enabled DataFrame in a conda environment with `arcpy` installed, you may receive a warning message `ValueError: The truth value of a DataFrame is ambiguous. Use a.empty, a.bool(), a.item(), a.any() or a.all().` Most often this is just a warning and the feature layer published correctly. Check the portal to ensure the layer was created." |
|
1462 | 1462 | "cell_type": "markdown", |
1463 | 1463 | "metadata": {}, |
1464 | 1464 | "source": [ |
1465 | | - "#### Get the target hosted feature layer" |
| 1465 | + "### Get the target hosted feature layer" |
1466 | 1466 | ] |
1467 | 1467 | }, |
1468 | 1468 | { |
|
1511 | 1511 | "cell_type": "markdown", |
1512 | 1512 | "metadata": {}, |
1513 | 1513 | "source": [ |
1514 | | - "#### Add attribute field to the target hosted feature layer\n", |
| 1514 | + "### Add attribute field to the target hosted feature layer\n", |
1515 | 1515 | "List all the current fields in the layer so you can use one as a field template. You'll create a copy from the template, edit its values, then add that field to the layer with the `add_to_definition()` method." |
1516 | 1516 | ] |
1517 | 1517 | }, |
|
1664 | 1664 | "cell_type": "markdown", |
1665 | 1665 | "metadata": {}, |
1666 | 1666 | "source": [ |
1667 | | - "#### Add a unique index to the new attribute field \n", |
| 1667 | + "### Add a unique index to the new attribute field \n", |
1668 | 1668 | "\n", |
1669 | 1669 | "When appending data to a layer, you need a foreign key. Thus, any attribute field that matches values from the source csv to those in a hosted feature layer must have a unique index in the hosted feature layer field. The `name` field in the hosted feature layer matches values in the `Country` field in the csv table, so we need to uniquely index the `name` field. \n", |
1670 | 1670 | "\n", |
|
2051 | 2051 | "cell_type": "markdown", |
2052 | 2052 | "metadata": {}, |
2053 | 2053 | "source": [ |
2054 | | - "#### Append attribute values from the `csv` item into target feature layer attribute field" |
| 2054 | + "### Append attribute values from the `csv` item into target feature layer attribute field" |
2055 | 2055 | ] |
2056 | 2056 | }, |
2057 | 2057 | { |
|
2334 | 2334 | "cell_type": "markdown", |
2335 | 2335 | "metadata": {}, |
2336 | 2336 | "source": [ |
2337 | | - "## Insert New Features and Update Existing Features - Upsert\n", |
| 2337 | + "## Insert New Features and Update Existing Features Using Upsert\n", |
2338 | 2338 | "\n", |
2339 | 2339 | "You'll now use the `append` to combine adding new features and correcting attribute value errors. This combination of adding new features (`insert`), and changing existing feature values (`update`) is known as an `upsert`. The `append` method includes the `field_mappings`, `upsert`,`skip_updates`, `skip_inserts`, `append_fields`, and `upsert_matching_field` parameters to provide you control over how the append occurs. " |
2340 | 2340 | ] |
|
2359 | 2359 | "cell_type": "markdown", |
2360 | 2360 | "metadata": {}, |
2361 | 2361 | "source": [ |
2362 | | - "#### Download the target Sierra Leone feature layer data\n", |
| 2362 | + "### Download the target feature layer data\n", |
2363 | 2363 | "Search for a File Geodatabase of the West African Country of Sierra Leone.\n", |
2364 | 2364 | "\n", |
2365 | 2365 | "For the purposes of illustrating the `append` function in this guide, the `arcgis_python` user needs to own a copy of the hosted feature layer to append data into. You'll download a File Geodatabase item as zip file then add it to the portal and publish a unique hosted feature service from that zip file." |
|
2419 | 2419 | "cell_type": "markdown", |
2420 | 2420 | "metadata": {}, |
2421 | 2421 | "source": [ |
2422 | | - "#### Publish the Sierra Leone target hosted feature layer" |
| 2422 | + "#### Publish the target hosted feature layer" |
2423 | 2423 | ] |
2424 | 2424 | }, |
2425 | 2425 | { |
|
2444 | 2444 | "cell_type": "markdown", |
2445 | 2445 | "metadata": {}, |
2446 | 2446 | "source": [ |
2447 | | - "#### Visualize the target feature layer\n", |
| 2447 | + "### Visualize the target feature layer\n", |
2448 | 2448 | "Notice, that the Southern region is missing data. " |
2449 | 2449 | ] |
2450 | 2450 | }, |
|
2505 | 2505 | "cell_type": "markdown", |
2506 | 2506 | "metadata": {}, |
2507 | 2507 | "source": [ |
2508 | | - "#### Query the feature layer to examine attribute errors\n", |
| 2508 | + "### Query the feature layer to examine attribute errors\n", |
2509 | 2509 | "We can see that certain features are missing from the southern part of Sierra Leone. We also can query the data to see that certain features of the Bo Chiefdom have been incorrectly labeled as being in the Eastern District. You can also see that certain Bo Chiefdoms have been incorrectly labeled as `Boao`.\n", |
2510 | 2510 | "\n", |
2511 | 2511 | "You'll use the `Append` function to both:\n", |
|
2690 | 2690 | "cell_type": "markdown", |
2691 | 2691 | "metadata": {}, |
2692 | 2692 | "source": [ |
2693 | | - "#### Examine attribute fields and indices \n", |
| 2693 | + "### Examine attribute fields and indices \n", |
2694 | 2694 | "When you are appending to a target feature layer, you need a layer attribute field that has unique values to match a \n", |
2695 | 2695 | "field in the source item (a foreign key) from which you'll append features/values.\n", |
2696 | 2696 | "\n", |
|
2820 | 2820 | "cell_type": "markdown", |
2821 | 2821 | "metadata": {}, |
2822 | 2822 | "source": [ |
2823 | | - "#### Examine the source file geodatabase" |
| 2823 | + "### Examine the source file geodatabase" |
2824 | 2824 | ] |
2825 | 2825 | }, |
2826 | 2826 | { |
|
2982 | 2982 | "cell_type": "markdown", |
2983 | 2983 | "metadata": {}, |
2984 | 2984 | "source": [ |
2985 | | - "#### Append using `upsert` to update attribute values and add new features\n", |
| 2985 | + "### Append using `upsert` to update attribute values and add new features\n", |
2986 | 2986 | "\n", |
2987 | 2987 | "The `Chiefdoms_Southern` feature class contains edits for Bo Chiefdom features where the name is misspelled in the `Name_2` attribute and the incorrect region is labeled in the `Name_1` attribute. The feature class also contains all the missing chiefdom features to complete the Southern region.\n", |
2988 | 2988 | "\n", |
|
0 commit comments