Version 6 of MapRun is being released as a new App in both the Google Play Store and the Apple App Store.
This allows MapRunF and MapRun6 to co-exist in a transition period. (and be rationalised later).
MapRun v6 will be available to a closed group initially, and all going well, will then be available to all.
OK, got it! Available in the Google Play store.
Looks good so far: many small improvements, I see.
May take it for a walk today.
Edit: Successfully used MapRun6 for a new Check Sites route in my local woods.
- handled a "beepfest" well when I inadvertently specified 2 controls within 2r
- uploaded OK to Strava at the end
- Wasn't able to try out the new QR code and NFC punching features so someone else will have to do that
Yes, I also found it in Google Play store, installed it and discovered that an event that I just created with a start date in the future wouldn't load because the start date was being enforced. So it seems that the event available dates are working but perhaps not the results & tracks available dates?
Nav-X Map Adventures
Santa Rosa, CA USA
Will MapRun6 eventually "overwrite" MapRunF on Android / iPhone with an automatic update as the (what I would see as an excellent "event specific" feature) "hide map" option seems very useful for how our orienteering club would want to implement MapRun? ....or is MapRun6 destined to replace MapRunF as a standalone app. (....probably not, but just asking!)
Tried MapRun6 yesterday, all OK and some nice improvements, but two comments. The high-res red line + low-res blue confused me (as I use blue lines for features to recce...) but why is the low-res line there at all? The other thing is that a course that has been started but exited again before punching any controls is not shown by MapRun6 in the results. I used that in MapRunF a lot for recce-ing (don't want to actually punch anything, just have a hi-res gpx file) and also for seeing if anybody has run any of my routes.
I might tidy this up and just show a single track in future versions, but I thought whilst we are settling in the idea of have two location feeds, it might be good to see both traces.
On the other point I see you have found the documentation on this... If the opening the event is just a "quick peek" for less than 30 seconds we now discard the track. (After a prompt that alerts the runner to this).
The limits on viewing results is a good enhancement - we're likely to make use of it when we can have competitive events again. Thanks :-)
The new Event entry form indicates that there will be 3 date ranges that will apply:
Dates the event can be run
Dates the results table will be visible
Dates that the tracks will be visible
I think there is probably a fourth category that would be worth adding: dates that scores are available (just overall scores, not # controls, time, control numbers visited, etc.).
When we set up score events to run over a week or two, it would be nice for runners to know how their score compares with other runners when they finish their run. However, we'd like to prevent later runners looking at the controls other people have visited, and prevent them looking at other people's tracks.
It would be good therefore if we could allow people to see just total scores of each participant, but not allow them to see the full results table (controls visited etc.) or other people's tracks, until after the event window has closed.
Is that possible with the functionality you are implementing?
A separate question: If that option is selected, will runners be able to see their own results & route if routes/tracks are not yet visible? It would be good if runners could see their own controls visited and the route they took. E.g. to understand where they might have made mistakes, or if they wanted to challenge a missed control.
Also, a usability suggestion - could the default end date for results & tracks be the default for runs + 1 year rather than defaulting to 2 years? So if you want an event to be available for 3 years for example, you would only need to change the run end date not all 3 dates.
Similarly, could the default start for results & tracks be set to the run start date if the run start date is changed?
The date ranges relating to results are for results display on the server.
Runners can still see what they've always seen on their phone.
Regarding an extra date range for total scores. We don't have a results display of total scores currently so that would need to be a new item, and possibly have restricted date ranges.
I'm thinking that I see how much these time ranges get before I go doing anything more with it... and OK on a different approach to default values.
The main drivers for the date ranges were:
- holding back results until the end of an event
- allowing close off of events for participation where the map is restricted (eg by the landowner)
- allowing auto archive of the event and the results after a defined period.
Tried to use MapRun6 on an Android device with a physical keyboard and fell at the first hurdle. Keyboard entry does not work properly when entering your name, specifically:
- Tab does not move to next field, instead it just enters a space
- Delete key does not work
MapRunF works fine (as does every other app I've ever tried!).