![]() ![]() Then someone commented that all of my plants where in the ocean LOL so I then started moving the pin around. I care about the locality! When I first started and didn't really know what I was doing I would put in Henderson Bay and keep the default. I was the only one on the team who thought even keeping that around was important, and what's there now was a compromise between my desire to control the text used to describe the location of my observation and everyone else's desire to show standardized place names. That said, I think many consumers of iNat data would argue that anything that forces you to choose some level of accuracy is a good thing, since many scientists consider occurrence data to be unusable without that information.Ĭhanging the "locality notes" was intentional, and we're certainly curious to here if anyone else cares about that. We may be able to refine the behavior of the location search a bit, but sometimes we're just at the mercy of whatever service we're using for geocoding. ![]() They've changed their API over the years, and the different ways they provide to turn place names like "Henderson Bay, NZ" into coordinates yield different kinds of results. Getting Google to give us data we can translate into coordinate accuracy has been tough. I did a quick test to see if this is only for Henderson Bay NZ, but the same thing happens for all of the places up this way that I visit and have done observations from - the wide accuracy and the the changing of the location name from what is should be to what the maps think it is. This does not happen with the old system. In the new system also, when I finally get the pin to where I want it, it changes the locality notes from Henderson Bay, New Zealand to Houhora 0484 (which is the area and not the place) so I have to change the locality notes back to what it should be. #Photo geotag overwritten with upload location android phone fullI also always use the full map which can not be done with this new system. I then drag the pointer to where I want it and with the old system the accuracy dissapears, but not with this new system so I have to adjust the accuracy also. The majority of my obs are from Henderson Bay, NZ and when I put that it it defaults to 2991.886322 accuracy. Most of this works well for me except the map. Are there things the old observation form does for you that the new uploader does not? Are there ways we can make the new uploader better before replacing the old observation form? Let us know in the comments below or in the Google Group. However, we want to hear from you after you've tried out the new uploader. We realize this will change the workflow for a lot of you, but we think the uploader is a better experience for almost all existing users, and a WAY better experience for new users. That means linking to the uploader instead of to, and perhaps even removing the latter way to add observations all together. We released the new uploader a few weeks ago, but now we want to go one step further and make the uploader the primary way to add observations to the site. ![]() The uploader makes it super easy to add observations to iNaturalist by allowing you to simply drag and drop photo files from your computer into the browser window, and then trying to extract as much information as possible from the photos themselves so you don't have to enter it manually. Adding observations to the website can be harder than it has to be, particularly when your photos contain so much useful information before you ever even upload them to the site. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |