I spent 11 nights backpacking in Glacier National Park this summer (on two separate trips), and noticed that existing mapping of the campsites is minimal. Each site generally consists of several tent sites, a food preparation area with bear-proof storage (a pole for hanging or a bear box), a toilet, and usually a fresh water supply. Usually there is a schematic map of the campsite posted, like this one shown below.

While I was there, I took a number of photos of camp site maps (I have not been able to find them online from the National Park Service), and did quick GPS surveys of a few sites with my Garmin watch.

I have made a first attempt at adding a full backcountry camp site map for Hole in the Wall Camp in this changeset. My approach was:

• Place the camp itself at the main trail junction, usually where the camp map is posted, tagged as tourism=camp_site. This is the way camps are tagged in OSM now (locations are rather approximate).
• Map the paths between parts of the camp, tagged with highway=path
• Add each official tent site as a node tagged with tourism=camp_pitch
• Add the toilet with amenity=toilets. In the case of Hole in the Wall, tagged with toilets:disposal=chemical, but in most cases it will be toilets:disposal=pitlatrine.
• Tagged the food preparation area with amenity=bearproof_storage, bearproof_storage=hang. This one is not very standard, I followed an example from this forum post.

A few notes and limitations:

• The tent sites and kitchen don’t show up in the default rendering (paths and toilets do).
• Using the junction as the camp location isn’t entirely satisfactory, but you can’t tag a complex relation like all the paths, tent sites and toilets. The alternative would be to use an arbitrary polygon around the site, but that seems wrong because it doesn’t have boundaries.
• Likewise, the tent sites and kitchen area could be mapped as polygons, but that would take more effort to do accurately.
• The kitchen area usually could get tagged amenity=bench as well, but maybe that is odd to do to the same node as bear storage.
• Mapping water access with amenity=drinking_water, drinking_water=treated would probably be useful.

I think it would be useful to add more sites, but I’d like to make sure they are done consistently. I will likely try adding a few more examples for which I have good surveys.

От перекрестка автозаправки вот до этого момента дорога в ужасном состоянии

Эвакуатор недорого в Московской области – это удобный и доступный способ транспортировки автомобилей в случае поломки, аварии или необходимости перемещения автомобиля на большие расстояния. Услуги эвакуации автомобилей предлагают множество компаний, работающих по всей Московской области, и подобрать наиболее подходящий вариант можно как по цене, так и по условиям обслуживания.

Главное преимущество заказа эвакуатора в Московской области — это оперативность и доступная стоимость. Современные компании предлагают гибкую ценовую политику, что позволяет клиентам выбрать услугу, соответствующую их бюджету. На цену эвакуации влияет несколько факторов: тип транспортного средства, расстояние транспортировки, время суток и сложность ситуации (например, вытаскивание автомобиля из кювета или с места ДТП).

Чтобы найти эвакуатор недорого, стоит обратить внимание на специальные предложения и акции, которые нередко проводятся различными службами. Также многие компании предоставляют круглосуточные услуги эвакуации, что особенно важно при непредвиденных ситуациях на дороге.

Таким образом, если вам необходим эвакуатор недорого в Московской области, вы всегда сможете подобрать надежного и доступного перевозчика, который оперативно поможет с транспортировкой вашего автомобиля в любой точке региона.

incibey Halil inci

مزرعه کشاورزی پدر استخر آبیاری تحت فشار آبیاری نوین مصرف بهینه آب آبیاری با دستگاه های لینیر خطی و پ کشت باغ پسته هر سال ده هکتار اضاف به مجموعه باغات به علت کم آبی سفره های اب زیر زمینی و نیاز به اب کم درخت پسته #سیف آباد #دهستان پایین محمدآبادخره #مزرعه حاج سیف الله خراسانی و پسران #باغ پسته حاج سیف الله #جنب باغ پسته حاج آقا نظری رفسنجانی #مزرعه تأسیس سال 1364

Holy

Donner l’opportunité d’aller assister au STATE OF THE MAP ne pas donner à tous les mondes; c’est pourquoi ;je peux dire que je suis l’une des personnes le plus chanceuse d’avoir été sélectionné a la HOT OPEN Summet, la bourse pour assisté au StateoftheMap24. le STATE OF THE MAP était organiser pour la première fois en Afrique, au Kenya, Nairobi et c’était une opportunité en or pour moi de rencontré plusieurs passionner de la cartographie qui partage la même vision avec moi. Quitter la RDC; passant par l’Uganda jusqu’au Kenya, Nairobi… la route était trop longue mais ça valait la peine. Plusieurs leçons apprise, plusieurs méthodologies de la Cartographie, le StateoftheMap a toujours été un moment pas comme les autres car ça ressemble plusieurs personnes dont auparavant on avait l’habitude de parler en ligne ;

