Fixed problem 2. Definitely was a bug. The map on the photo page was showing the marker for the centre of Karang Asem, instead of the precise location where you mapped it. Sorted that little problem, so it's right now.
Will have to look into problem 1 a bit more.
Oh, problem 1 I think is somewhat expected behaviour.This is just a naming thing. The lat / lon for "Zhaoxingxiang, Liping, Qiandongnan, Guizhou, China" is in fact - 25.906784 , 109.179352.
The name "Liuzhou, Guanxi, China" is used only to name the location and that stays the same. If that is inaccurately named, then this is due to Flickr having that location incorrectly mapped (that's where we get our location names from). More on that issue in this thread (post 3 explains it in detail).
Trip map location names ARE however taken from Google (or you can change them to whatever you want). That is fine in that environment, but for the photos, we prefer to have photos grouped under one common location name and this is the way to achieve that.
Hope that explains it!
Yup, (2) is fixed now... cheers!
With (1), I changed to (-25.906784 , 109.179352) in the trip map & that put the stop into the Indian Ocean off the coast of WA, Australia? So I changed it back to (25.906784 , 109.179352). & matched the trip map & photo co-ord's. The only problem now is when I click the location on the trip map, the attached photo doesn't come up in the info window that is opened. As for the technical reasons, I would go with whatever you suggest as it's certainly 'not' something I'm good at... lol
Oops, didn't mean to say it was -25 . That was meant to be a dash pointing to the correct coordinates. heh.
Just to say that what you had already was correct, so when it seemed like it wasn't updating the location - in fact it just didn't really have anything to update, so nothing changed!
And good news, the problem for the first one was very similar to the other problem. Also only picking up photos based on the centre of Liuzhou, instead of the actual location of the photo. Fixed that little bug as well! Yay! Thanks for alerting us to it