Can't Update State on Moveable Cache.
- mattyrx
- 850 or more found!!!
- Posts: 265
- Joined: 21 May 10 9:57 pm
- Location: The Channon, NSW
- Contact:
Can't Update State on Moveable Cache.
Hey there!
I'm unable to update the state on my movable future dated published cache GA12629. It's stuck on NSW - but should be QLD. When I edit the cache, the change isn't saved. The co-ordinates point to a QLD location. Just thought it would be nice to have it all schmick before it becomes active.
I'm unable to update the state on my movable future dated published cache GA12629. It's stuck on NSW - but should be QLD. When I edit the cache, the change isn't saved. The co-ordinates point to a QLD location. Just thought it would be nice to have it all schmick before it becomes active.
- CraigRat
- 850 or more found!!!
- Posts: 7015
- Joined: 23 August 04 3:17 pm
- Twitter: CraigRat
- Facebook: http://facebook.com/CraigRat
- Location: Launceston, TAS
- Contact:
Re: Can't Update State on Moveable Cache.
Very wierd, it seems to insist coolangatta is in NSW. Looking in to it.
- CraigRat
- 850 or more found!!!
- Posts: 7015
- Joined: 23 August 04 3:17 pm
- Twitter: CraigRat
- Facebook: http://facebook.com/CraigRat
- Location: Launceston, TAS
- Contact:
Re: Can't Update State on Moveable Cache.
I've manually changed the state for now, seems our geocoder is 100% certain it is in NSW
- The Morris
- 8500 or more caches found
- Posts: 185
- Joined: 08 November 05 10:38 pm
- Location: Portland
Re: Can't Update State on Moveable Cache.
Me too - it won't save the updated coordinates and changes the state to NSW.
GA6712
GA6712
- mattyrx
- 850 or more found!!!
- Posts: 265
- Joined: 21 May 10 9:57 pm
- Location: The Channon, NSW
- Contact:
Re: Can't Update State on Moveable Cache.
Perfect! Thanks for your help!
- caughtatwork
- Posts: 17017
- Joined: 17 May 04 12:11 pm
- Location: Melbourne
- Contact:
Re: Can't Update State on Moveable Cache.
If it's not saving the co-ords, that generally means they are dodgy.The Morris wrote:Me too - it won't save the updated coordinates and changes the state to NSW.
GA6712
PM them to me and I'll check.
S37 E144 which is what the cache has is in NSW so the state won't change.
- caughtatwork
- Posts: 17017
- Joined: 17 May 04 12:11 pm
- Location: Melbourne
- Contact:
Re: Can't Update State on Moveable Cache.
This has been changed now.CraigRat wrote:I've manually changed the state for now, seems our geocoder is 100% certain it is in NSW
We were getting the co-ords as they were listed and using the lat/lon to determine the state (as we have always done). At the borders this information is not reliable and so even though the location is in Qld, our data says it's in NSW. So I have updated the function to return the state from the geocoder. This of course will be problematical in countries that do not have states like NZ so I'll try and work something out.
- Richary
- 8000 or more caches found
- Posts: 4189
- Joined: 04 February 04 10:55 pm
- Location: Waitara, Sydney
Re: Can't Update State on Moveable Cache.
That's broken something
EDIT: I just realised I had listed them as Traditional, editing to Moveable has removed that warning about the state, so maybe the problem is only happening with trads?
One is temporarily listed at the same coords as another of my caches 200 meters from home in Sydney, and another a bit further south though neither have been placed or published yet - just getting the GA numbers to put on the dinosaurs. GA12833 & 12834.Selected State Notice: Courtesy Notice
The Cache does not appear to be in the State selected, please re-check your co-ordinates.
You may be receiving this message if your cache is near a state border. If this is the case, please disregard this message
EDIT: I just realised I had listed them as Traditional, editing to Moveable has removed that warning about the state, so maybe the problem is only happening with trads?
- caughtatwork
- Posts: 17017
- Joined: 17 May 04 12:11 pm
- Location: Melbourne
- Contact:
Re: Can't Update State on Moveable Cache.
Thanks for the report. Moveables don't do that check, but the fact that it has come up for a traditional has highlighted an issue. The API sometimes returns NSW or New South Wales depending on the data that has been coded for certain areas. In this case it was returning New South Wales so was failing the "is the state the same state" check which was comparing the listing state of NSW. It's all a bit technical but it is now corrected thanks to your report.