www.flickr.com/photos/201459404@N07/54007191244/in/dateposted-public/” title=”IMG_2099”></a>

Le plus excitant c’était de rencontrer ces jeunes filles aussi enthousiastes, motivée, venue du 4coins du monde ; on pouvait voir la force de donnée libre (cartographie) qui a su réunir autant des mondes.

Au State of the map (SOTM) on pouvait rencontrer plusieurs personnes parmi les quelles Benedicta a tiré mon attention, sa présentation sur le taux de pourcentage de la participation des femmes dans OpenStreetMap était tout simplement intéressante, elle a donné les piste à suivre pour amener les femmes a intégré OSM

Ça sera ingrate de notre part de finir sans remercier L’équipe de humanitarian OpenStreetMap HOT OpenSumit pour nous avoir fourni une bourse de voyage pour nous permettre d’assister à la conférence,(SOTM24) un autre remerciement particulière va à Geoffrey Katerrega et a toute l’equipe d’OSMRDC

Durch eine Website über vier Schulstraßen in Dortmund [1] und mit der Frage im Forum [2] habe ich diese mit dem Tag

traffic_intervention=school_street

versehen.

Zusätzlich habe ich auf einer uMap [3] 17 weitere Schulstraßen eingetragen, die ich im Internet gefunden habe.

Wer ein Foto der Beschilderung hat, kann es mir gerne schicken (oder einen Link teilen). Ich werde es entsprechend ergänzen. Und falls jemand weitere Schulstraßen kennt, freue ich mich über Hinweise oder Kommentare!

[1] Schulstrassen auf dortmund.de

[2] Forum

[3] Karte

It is definitely good knowing how to use field tools to map on specific projects.

There comes experience 😊 regardless of previous teaching on how to use these tools like ODK, Vespucci, Mapsme and others; in the field you definitely have to use your own discretion to relate and adjust to what is given to maintain your nobility at work.

К нему не заростет народная тропа,
Вознесся выше он главою непокорной
Александрийского столпа.

Получилось вот так:

Так же на F4

Моделировать классицистические формы довольно просто, а вот с ангелом всё намного сложнее. Если у кого-то есть лицензионно-чистая модель ангела с Александровской колонны, например для 3д-принтера, милости прошу.

Нет, весь я не умру — душа в заветной лире
Мой прах переживет и тленья убежит —
И славен буду я, доколь в подлунном мире
Жив будет хоть один пиит.

Ну или хотя бы один картограф :)

P.S. Как бы так еще главный штаб переделать, чтобы он был похож на себя?

I became interested in the issue of localizing the map of Ukraine into English and decided to raise it in several forum discussions (first, second, third) to delve into the nuances and find optimal approaches to filling out the name:en tag for objects in Ukraine.

My goal was to understand how to correctly fill in the name:en tag and determine whether it should contain a translation or transliteration. While this may seem like a technical issue, it actually has deep cultural and historical roots, and the answer is not immediately obvious. However, through the discussion, I believe I found a solution and would like to share it in this diary.

Endonyms and Exonyms: What Are They?

First and foremost, it is important to understand the difference between endonyms and exonyms.

Endonym refers to the name of a geographical object in the language of the people who live in that area. For instance, for the residents of Ukraine, the name of the capital Kyiv is an endonym. Endonyms always reflect the authentic name used by the local population.

Exonym refers to the name for the same geographical object used by people or countries outside that area. Examples of Ukrainian exonyms include Viden for Wien, Niu-York for New York, and Florentsia for Firenze. The Spanish name for the city Lviv is Leópolis, and the German name is Lemberg. Historically, such names were formed quite chaotically, influenced by various linguistic traditions or political processes.

Exonyms have a long history tied to colonization, geopolitical influence, and cultural interactions between countries. In the case of Ukraine, many exonyms used in other countries were shaped during the prolonged influence of the russian empire and the soviet union. For example, names like Kiev, Cherkassy, and many other Russian versions of Ukrainian names were incorporated into most maps and atlases of that time. Some Ukrainian names even changed under this influence and became official, such as the town Brovary, where the local villages still predominantly use the name Brovari.

