removed local path information

Author: jyaistMap

guide/04-feature-data-and-analysis/appending-features.ipynb

@@ -558,29 +558,6 @@
     "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 `feild_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."
    ]
   },
-  {
-   "cell_type": "code",
-   "execution_count": 37,
-   "metadata": {},
-   "outputs": [
-    {
-     "data": {
-      "text/plain": [
-       "'C:\\\\\\\\Data\\\\My_Projects\\\\Python_API\\\\append_review\\\\guide'"
-      ]
-     },
-     "execution_count": 37,
-     "metadata": {},
-     "output_type": "execute_result"
-    }
-   ],
-   "source": [
-    "cwd = os.path.join(r\"C:\\\\Data\\My_Projects\", \"Python_API\", \"append_review\")\n",
-    "wd = os.path.join(cwd,\"guide\")\n",
-    "os.chdir(wd)\n",
-    "wd"
-   ]
-  },
   {
    "cell_type": "code",
    "execution_count": 40,
@@ -2411,18 +2388,6 @@
     "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. "
    ]
   },
-  {
-   "cell_type": "code",
-   "execution_count": 65,
-   "metadata": {},
-   "outputs": [],
-   "source": [
-    "cwd = os.path.join(r\"C:\\\\Data\\My_Projects\", \"Python_API\", \"append_review\", \"guide\")\n",
-    "wd = cwd\n",
-    "os.chdir(wd)\n",
-    "guide_dir = wd"
-   ]
-  },
   {
    "cell_type": "code",
    "execution_count": 66,