4 ms·

Pro-tip: If you're uploading on the web browser and your pic doesn't have GPS coordinates, set the location before trying to identify the species. Setting the l

Pro-tip: If you're uploading on the web browser and your pic doesn't have GPS coordinates, set the location before trying to identify the species. Setting the location helps the AI limit it's suggestions to the geographic area. Another buried feature is being able to view your observations and species in a tree view. Go to Dashboard -> Profile -> Species (under your profile picture) Here's mine [0]. I really like how I can drill down the taxon tree and filter to see just species and/or observations at any level of the tree. Edit: Oh, and be careful if you're worried about metadata in your pictures. iNat doesn't strip it out. I actually kind of like that -- after poking around, it helped me identify my next camera purchase. But Somebody could totally dox me (well, de-anonify me) with the metadata in some of my pictures.... [0] https://www.inaturalist.org/lifelists/dolfindave?view=tree&tree_mode=full_taxonomy https://www.inaturalist.org/lifelists/dolfindave?view=tree&t...

flandish 4y ago
Ohh cool. Thanks for the insight! Yeah a photo in a park is fine… a photo in a home, maybe different lol.
- shagie 4y ago
  When I've done GPS stuff with photos in houses, I've lopped off decimal digits until the circle which it represented was sufficiently large enough. I typically lop to one decimal digit to give "close enough, but not exact". http://wiki.gis.com/wiki/index.php/Decimal_degrees http://wiki.gis.com/wiki/index.php/Decimal_degrees
  - daveslash 4y ago
    That's interesting... I didn't realize that it worked that way. For example, I just assumed that something like 32N, saved in an int, would be interpreted the same as 32.00000000N -- I didn't realize that the number of decimal places implied precision/significant digits. I suppose it's not surprising, and it makes sense, but I hadn't really thought much about it before. I also suppose there are probably systems out there that don't work with Decimal-Degrees and do assume 32 == 32.000 because the devs weren't aware. Thanks for sharing!
    - shagie 4y ago
      Relevant XKCD - https://xkcd.com/2170/ https://xkcd.com/2170/ For some fun with geogson and unintended precision - https://rapidlasso.com/2019/05/06/how-many-decimal-digits-for-storing-longitude-latitude/ https://rapidlasso.com/2019/05/06/how-many-decimal-digits-fo... > Recently I came across this tweet containing the image below and it made me laugh … albeit not in the original way the tweet intended. The tweet was joking that “Anyone is able to open a GeoJSON file” and included the Microsoft Word screen shot seen below as a response to someone else tweeting that “Handing in a project as @GeoJSON. Let’s see if I get the usual “I can’t open this file” even though […]”. What was funny to me was seeing longitude and latitude coordinates stored with 15 decimal digits right of the decimal point. Also of interest in precision - https://gis.stackexchange.com/questions/8650/measuring-accuracy-of-latitude-and-longitude/ https://gis.stackexchange.com/questions/8650/measuring-accur...

flandish 4y ago

Ohh cool. Thanks for the insight! Yeah a photo in a park is fine… a photo in a home, maybe different lol.

shagie 4y ago
When I've done GPS stuff with photos in houses, I've lopped off decimal digits until the circle which it represented was sufficiently large enough. I typically lop to one decimal digit to give "close enough, but not exact". http://wiki.gis.com/wiki/index.php/Decimal_degrees http://wiki.gis.com/wiki/index.php/Decimal_degrees
- daveslash 4y ago
  That's interesting... I didn't realize that it worked that way. For example, I just assumed that something like 32N, saved in an int, would be interpreted the same as 32.00000000N -- I didn't realize that the number of decimal places implied precision/significant digits. I suppose it's not surprising, and it makes sense, but I hadn't really thought much about it before. I also suppose there are probably systems out there that don't work with Decimal-Degrees and do assume 32 == 32.000 because the devs weren't aware. Thanks for sharing!
  - shagie 4y ago
    Relevant XKCD - https://xkcd.com/2170/ https://xkcd.com/2170/ For some fun with geogson and unintended precision - https://rapidlasso.com/2019/05/06/how-many-decimal-digits-for-storing-longitude-latitude/ https://rapidlasso.com/2019/05/06/how-many-decimal-digits-fo... > Recently I came across this tweet containing the image below and it made me laugh … albeit not in the original way the tweet intended. The tweet was joking that “Anyone is able to open a GeoJSON file” and included the Microsoft Word screen shot seen below as a response to someone else tweeting that “Handing in a project as @GeoJSON. Let’s see if I get the usual “I can’t open this file” even though […]”. What was funny to me was seeing longitude and latitude coordinates stored with 15 decimal digits right of the decimal point. Also of interest in precision - https://gis.stackexchange.com/questions/8650/measuring-accuracy-of-latitude-and-longitude/ https://gis.stackexchange.com/questions/8650/measuring-accur...