Skip to content

Commit 9cf8672

Browse files
requested changes complete
1 parent b5b1c4a commit 9cf8672

File tree

1 file changed

+7
-5
lines changed

1 file changed

+7
-5
lines changed

samples/05_content_publishers/using_and_updating_GIS_content.ipynb

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@
66
"source": [
77
"# Using and updating GIS content\n",
88
"\n",
9-
"The GIS is a warehouse of geographic content and services. Arcgis includes several classes to make use of these content, publish new items and update the them when needed. This sample on updating the content of web maps and web scenes will demonstrate the following\n",
9+
"The GIS is a warehouse of geographic content and services. ArcGIS includes several classes to make use of this content, publish new items and update them when needed. This sample on updating the content of web maps and web scenes will demonstrate the following\n",
1010
" * **Replace web layers** of a web map. For instance, you can use this to update a web map when the services it points to were deleted. The sample shows how to read a web feature layer as a **FeatureService** object and inspect its properties.\n",
1111
" * **Drive the map widget by code**. In addition to displaying the interactive map widget, you can also set it to load at a particular extent. This is great for presentation purposes. During this process, the sample shows how to create and use a **MapView** object and a **Geocoder** object.\n",
1212
" * Make a **copy of a public web scene** item into your contents and then update it.\n",
@@ -791,9 +791,9 @@
791791
"metadata": {},
792792
"source": [
793793
"## Make a copy of the public web scene item\n",
794-
"To make a copy, we essentially download the content of the web scene JSON, remove the parts we don't want, add the layers that we want and publish a new item using that information. The publishing steps is similar to what is described earlier in the **data preparation** section and in detail in the sample titled **Publishing web maps and web scenes**.\n",
794+
"To make a copy, we essentially download the content of the web scene JSON, remove the parts we don't want, add the layers that we want and publish a new item using that information. The publishing steps are similar to what is described earlier in the **data preparation** section and in detail in the sample titled **Publishing web maps and web scenes**.\n",
795795
"\n",
796-
"Let's say, we are only interested in the storms that occur in summer. Summer in tropical Asia is around April-June and that matches with a layer in the existing web scene. Let us query the `operationalLayers` section of the web scene to understand how the layers look like.\n",
796+
"Let's say, we are only interested in the storms that occur in summer. Summer in tropical Asia is around April-June and that matches with a layer in the existing web scene. Let us query the `operationalLayers` section of the web scene to understand what the layers look like.\n",
797797
"\n",
798798
"### Update operational layers of new web scene"
799799
]
@@ -1800,7 +1800,9 @@
18001800
{
18011801
"cell_type": "code",
18021802
"execution_count": 29,
1803-
"metadata": {},
1803+
"metadata": {
1804+
"scrolled": true
1805+
},
18041806
"outputs": [
18051807
{
18061808
"data": {
@@ -1844,7 +1846,7 @@
18441846
"cell_type": "markdown",
18451847
"metadata": {},
18461848
"source": [
1847-
"Now let us explore how the `baseMap` dictionary of the **web scene** looks like."
1849+
"Now let us explore what the `baseMap` dictionary of the **web scene** looks like."
18481850
]
18491851
},
18501852
{

0 commit comments

Comments
 (0)