While trying to drawn down the backlog of flagged atlases and create some new ones, I’ve run across some specific boundary-related inaccuracies:
The Bonin Islands (or Ogasawara Islands) don’t appear to be included in the atlas polygons at all
The Volcano Islands to their south are included in Shikoku. Both island chains are part of Tokyo prefecture.
The polygon for Isla Tortuga, east of Baja California, is located in the wrong place, as is that for Isla San Pedro Martir to the north.
Akimiski Island is included as part of Kenora, Ontario, but should be part of Qikiqtaaluk, Nunavut
Fatu Hiva and Motane or Moho Tani lack boundaries; these islands are part of the Îles Marquises, French Polynesia, and immediately adjacent to the mapped islands.
The Prince Edward Islands (including Marion Island), part of South Africa, are missing from the map.
Machias Seal Island, in the Gulf of Maine is missing from the map
Islas Marietas, off the coast of Nayarit, Mexico are missing from the map
Further atlas-related glitch: when selecting the State of Santa Caterina, in Brazil, Santa Caterina, in the State of Amazonas, is automatically selected at the same time.
Hm, the boundaries look fine on each place page, but I’m running into issues with atlases. For example, I’m trying to add the Itapiranga in Amazonas to the atlas for Bradypus tridactylus, but I can’t select the place. Just to try it out, I also exploded Santa Catarina and tried to add the Itapiranga there, but no luck either.
I can select the Itapiranga in Amazonas, but it’s still not working for the Itapiranga in Santa Catarina.
Are the atlas shapes stored separately from the boundaries for the places? That is, did correcting the shape of Amazonas here correct the atlas shape, or was that a separate step?
The inability to clicking Itapiranga in Santa Catarina seems to have something to do with the UI on the Altas page but not the underlying data.
The atlases just use standard places. So if you change the standard place boundaries the atlases change. similarly if you add/remove a species to a standard place default checklist the atlases change. So if you wanted, you could add 3-toed sloth to the Itapiranga in Santa Catarina default checklist and that place would show up green, even though the UI won’t let you click on it…
@choess do you think you could convert your original post to a wiki? I’d like to add other issues and that might be a nice way to keep them all together.
I’m having trouble with trying (i.e. cannot figure out how) to add a place around Mexico City to an atlas. there is a single observation that keeps getting un-covered by the atlas selected places.
in the atlas map view, it seems to be inside the iNaturalist place boundary for the Distrito Federal, BUT is just barely outside it if going by the Google Maps boundary:
is this an issue with the place polygons? some weird error only particular to this case? help would be appreciated, since if the butterfly identifiers/curators do want to commit the split that depends on this atlas, I don’t want this observation to be bumped to genus for erroneous reasons…
(I apologise if the mention of a specific observation is not allowed due to strict interpretation of forum rules, but I am attempting to help with this record since it is the only one affected by this problem, not calling out the user; there is no issue with the observation itself.)
sorry to double-post, but I need to make sure the atlas is fixed before committing these changes. could someone else verify that Lon vitellina is listed as “present” in the Tlalnepantla de Baz checklist: https://www.inaturalist.org/listed_taxa/126844110
despite the history saying that the last action was adding it? or if you don’t see that, would you kindly be able to post a screenshot of it active in the atlas?
