161. OpenStreetMap OpenTopoMap maps

OpenStreetMap maps https://forum.inaturalist.org/t/in-pursuit-of-mappiness-part-1/21864/5
would love to use maps from OpenStreetMap 22 in iNaturalist. They’re are different map styles available, for example Mapnik 22 or OpenTopoMap 7.
https://www.openstreetmap.org/ or OpenTopoMap.
The use of different map styles can be seen in Historic.Place (Monumenten) 3. Use “Base map” in the menu on the upper right.
Mapnik OpenStreetMap
OSM maps are made from volunteered open data and often more detailed than Google maps.
https://opentopomap.org/#map=5/49.000/10.000

The level of detail and accuracy varies drastically with OSM. Much of the rural U.S. for example is horrifically bad, but Europe as a whole is excellent. . I live in Italy and I’ve been using OSM for hiking for quite a while. Google Maps has absolutely no information on anything besides the “main” (paved) roads, and in the countryside even those are sometimes wrong (shows non-existing road links). This is made worse b heartily agree. Google maps quality is great in Florida, US cities but is not complete in or around many conservation areas. I find myself opening the location in OSM (that’s an option under the embedded google map) pretty often to figure out where an observation is.
https://forum.inaturalist.org/t/use-openstreetmap-maps/2588
prefer to have a third basemap option so that users can find the best way for themselves.
Geograph Germany for example: http://geo.hlipp.de/gridref/UMB0563

the website is using the Google Maps platform, plus a set of map tiles provided by Google, plus a set of aerial tiles provided by Google, right? the Android app uses a Google APK, plus the Google aerial and map tiles, i think.

so if you all are wanting the OSM tiles, then the OSM tiles either become a third basemap option or replace the Google map tiles, i think. the aerial tiles would still be provided by Google, and the mapping platform would still be Google, right (unless more major changes are contemplated)?

if anyone wants to seriously have a conversation about fundraising or getting a third party to donate hosting, then it might be useful to understand what kind of current demand / usage there is for the Google map tiles from iNaturalist users and how much that is growing over time. i doubt that any third party would make a commitment to host without understanding that kind of thing.

his has support among the iNat team, but we would have to either host the tiles or pay for hosting them and then re-engineer our front-end, so it would be a pretty big deal to make this possible.

penTopoMaps: more detailed maps than Google Maps and with a lot of features, which facilitate the identification of places when adding a new observation (for example a picture taken from a camera without GPS).
Especially contributors in China, where Google maps is banned, and folks like me who use Huawei devices, would then be actually able to use the app. Right now I have to go back and revisit every single observation on a web browser to be able to set the location.
PS: 16 years ago (!) I submitted a correction to Googlemaps. It is still wrong today. Also, Google still can’t find my home address and still

little movement here - I’ll be discussing this with the OpenStreetMap US community next week during the Mappy Hour - https://osmus.civicrm.org/civicrm/event/info?reset=1&id=20


GPS Apps for Android

Gaia GPS is great: https://www.gaiagps.com
https://play.google.com/store/apps/details?id=eu.basicairdata.graziano.gpslogger
https://play.google.com/store/apps/details?id=com.mictale.gpsessentials


The British Lichen Society

Secondly, upon popular demand, we are delighted to announce that the BLS AGM 2021 talks are now available via our new Youtube account. We have 17 of the talks from across the weekend available to watch. Understandably, we do not have permissions for some talks to go live, mostly due to unpublished works and data - so apologies these are not in the public domain. We hope you enjoy re-watching the wide breadth of interesting talks from across the weekend.

