FetchPoint: The Game

2 lurkers | 284 watchers

Nellers Aug 2020 1:56pm, 9 Aug 2020 36,958 posts	0 Nellers I'm the same for that eL Bee! and I do the same. I'm on the edge of town with fields, railway line and dual carriageway cutting off the edges of my circle, with fields beyond. If it's legal to get to it I'll leave it, even if it's somewhere I can't practically get to. If it's in fields with no paths or literally the wrong side of the tracks, I'll mark i and kill it. It's the bits that are legally accessible but only really in the summer in daylight that cause me dilemmas.
Velociraptor Aug 2020 2:07pm, 9 Aug 2020 47,923 posts	0 Velociraptor eL Bee! and I have the same dilemma, Nellers. There are footpaths in our circle that are accessible at this time of year but would need to be logged as bog-snorkelling between October and April. I shall be quite happy to relocate any bugs that land there then.
Vancouver Jogger Aug 2020 2:42pm, 9 Aug 2020 5,195 posts	0 Vancouver Jogger Fetch made a change to the coding a little while ago to make seasonal inaccessibility an option - you can mark something inaccessible and then when the season changes just run that route and all the points will get turned back to accessible. Of course the same thing happens when a confident cyclist rides along that dangerous A road that has no pavements which you’ve spent weeks marking as in accessible
Bright Strider Aug 2020 4:07pm, 9 Aug 2020 124 posts	0 Bright Strider To approach accessibility from the other angle, I recently ran through a bug's circle, but the route went through the edge of the circle. If I'd cycled it, I could have gone deeper into the circle because the bug was in a field, next to a road, with the pavement on the other side. Between GPS and the game, despite having run through the circle, Fetchpoint thought I had not. I took the approach that there was an accessibility problem, and marked it as such. The bug moved to a point where I could go through the middle, and I did squash it successfully, later that day.
Bright Strider Aug 2020 4:18pm, 9 Aug 2020 125 posts	0 Bright Strider Given that inaccessibility is now easily reversible I have fewer qualms than I used to about marking a bug as inaccessible.
ftrobbie Aug 2020 8:02pm, 9 Aug 2020 267 posts	0 ftrobbie [Given that inaccessibility is now easily reversible I have fewer qualms than I used to about marking a bug as inaccessible. ] This 👍
Nellers Aug 2020 9:01pm, 9 Aug 2020 36,959 posts	0 Nellers Fair enough then. I won’t feel guilty when the weather turns and I lose the light. Cheers.👍🏻
Velociraptor Aug 2020 9:01pm, 9 Aug 2020 47,930 posts	0 Velociraptor I marked my bug as inaccessible this morning because although I could have got it on a weekday by going into the surgery car park I couldn't have got it today without climbing over the gate, which was padlocked shut. And we're going to have an interesting situation when the local parkrun starts, because markers on the rugby fields (which are private property) will be accessible for about two hours on a Saturday morning and inaccessible at most other times.
sallykate Aug 2020 9:39pm, 9 Aug 2020 6,817 posts	0 sallykate I mark a bug as inaccessible when it’s in a place I can’t access during working hours. I think that’s ok - it’s not because I’m lazy, it’s a practical reason.
ftrobbie Aug 2020 7:32am, 10 Aug 2020 268 posts	0 ftrobbie Velo, I don't see it as a problem, all that is going to happen is that every week the spots on the parkrun route plus gps drift/ inaccuracy will be opened up. And all the following week people may mark stuff as inaccessible. Alternatively just mark the bugs and leave everything else alone and take the opportunity to warm up and collect the newly available swag every parkrun. The only real issue that affects the game are the bugs if you are trying to build a score.