Page 3 of 3

Re: Dinosaur Moveable Game September 2018

Posted: 26 September 18 2:11 pm
by caughtatwork
gooseandegg wrote:
whitewebbs wrote:I found GA12934 today and moved it from its original position in Rokeby to Lauderdale. While checking the ladder I noticed It has not had a move registered. It shows no distance at all and no coordinates are showing in the published log now of where it started off. The coords in the published email on the 1 September were S42 53.956 E147 26.259.

This is my dinosaur and I too would like to know why the first move by whitewebbs was not recorded. The move was from S42 53.956 E147 26.259 to S42 53.956 E147 26.259, a distance of 3.8km. The move and distance have not been counted.
The game counts the distance between logs and co-ordinates. Or in other words, under the whitewebbs log there is no "moved" distance registered. Your published log has no co-ordinates. As such the game cannot determine where it moved FROM. You can address this by editing your published log and placing the original cache co-ordinates on it.

Re: Dinosaur Moveable Game September 2018

Posted: 26 September 18 2:52 pm
by gooseandegg
caughtatwork wrote:
gooseandegg wrote:
whitewebbs wrote:I found GA12934 today and moved it from its original position in Rokeby to Lauderdale. While checking the ladder I noticed It has not had a move registered. It shows no distance at all and no coordinates are showing in the published log now of where it started off. The coords in the published email on the 1 September were S42 53.956 E147 26.259.

This is my dinosaur and I too would like to know why the first move by whitewebbs was not recorded. The move was from S42 53.956 E147 26.259 to S42 53.956 E147 26.259, a distance of 3.8km. The move and distance have not been counted.
The game counts the distance between logs and co-ordinates. Or in other words, under the whitewebbs log there is no "moved" distance registered. Your published log has no co-ordinates. As such the game cannot determine where it moved FROM. You can address this by editing your published log and placing the original cache co-ordinates on it.

i see what i did. all good. Thx