Today, exonyms imposed by other states, particularly Russian ones, often elicit negative reactions in Ukraine. This topic is especially relevant in the context of decolonization and the desire to break away from the Russian linguistic legacy.

The Issue of Transliteration and Translation of Ukrainian Names

Discussions about the use of the name:en tag within the Ukrainian OpenStreetMap community have been ongoing for many years. Almost 14 years ago, the first attempts at mechanical transliteration/translation of Ukrainian names and the automatic filling in of name:en occurred after a forum discussion.

Currently, the OpenStreetMap database contains around 300,000 objects with Ukrainian names that have a corresponding name in name:en. However, for most of these objects, no actual English counterparts ever existed. These English names were created by mappers themselves. Here are examples of names I personally filled in based on Ukrainian street names in a small town:

• Kyivska Street
• Nezalezhnosti Street
• Aerodromna Street
• Molodizhna Street
• Field Street
• Lake Lane
• Peace Street
• Victory Street
• Gogol Lane
• Victory Street
• Unity Street
• Independence Street

So, how should the name:en tag be filled out? Should it be a translation, transliteration, or a combination of both? The answer to this question is mappers should not invent names in other languages. An English exonym only begins to exist when the English-speaking population of other countries starts using it, and there is written or spoken evidence of its use. Only if an exonym already exists for a particular object in Ukraine can it be added to name:en:

Endonym, name, name:uk	Exonym, name:en
Чорне море	Black Sea
Дунай	Danube
Димерчин ставок
Крим	Crimea
Закарпаття	Transcarpathia
Харитонівська сільська громада
Київ	Kyiv
Витягайлівка
Цмоки
вулиця Леонтія Свічки
2-й провулок Сергайовки
урочище Попові Корита

So, what should be done for objects that do not have an established English exonym? In my opinion, the correct approach is to provide users with a romanized endonym. This ensures the authentic representation of Ukrainian names in Latin script, without creating artificial alternative foreign names.

Romanization

Romanization is the conversion of text from another writing system into the symbols of the Roman (Latin) alphabet or a system for doing so. Romanization methods can include transliteration and transcription. The Ukrainian community has long used the official transliteration system, approved by the Cabinet of Ministers of Ukraine in 2010. This system was also adopted by international geographic naming authorities: the United States Board on Geographic Names (BGN) and the Permanent Committee on Geographical Names (PCGN) in the United Kingdom in 2019, making it universally applicable for use on English-language maps. In practice, romanization helps avoid errors related to translation or the incorrect use of foreign names.

Which Tag to Use for Romanized Names?

If an object has a name, we fill in name. If that name is in Ukrainian, we duplicate it in name:uk. If the name is Ukrainian, the next step should be its romanization and filling in the name:uk-Latn tag.

Endonym, name, name:uk	Exonym, name:en	Romanized Ukrainian Name, name:uk-Latn
Чорне море	Black Sea	Chorne More
Дунай	Danube	Dunai
Димерчин ставок		Dymerchyn Stavok
Крим	Crimea	Krym
Закарпаття	Transcarpathia	Zakarpattia
Харитонівська сільська громада		Kharytonivska Silska Hromada
Київ	Kyiv	Kyiv
Витягайлівка		Vytiahailivka
Цмоки		Tsmoky
вулиця Леонтія Свічки		Vulytsia Leontiia Svichky
2-й провулок Сергайовки		Druhyi Provulok Serhaiovky
урочище Попові Корита		Urochyshche Popovi Koryta

Not All name:en Tags Are Exonyms

Some objects have names of non-Ukrainian origin. For example, the names on the signs of restaurant chains like McDonald’s and KFC should be filled in name and duplicated in name:en.

Often, apart from a Ukrainian name, an organization may also have an official name in English. Even if the name:en is not widely used by English speakers, this name should be filled in. Ukrainian universities often have both Ukrainian and English names.

name	name:uk	name:en
McDonald’s	МакДональдз	McDonald’s
KFC		KFC
Kärcher	Керхер
Київський політехнічний інститут імені Ігоря Сікорського	Київський політехнічний інститут імені Ігоря Сікорського	Igor Sikorsky Kyiv Polytechnic Institute
Уманський державний педагогічний університет імені Павла Тичини	Уманський державний педагогічний університет імені Павла Тичини	Pavlo Tychyna Uman State Pedagogical University
Національний університет «Львівська політехніка»	Національний університет «Львівська політехніка»	Lviv Polytechnic National University

