This is something I could have been using all along for our forest maps. We cannot see the features using Google Earth (which is the recommended method) due to the forest cover on most of our maps, including many of the local park maps.
Today I walked an upcoming course and dropped pins at a number of control locations where the app didn't beep in a timely manner or my track didn't match with the feature on the map. I then edited the KML (which had been generated from Purple Pen) with these new locations and re-uploaded it. This should result in a more satisfactory experience for the competitors.
I couldn't find any documentation on the Checksites pages about the Drop Pin functionality. So I mention it here for others to make use of.
I was the one who mentioned it - it was an accidental find! I’ve since used it a number of times and it is very useful. My original experience with waypoints was not great (I was using a separate app at the time) due to the track wandering around a lot when you stop (iPhone and normal watch track) so I found you could grab multiple waypoints from the same spot and they had a fairly large spread. I purchased a Garmin Glo 2 (external Bluetooth GPS receiver) and have found this to be an excellent addition. With the much increased data rate (4pts/sec for iOS and up to 10 for Android) and it’s ability to “lock” when you stop moving, waypoints are much more accurate and consistent.
This functionality has not been actively promoted as it is not without some limitations and constraints.
Take the scenario, of an event setter wanting to place controls for MapRun on features under tree coverage ie not visible from Google Earth.
- If the setter were to take their Android/iPhone into the field, visit each site and drop a Pin and use the recorded Lat/Lng as the control location, experience has shown that this can give patchy results (regarding the effectiveness of these controls in a subsequent MapRun event).
- Choosing to use an obscured location for a control site (even with 100% accurate Lat/Lng) has extra risk as the GPS of runners is likely to be less accurate in such locations. Consideration could be given to increasing punching tolerance to allow for this.
- As Michael says, taking multiple readings can help ... particularly if the control site is approached from different directions at different times (rather than just sequentially recording multiple locations at the site).
- The feature (to record location Pins) was included in MapRun principally for mappers who use MapRun as part of their map verification checks.
- The feature CAN BE effective with a high-quality bluetooth-connected external GPS device connected to MapRunF. Devices like the Garmin GLO or better still, if you can get a device that uses multiple satellite systems (GSP, GLONASS, Galelio, Beidou, QZSS) and can use real-time terrestrial-based error correction (eg RTK), then very good location accuracy can be achieved (cm accuracy). Look in the Android Play Store for 'NTRIP' client Apps.
- In summary - The feature exists in MapRunF, but it should be used in the knowledge of the above limitations/constraints. As GPS technology gets even better, and RTK becomes more prevalent, this feature may come into its own.
- As always any feedback from use in the field is welcome.