Thirdly, please subscribe to, and share the Youtube account - www.youtube.com/channel/UCUjl6i-3zezoIGm9vhJ1yDg/videos . We are hoping to bring more lichen content to our members and the public. That being said, if you have any content under you ownership/copyright, such as recorded talks, presentations etc. then please get in contact. We are hoping to populate our Youtube channel with useful resources.

  1. BLS AGM 2021 The Dougal Swinscow Lecture: Dr Rosemarie Honegger 12 April
    Lichens: A more than 400 Million-years-old success story.

    BLS AGM 2021 The Dougal Swinscow Lecture: Dr Rosemarie Honegger 12 April
    Lichens: A more than 400 Million-years-old success story.

  2. BLS AGM 2021 Student Talks: Alejandro Hueraca Delgado
    Unveiling the lichen flora of Northeastern Mexico.

    BLS AGM 2021 Student Talks: Alejandro Hueraca Delgado
    Unveiling the lichen flora of Northeastern Mexico.

  3. BLS AGM 2021 Student Talks: Gulnara Tagirdzhanova
    Genomes of lichen - associated yeasts and what we can predict from them.

    BLS AGM 2021 Student Talks: Gulnara Tagirdzhanova
    Genomes of lichen - associated yeasts and what we can predict from them.

  4. BLS AGM 2021 Discussion Panel: Lichens in the Anthropocene
    Lichens in the Anthropocene Discussion Panel: Neil Sanderson, Peter Crittenden, Ray Woods and Chris Ellis (chaired by Pat Wolseley & April Windle).

    BLS AGM 2021 Discussion Panel: Lichens in the Anthropocene
    Lichens in the Anthropocene Discussion Panel: Neil Sanderson, Peter Crittenden, Ray Woods and Chris Ellis (chaired by Pat Wolseley & April Windle).

  5. BLS AGM Virtual Field Meeting: Andy Acton
    Atlantic hazel woodland in Scotland

    BLS AGM Virtual Field Meeting: Andy Acton
    Atlantic hazel woodland in Scotland

  6. NoorderPlantsoen Talk of the Town #6: Over Sanne ten Wolde Columniste, het Stadspark en eindexamens

    NoorderPlantsoen Talk of the Town #6: Over escortservice, het Stadspark en eindexamens

Lazy Load Annotations