However, it’s essential to remember that we document names, not create them. One important note — not all names written in Latin script are English. For instance, the supermarket chain Varus, though written in Latin, is not an English name. It is derived from the names of the company’s founders: Valerii Kopytko and Ruslan Shostak. In such cases, name:en should remain empty.

Conclusion

Based on the forum discussions, I suggest filling out the name:en tag as follows:

1. If an English exonym exists for the object, write the exonym.
2. If there is no English exonym, leave the name:en tag empty, unless there are exceptions, as described above.
3. The name:uk-Latn tag should contain the transliterated version of the Ukrainian name.

This approach will support the natural development of English exonyms for places and geographical objects in Ukraine and help avoid populating the name:en tag with inappropriate or meaningless names.

Additionally, I have initiated a discussion on the name:uk-Latn tag in the Ukrainian section of the forum.

Last week we released Rapid v2.4, the most advanced web-based editor for OpenStreetMap. This release wraps up several months of work, includes numerous bugfixes, and a few notable features:

🈺 Improved Text Localization

Now Rapid can again be localized into different languages. The Rapid Editor project on Transifex allows anyone from the community to translate Rapid.

📷 Improved Handling of Street-level Imagery and Detections

We squashed a bunch of bugs and made many improvements to how Rapid handles street-level imagery, such as Mapillary. Now users can select a detected feature or traffic sign to learn more about it, and Rapid will highlight the imagery that shows that detection, both on the map and in the viewer. This will be especially useful for mapping pedestrian features, such as traffic signs, crosswalks, bike racks, and more.

👩‍💻 Use Rapid

👉 Bookmark Rapid and make it your editor of choice:

• https://rapideditor.org/rapid#map=2.00/0.0/0.0&background=Bing

👉 v2.4 Changelog:

• https://github.com/facebook/Rapid/blob/main/CHANGELOG.md#240

⭐️ Follow and star the Rapid project on GitHub:

• https://github.com/facebook/Rapid

❤️ Like and share:

• Twitter/𝕩 : https://x.com/bhousel/status/1834718057379643817
• Mastodon: https://mastodon.social/@bhousel/113132573097246901
• Threads: https://www.threads.net/@houselb/post/C_378WtRg4W
• OSM: https://community.openstreetmap.org/t/rapid-v2-4-released-today/118760

🫶 Happy Mapping!

Introduction:

Over the past year, I have been working as a backend developer on the Field Mapping and Tasking Manager (FMTM) project for the Humanitarian OpenStreetMap Team (HOT). My role has involved system design, feature development, and bug fixing, all aimed at enhancing the efficiency and usability of field mapping for humanitarian purposes. One of my key contributions has been developing and refining the FMTM Splitter —an algorithm designed to streamline field mapping by dividing map Areas of Interest (AOI) into manageable tasks for mappers.

In this post, I will discuss the workings of the FMTM Splitter, the challenges we’ve overcome, and how OpenStreetMap (OSM) data plays a vital role in making this tool effective for humanitarian efforts.

The FMTM Splitter: Two Key Algorithms

The FMTM Splitter is crucial for breaking down large AOIs into smaller, manageable tasks for field mappers. The goal is to ensure that mappers can efficiently collect and update information without having to cross major obstacles like highways or rivers. This makes the mapping process not only faster but also safer and more convenient for field mappers.

We developed two main algorithms for splitting AOIs:

SplitBySquare:

This method splits an AOI into equal-sized square grids based on predefined dimensions, such as 100 meter. It’s a straightforward approach that’s ideal for areas with uniform or relatively simple features.

SplitByAlgorithm:

This more advanced method is designed to split AOIs based on the number of OSM features present, ensuring that each task contains a balanced number of map features such as buildings. Importantly, the algorithm takes into account highways, railways, and waterways to avoid splitting tasks across major infrastructure, ensuring that field mappers don’t have to navigate large barriers while collecting data. When no major barriers are present, the algorithm uses K-Means clustering to divide the AOI based on the specified number of buildings, with additional steps to simplify the task boundaries for ease of use.

Where Does OpenStreetMap Come In?

