Invalid longitude

[dcurrie]

I ran around the following MapRun this morning using MapRunG:

/UK/Find Your Way/FYW South Hants/FYW SOC League 2022/FYW Townhill Bitterne Park ScoreN45

Everything was fine up until the point I attempted to show my result at which point I got the following error:

error: Invalid argument (_longitude) : Longitude must be between 180 and 180
degrees: 358.61893584408574

The results are set not to be visible yet but, if I look in the admin console, my run appears to have uploaded successfully.

Unfortunately, someone else has just e-mailed to say that, they attempted to complete it using MapRun6 and this error comes up immediately when you click "Go to start". They did manage to successfully complete the course from a paper map although, as the error just stayed there, they couldn't see how long they had remaining. Having just checked, I also see the error at this point.

Any suggestions as to how to rectify this?

Regards
David

[dcurrie]

I had looked at the KML file and everything looked fine but, poking around inside, the KMZ, I see that there are the east/west coordinates at 358 degrees. I'll try and find out what the planner used to create the KMZ.

[dcurrie]

The planner has confirmed that he used the KMZ Create function on the MapRun site so I'm surprised no one else has seen this. (He's just gone through the process again with the same result.)

[Peter Effeney]

Dave

The create KMZ function has been known to create values that are out of range on rare occasions. I've not seen a repeatable example. I expect its some combination of location/rotation and the placement of the two pins.

If you have a case that consistently fails and can describe roughly where the two pins are dropped, could you email details (including the image file) to [e-mail] please.

On recovering the situation, sorry to say, a new KMZ will need to be created. Try putting the pins in opposite corners and potentially just go for an un-tiled KMZ. Then delete the event, recreate it with the same name and refresh results.

I'll add a test for out-of-bounds values in the KMZ create (and if you have a failing example, I'll find the root cause). Also a function to replace a map of a published event is planned.

Peter

[dcurrie]

Thanks, Peter. Hopefully, with that information the planner will both be able to recreate with and without the problem! I wasn't aware of the trick with recreating the event with the same name to pick up the results - that would have saved me some effort with previous issues!

[Peter Effeney]

David,

Thanks for the update. It would be great if we can reproduce the error.

The advantage of requiring all events to have a globally-unique name is that we can do simple matching of individual results to events. ... So, if it all goes wrong, or an update to Map or Course (hopefully minor) is required, delete the event and recreate it with the same name. (and refresh results).

The process of doing a Refresh of results for an event, deletes the existing combined results and RouteGadget tracks for the event, then looks for any results that match this event name and creates a new set of results and tracks.

Of course, people who have already downloaded the event to their phone/watch may still use the old version.... but any new downloads will use the updated version.

The other point to be aware of if you are using MapRunLinks (URLs or QR Codes), is that the MapRunLink will be different for the re-published event. (We are looking at changing this so that this doesn't occur in the future).

If the change to map or course is so material that it would be unfair for some to run on the original version and some to run on the new version, then a new event name is recommended.

... and of course if the event has a problem, it's best to replace it with a version that works.

I hope this explanation helps Admins to better understand their options.

Peter

Peter

[dcurrie]

Just to circle back on this... I believe Mark (the planner) was going to email the support address but, for the benefit of anyone else reading this, he did get to the bottom of the problem. The solution is to make sure that you don't spin the map when using KMZ Create. For each revolution of the globe you do before placing a pin it's adding/subtracting 360 degrees whereas the MapRun app itself can only cope with values in the range -180 to 180 degrees.

Cheers,
David