hanks for explaining how the UX is supposed to work here -- I definitely didn't understand that the annotations panel was supposed to be sticky and didn't realize a user could navigate with the left and right arrows to different obs pages when I made this pull request. I believe this is now working as expected -- the panel stays open or closed during a session whether the user is logged in or logged out, and it also remains sticky if a logged in user navigates away from the page and comes back. To achieve this, the open/closed state of the panel is now being stored in the controlled_terms reducer instead of in the annotations component. And the state of controlled terms is now being reset when a user navigates to a new observation page, so the annotations for that observation can be loaded correctly. reverted the umbrella stats code since it's not actually a query that uses pagination & therefore should only be fetched on page a good plan to me! I didn't realize when implementing per_page=0 that it might end up putting double the load on the database... I was making an assumption that fetching counts was less intensive than fetching full results and/or that users might not click on as many tabs as we think they do. I reverted all the code relating to fetching observations, species, and observers, and I kept identifiers as is so we can learn a bit about how often that panel is loaded / whether that improves or decreases performance. a good plan to me! I didn't realize when implementing per_page=0 that it might end up putting double the load on the database... I was making an assumption that fetching counts was less intensive than fetching full results and/or that users might not click on as many tabs as we think they do. I reverted all the coderelating to fetching observations, species, and observers, and I kept identifiers as is so we can learn a bit about how often that panel is loaded / whether that improves or decreases performance. Everything seems to be working well for me with these changes. A lot of the lazy loading will save queries at page load time and I think that should help make things feel faster for most users. The part that I'm hesitant about is splitting up requests for observations, observations, and species_counts into two parts - one with per_page=0 and one that fetches the first results, at least for collections and less so for umbrellas. The problem is we have the leaderboard panels pretty high up on the page and we need the first results of observations, observers, and species_counts to render those panels. Given that section is so high up, I suspect that more often than not that section will be rendered and we'll end up making requests for those data. I think it'll be overall more performant to skip the per_page=0 requests to fetch only the counts, and make single requests for those 3 things. We can try keeping it the way it is for identifiers since we don't need the identifiers list for anywhere other than the identifiers panel, and people may not be clicking on that a lot. We might even be able to run some stats after this is released to see how often the identifiers panel is loaded. If for example it were loaded for every session, then it may make sense to skip the per_page=0 request for identifiers as well, but if it's rarely used then splitting up the requests makes sense. For umbrella projects, since it doesn't have the same leaderboard as collection projects and fetches data differently for the umbrella stats, it's possible it would be overall more performant to keep the split requests. But I'm not sure that the per_page=0 query is going to be any faster than one that fetches results (on the server side - it obviously would send less data to the user). So I'm kind of torn on that and am slightly leaning to - let's just fetch the data with the counts and save the potential additional queries which may initiate large Elasticsearch aggregations. Everything else is looking good though - loading the posts, quality_grades, map, etc is all working well and could save on some queries. Thanks for the work on this - I hope it's not too much of a pain to change how observations, observers, and species_counts are loaded (if we think making the change I suggested is a good id Everything seems to be working well for me with these changes. A lot of the lazy loading will save queries at page load time and I think that should help make things feel faster for most users. The part that I'm hesitant about is splitting up requests for observations, observations, and species_counts into two parts - one with per_page=0 and one that fetches the first results, at least for collections and less so for umbrellas. The problem is we have the leaderboard panels pretty high up on the page and we need the first results of observations, observers, and species_counts to render those panels. Given that section is so high up, I suspect that more often than not that section will be rendered and we'll end up making requests for those data. I think it'll be overall more performant to skip the per_page=0 requests to fetch only the counts, and make single requests for those 3 things. We can try keeping it the way it is for identifiers since we don't need the identifiers list for anywhere other than the identifiers panel, and people may not be clicking on that a lot. We might even be able to run some stats after this is released to see how often the identifiers panel is loaded. If for example it were loaded for every session, then it may make sense to skip the per_page=0 request for identifiers as well, but if it's rarely used then splitting up the requests makes sense. For umbrella projects, since it doesn't have the same leaderboard as collection projects and fetches data differently for the umbrella stats, it's possible it would be overall more performant to keep the split requests. But I'm not sure that the per_page=0 query is going to be any faster than one that fetches results (on the server side - it obviously would send less data to the user). So I'm kind of torn on that and am slightly leaning to - let's just fetch the data with the counts and save the potential additional queries which may initiate large Elasticsearch aggregations. Everything else is looking good though - loading the posts, quality_grades, map, etc is all working well and could save on some queries. Thanks for the work on this - I hope it's not too much of a pain to change how observations, observers, and species_counts are loaded (if we think making the c
  1. OpenStreetMap maps


layers (overlays) to the maps on iNaturalist

Is there any way to add extra layers (overlays) to the maps on iNaturalist?
For example, to add Ecoregions to a Taxon Page Map.
https://forum.inaturalist.org/t/is-there-any-way-to-add-extra-layers-overlays-to-the-maps-on-inaturalist/21983 done it before, once you do a it a few times, hopefully you find it’s really not that hard. and once you’ve saved a map that you like, you could use it as a template for other maps. suppose, for example, you really like the ecoregion map that i made in the tutorial. since that map is published, you could just take it and mix in things that you want and remove things that you don’t want.
(if you read the tutorial and try unsuccessfully to make your own map, let me know, and maybe there’s something can be described differently to make it more accessible to more people.) http://leafletjs.com/

https://forum.inaturalist.org/t/in-pursuit-of-mappiness-part-1/21864/6
http://maps.stamen.com/#toner/12/37.7706/-122.3782 For over a decade, Stamen has been exploring cartography with our clients and in research. These maps are presented here for your enjoyment and use wherever you display OpenStreetMap data.
https://forum.inaturalist.org/t/new-options-for-the-inaturalist/22062/8
https://openlayers.org/

https://forum.inaturalist.org/t/map-animation-of-observations-over-time/1217/9
https://forum.inaturalist.org/t/getting-the-inaturalist-aws-open-data-metadata-files-and-working-with-them-in-a-database/22135
https://www.youtube.com/results?search_query=tiny+world

Publicado por ahospers ahospers, 10 de abril de 2021

Comentarios

No hay comentarios todavía.

Agregar un comentario

Acceder o Crear una cuenta para agregar comentarios.