So, where does OpenStreetMap (OSM) come into the picture? FMTM’s primary mission is to enhance OSM data with detailed, field-verified metadata. We might already have basic data like building outlines or roadways in OSM, but with FMTM, we can enrich these features with critical details collected by field mappers, such as:

• The materials used in construction
• The number of floors in a building
• Typical usage patterns, such as the number of people using a facility

FMTM not only imports OSM data for updating but also allows the inclusion of custom data that might not yet exist in OSM, providing flexibility for field mapping operations. This is particularly important in rapidly evolving situations like disaster relief, where field-collected data plays a crucial role in decision-making.

Lessons Learned and Future Plans

Working on FMTM has provided invaluable insights into both technical and humanitarian challenges. From system scalability to ensuring ease of use for field mappers, the project has reinforced the importance of building tools that can adapt to real-world complexities.

While the current FMTM Splitter algorithm has greatly enhanced field mapping by efficiently dividing Areas of Interest (AOIs), there are opportunities for further optimization. One potential improvement is to introduce a feature that merges smaller tasks with neighboring areas if the created task falls below the desired threshold.

Proposed Feature: Task Merging

When an area is subdivided into tasks, occasionally a few remaining buildings may be grouped into small tasks of 1-2 buildings (as there are no more adjacent buildings to form a larger group). In this scenario, we propose adding an intelligent task-merging mechanism that:

1. Detects Smaller Tasks: Identify any tasks that are below the desired area or contain fewer buildings than specified.
2. Merges with Neighboring Tasks: Combine the smaller task with an adjacent task, ensuring the resulting task is both manageable and aligned with the defined size and desired building number.
3. Retains Boundaries: Ensure that important boundaries like highways, railways, or waterways remain intact during the merging process to avoid inconvenience for field mappers.

Moving forward, I’m excited to continue improving FMTM by exploring new ways to enhance tasking algorithms and integrating more advanced data validation processes. There’s also potential for incorporating machine learning to assist in task creation and AOI splitting based on real-time data.

ODK Entities and Their Role in FMTM

One of the exciting aspects of FMTM is its integration with Open Data Kit (ODK) surveys. ODK Entities are essentially a representation of OSM features, which can be updated based on detailed surveys conducted in the field. This makes it possible to enrich OSM data with high-quality, field-verified information, which is especially important for features that are challenging to verify remotely (e.g. building materials or usage patterns).

Challenges and Solutions:

One of the main challenges we faced while developing the SplitByAlgorithm approach was ensuring that field mappers wouldn’t have to cross major highways, rivers, or other barriers. Incorporating these features into the algorithm was a complex task but crucial for effective mapping. We also had to ensure that when no such features were present, the algorithm could still divide the AOI efficiently using K-Means clustering, balancing the number of OSM features in each task.

Simplifying task boundaries was another key feature we implemented, making the tasks easier to work with in the field. By keeping task boundaries clear and manageable, we help mappers focus on collecting data rather than dealing with confusing or irregular boundaries.

Why This Matters:

By splitting AOIs into manageable tasks, the FMTM Splitter makes it easier for field mappers to add detailed, field-verified metadata to OSM. Whether updating information on schools, hospitals, or other critical infrastructure, this process helps make OSM a more reliable and informative resource for humanitarian work.

The FMTM project aligns closely with HOT’s mission of using open data to support disaster response, development, and community resilience. The improvements we’re making to the tasking manager will help teams in the field work more efficiently and contribute valuable data to the global OSM community.

Call to Action:

If you’re interested in learning more about FMTM or contributing to the project, feel free to reach out! Whether you’re a mapper, developer, or simply someone interested in the intersection of humanitarian work and open data, there are plenty of ways to get involved.

dear diorey

Didn’t do anything today sadly apart from a few streetcomplete stars

16th of September, 23:27, Poland

Mi ubicación principal de Facebook

Well, let me share my experiences at “State of the Map 2024” in Nairobi at the University of Nairobi which I must say was like the coolest place ever for a bunch of map nerds like us to meet. As far as I can tell, it’s the place where all the folks behind OpenStreetMap, get together from all corners of the world to share their experiences, get excited about the mission of making this world more navigable with the help of our maps. It was very much like attending a large family reunion with an attempt at small talk that quickly degenerated into everyone’s passion for Open geospatial data.

