updating the monitoring tasking orders juypter notebook to relfect the recent rrule changes

Author: keith-plant

jupyter-notebooks/tasking-api/planet_tasking_api_monitoring_orders.ipynb

@@ -27,8 +27,6 @@
    ]
   },
   {
-   "cell_type": "markdown",
-   "metadata": {},
    "source": [
     "## Introduction\n",
     "\n",
@@ -37,7 +35,9 @@
     "This tutorial is an introduction on how to create monitoring tasking orders using [Planet](https://www.planet.com)'s Tasking API. It provides code samples on how to write simple Python code to do this.\n",
     "\n",
     "The API reference documentation can be found at https://developers.planet.com/docs/tasking"
-   ]
+   ],
+   "cell_type": "markdown",
+   "metadata": {}
   },
   {
    "cell_type": "markdown",
@@ -192,15 +192,17 @@
    ]
   },
   {
-   "cell_type": "markdown",
-   "metadata": {},
    "source": [
     "## 1 | Compose the monitoring tasking order\n",
     "\n",
-    "We want to create a monitoring tasking order that can be set up to take images of the same location at a defined cadence, in this example once per week. To keep things simple we are going to create a Point order, which takes a single latitude/longitude coordinate pair. Since this is your monitoring order, you need to provide the details of what the tasing order is called, the coordinates, the time period over which the order should be active and the cadence.\n",
+    "We want to create a monitoring tasking order that can be set up to take images of the same location at a defined cadence, in this example once per week for a month. To keep things simple we are going to create a Point order, which takes a single latitude/longitude coordinate pair. Since this is your monitoring order, you need to provide the details of what the tasking order is called and the coordinates. \n",
     "\n",
-    "To make things easier, we will default the start and end time to start tomorrow and end 28 days from now, with the aim of taking four images if we stick to the weekly cadence. Of course, feel free to change this to suit your needs, but if you do, take note that all times should be in UTC format. Unlike a standard flexible tasking order, a monitoring tasking order requires the end time to be defined."
-   ]
+    "To make things easier, we will default the start time to start tomorrow with the aim of taking four images if we stick to the weekly cadence. Of course, feel free to change this to suit your needs, but if you do, take note that all times should be in UTC format.\n",
+    "\n",
+    "Monitoring Tasking Orders are composed slightly different than other types of Tasking Order in that they do not require an *end time* to be defined, in fact the end time is ignored even if it is provided. Instead it requires a **rrule** string to be defined that will set the frequency, the interval and the count, which, when taken together, define the overall cadence pattern for the monitoring order. The only required field in the rrule stirng is the **count**, although in this example we are also defining the frequency, the interval and the week start. More information on the rrule and how it is used for Tasking Orders can be found in the [Planet Developers Portal](https://developers.planet.com/docs/tasking/examples/monitoring)\n"
+   ],
+   "cell_type": "markdown",
+   "metadata": {}
   },
   {
    "cell_type": "code",
@@ -213,7 +215,8 @@
     "latitude=float(input(\"Provide the latitude\"))\n",
     "longitude=float(input(\"Provide the longitude\"))\n",
     "\n",
-    "# Because the geometry is GeoJSON, the coordinates must be longitude,latitude\n",
+    "# Because the geometry is GeoJSON, the coordinates must be longitude,latitude. \n",
+    "# It is also necessary to set the scheduling_type to \"MONITORING\"\n",
     "order = {\n",
     "    'name': name,\n",
     "    'geometry': {\n",
@@ -222,20 +225,19 @@
     "            longitude,\n",
     "            latitude\n",
     "        ]\n",
-    "    }\n",
+    "    },\n",
+    "    \"scheduling_type\": \"MONITORING\"\n",
     "}\n",
     "\n",
-    "# Set a start and end time, giving the order a month to complete\n",
+    "# Set a start time\n",
     "tomorrow = datetime.now(pytz.utc) + timedelta(days=1)\n",
-    "twenty_eight_days_later = tomorrow + timedelta(days=28)\n",
     "\n",
-    "# define the cadence\n",
-    "cadence=7\n",
+    "# define the rrule\n",
+    "rrule=\"FREQ=WEEKLY;COUNT=4;INTERVAL=1;WKST=MO\"\n",
     "\n",
     "monitoring_parameters = {\n",
     "    'start_time': tomorrow.isoformat(),\n",
-    "    'end_time': twenty_eight_days_later.isoformat(),\n",
-    "    'monitoring_cadence': cadence\n",
+    "    'rrule': rrule\n",
     "}\n",
     "\n",
     "# Add the monitoring parameters\n",