I’ll post another pair to see if the problem can be reproduced.
Thanks - got a country code for both this time.
No problem … but isn’t an intermittent problem worse than a consistent one?
I’ll probably have to deploy it to the live server just to see how intermittent its going to be.
Yes sorry, I should have been more helpful
@Chris_Valentine
Not sure that this is what you are all talking about - my cameras are old and I never use my Garmen anymore - it never worked well on Table Mountain
But I spotted DJs. comment and thought…
‘Today I had the need to correct a location’. My problem was much the same.
I was posting in haste and missed the - (minus) sign for the South.
So iSpot saw me as GLOBAL and the dictionary pop-down didn’t have my species listed
I think this is the reason - 3 results are offered by POWO Mine was Lobelia comosa L. not Lobelia comosa Cav.
https://powo.science.kew.org/results?q=Lobelia%20comosa
I’ll add the link to my post which may explain better
Wondering if this will be a problem if we go GLOBAL
M
The test needed to be done on the acceptance server, which has an extra level of security as its just for testing. You’ve highlighted the fact that dictionary and community are two separate things. No matter - thanks for posting.
1 Like
The additions and changes for copyright/creative commons and country code have now been pushed to the live server.
We are awaiting an updated mapping of NBN keys to GBIF codes then I’ll be deploying the latest UK & Ireland dictionary to the liver server too.
Sorry - rollover code?
Will old names or attributions be updated and will the rollover icon display the old name?
You added some complex code
OK with you now. Yes, if there was a change from the previous dictionary, that icon will again appear.