At the first glance at place, I could sense the energy, the vibrancy, the pulse however one chooses to describe it. It worked as if entering a beehive of mapping lovers. People had this vibe that after this buzzing, everyone was eager to get down to business and start the sessions to discuss about how they have used OpenStreetMap in the different projects in their communities. I’m telling you, the keynote speakers? They were dropping some serious knowledge bombs about how this simple and fun mapping pastime has become an orchestra for communities. Disregard, as it is not just about going from point A to B now it is also about assisting from time to time when disaster strikes and also ensuring that our cities do not became concrete jungles without any means of implementation.

And the workshops? Oh man, they were like a buffet of brains 🧠, a table full of all the things I ever studied. If it was ‘a float,’ they had it. Looking for a GIS technology fix? Check. If you’re trying to get the latest and greatest on how to increase mapping in your community? Double check. It was as if the speakers were given an interactive storybook where instead of slaying stars ✨ attendees being enlightened on the benefits of open data. Of course, one has to remember these young lads “Youth Mappers” that are also creating and developing their own mapping projects. They’re the boys and girls of the next technological age, the mapmakers of a new age too, and it is rather thrilling actually. I also had a lightening about QFIELD and QFIELD Sync.

As I left Nairobi, I could leave a part of me in Nairobi for those few days💨 I was in the city. But you know what? I’m not sad. It’s awesome now that I have this network of friends and colleagues who are virtually distributed all over the world. And we’re all united by this by the passion to make sure that where you are, you can get your hands on some of the best maps I’ve ever seen the OpenStreetMap.

Yes, so State of the Map 2024 was fun, or as fun as one can expect when getting barely any sleep for four nights in a row. It made everyone feel much closer which was good and brought back my interest in the mapping job i do. Well, guess what it is not always that you can claim that you have reduced the world to a bundle of dots with the help of digital lines, is it? Keep on mapping, folks! In a special way, I would like to thank Humanitarian OpenStreetMap Team through the HOT OpenSumit Program for providing me with a Travel Grant to make it possible for me to attend the event Another special thanks goes to Mr. Katerrega Geoffrey, and the entire OSM Kenya and OSM Ugandan teams.

God Bless!

Since the beginning of June, I have been working on researching and locating the holy wells of County Kilkenny. I have more or less identified about 213 of them which are described in sources going back at least 90 years (Schools’ Collection etc). In some cases, it is very difficult to locate them, because their location was only given as “in such and such a townland in that person’s field”, and it is very difficult to find out who owned a field 90 years ago.

In addition to that, I have more recently started an oral history project collecting people’s memories and stories about holy wells, patterns (which is a type of originally religious festival in Ireland where people do or did things in a certain pattern around a sacred site usually on the patron saint’s feast day) and other related things. I’m uploading them to Wikimedia and add transcripts, if you’re interested: Category:Oral history about holy wells in County Kilkenny.

What has that to do with mapping, you may ask. Well, apart from locating these holy wells and holy well sites which are protected monuments (and sometimes still water sources), I’m getting local place names from my interviewees as well. Names of roads, cross roads, field names etc which are also not recorded on any map yet, but are frequently still used by locals or were used in the past, so recording them now will help locate things referred to in older sources. Some of these, like Bóthar Chiaráin (Kieran’s Road after St Kieran) potentially go back 1300 years or so.

I’m also learning about the interesting etymology of house names like “The Awk” (or The Awg, not sure).

YouthMappers Pre-Event at American Spaces.

The State of the Map (SotM) 2024 in Nairobi started with the most exciting YouthMappers pre-event at American Spaces. It was clear that the conference was going to be full of inspiration and action. Our host Laura was there to welcome YouthMappers early birds from different parts of the world gathered in the venue gearing up for the day’s activities just to prepare for the conference.

Rory from the USAID made an engaging presentation on what YouthMappers do to map problems and solve them, especially in projects that have data gaps in areas such as disasters and health. He recounted some highlights from the program over nine years then we dived into an open discussion on needs for the future of the YouthMappers program. Lastly, we had Priscilla, the Leadership Fellow of the Year 2023, provided useful advice on how to get the most out of the conference, stressing the role of real communication and connections. The meeting came to a close with some pizza, socialization with new acquaintances, and expectedly new ties.

Mapathon at ESA: Mapping for a Cause (Water reservoirs)

