auto

assign4.md

@@ -119,13 +119,13 @@ serialization to put to a file (use a text editor to look at).
   
   
 ## Additional Task, and Extra Credit
-Pick one of the tasks below for the last 10 points of this project.
+Pick one or two of the tasks below for the last 10 points of this project.
 
 Pick up to another three for 10 pts bonus for each you accomplish (up to a max of three), or a donut each,
 your choice. You'd have to come by to pick up the donut.  The points
 will be appliable on either the `assign5` or the final (which will be
 out of 200 pts):
-- *Get your app to read and write files with the .gpx extension*.  Instead of
+- (10 pts) *Get your app to read and write files with the .gpx extension*.  Instead of
   reading and writing .gpx436, read and write .gpx. Here, I'm just
   asking you to get the UTI setup correct so that the document and
   browser will allow you to read and write files with the `.gpx`
@@ -134,12 +134,12 @@ out of 200 pts):
   able to write read and write RideWithGPX files. Don't worry, look at
   [this file](assign4bmwRS1200.gpx) and you will see the format is dirt simple (though
   there may be multiple `trkseg`s).
-- *Show a pre-planned route*. Show the route (w/ a
+- (5 pts) *Show a pre-planned route*. Show the route (w/ a
   different color) from another gpx file as you are recording a ride, so that the rider can
   follow a pre-planned route. Allow the user to choose which other
   ride to use by adding a button to the screen which showing a
   pre-recorded ride. Must be able to turn this off as well.
-- *Poor man's turn-by-turn navigation* - The best way to do turn-by-turn
+- (10 pts) *Poor man's turn-by-turn navigation* - The best way to do turn-by-turn
   navigation is to know when and where you turn onto a different
   street. We don't have that information, so you can try to use
   heuristics, like "turned left or right between 70 and 110 degrees
@@ -153,7 +153,7 @@ out of 200 pts):
   direction of travel is "up", or north is "up". 
 - (5 pts) *Tracking vs not tracking map*  By default, our app *tracks* the
   rider on the map: keeps him/her centered in the middle of the screen with a set
-  magnification. Cease tracking you detect that the rider has manipulated the display,
+  magnification. Cease tracking when you detect that the rider has manipulated the display,
   either moving, zooming, or rotating. Allow the rider to restart
   tracking by hitting a button, ideally the above map orientation button.