The day didn’t end there, next on my schedule was a mapathon at the Humanitarian OpenStreetMap Team Eastern and Southern Africa hub (ESA) offices. After a quick cab ride, we arrived at ESA, ready to dive into more hands-on mapping activities. Collaborating with experienced individuals in the field of open mapping was an enriching experience, and the focus of the mapathon was particularly compelling: mapping water reservoirs for drought-affected areas in Ethiopia. The work we were doing felt purposeful and impactful, knowing that these maps could directly aid efforts to mitigate the effects of droughts. During the Mapathon we surprised Geoffrey with a birthday celebration! Cakes, pizza, and plenty of laughter filled the room as we continued mapping, all while enjoying each other’s company.

Day 1 of SotM 2024: Learning, Sharing, and Growing

The following day, the official State of the Map Conference commenced as scheduled. It was quite interesting to finally meet fellow mappers in person as well as meet new people. With our lanyards and T-shirts on, the participants were prepared for a long day of presentations and meeting other members. We were welcomed by Walter, and if you do not know him (Talaaaaaaa) That was Iconic,

There was very little time between the day sessions since they were all amazing including organizations such as TomTom UN Maps and their Asian and Pacific projects. I have to say, I was almost moved by Trufi’s presentation, an NGO that is trying to change the way we look at public transport with the help of maps. The amount of information that was provided in each session was very high and I was noting down points to be able to capture all the information being brought forth.

Days 2 and 3: Expanding Horizons, Building Futures

The remaining days of the conference were just as packed with inspiration and knowledge sharing. Also in focus were academic tracks, which offered compelling presentations on the adoption of OpenStreetMap in research and education. Lightning talks kept the energy high, dealing with a wide range of topics and being extremely short, bright, and to the point. The panels took on some of the most controversial issues in the world of mapping and resilience disasters.

The social event was amazing, from the “Nganga” buses filled with music to games, the awarding ceremony, as well as food and drinks. The efforts made by the organizers, sponsors, and speakers in making the conference both informative and participatory are commendable. I departed from Nairobi feeling thankful and knowledgeable, with inspiration to carry on the spirit of open mapping in achieving sustainable development goals. Special thanks to HOT Un summit for making my participation possible, and to all the amazing people who made these days unforgettable. I’m already looking forward to what’s next—see you all in Manila in 2025!

WATCH MY VLOG HERE

Through this initiative, GeoTE Tanzania focuses on integrating OpenStreetMap (OSM) into academic curricula through five-week Field Training sessions with YouthMappers and academic partners. This program emphasizes practical application and problem-solving using OSM data across disciplines such as wildlife, forestry, agriculture, rural and urban development, and environmental studies. By partnering with universities like Sokoine University of Agriculture, GeoTE facilitates hands-on learning experiences that prepare students to address community challenges with geospatial techniques. “Incorporating OpenStreetMap into Academic Curricula: Insights from GeoTE Tanzania’s Five-Week Field Training with YouthMappers and Academic Partners” explores the transformative role of OSM in academic settings and community development. GeoTE Tanzania’s approach to integrating OSM into academic curricula revolves around practical application and problem-solving, empowering students to leverage geospatial data for real-world impact. The program’s structure emphasizes collaboration with academic partners and organizations like YouthMappers to deliver comprehensive Field Training sessions lasting five weeks. These sessions serve as immersive learning experiences where students apply OSM data and techniques to address community challenges across various domains, including wildlife conservation, forestry management, agricultural development, and urban planning.

Through step-by-step mentorship on project ideation and execution, students gain proficiency in using OSM as a tool for spatial analysis and decision-making. The program’s focus extends beyond technical skills to cultivate critical thinking and problem-solving abilities essential for effective community engagement.

A cornerstone of GeoTE’s approach is its partnership with academic institutions like the Sokoine University of Agriculture, where Field Training sessions are integrated into the academic calendar. This collaboration ensures that students receive academic credit while gaining practical experience in OSM mapping and analysis.

GeoTE Tanzania’s experience offers valuable insights into the potential of OSM to enhance academic curricula and foster community development. By equipping students with OSM skills and empowering them to address local challenges, GeoTE contributes to building a sustainable ecosystem of geospatial practitioners capable of driving positive change in their communities.

Through case studies and testimonials, and the motive to expanding this approach we invite institutions and partners to collaborate with us in expanding and sustaining the Field Practical Training program, ensuring more students gain vital geospatial skills to solve pressing community challenges

WATCH THE FPT 2024 VLOG HERE

BATAS DESA WANA REJA DENGAN WANA ARUM RIMBO ULU TEBO