OpenStreetMap
Today I mapped the tiny village of Kaftall.
Kaftall does not have many houses, but they are spread all around the hill in quite a big area.
I also moved around a little and mapped some building on the surrounding areas.
“#100villagesin100days #day22”
In new version of userscript, I focused on analyzing edits. QuickLook for changesets, hotkeys, filtering changesets, mass actions and more.
Help wanted: I would be grateful if someone knows how to get into the site code and manage the map (add new objects, change layers, colors …) This would make it much easier for new features to appear. Otherwise, they will only be available in OSM-NG (:
Now you don’t need to open OSMCha for simple changesets. Tag changes will be visible directly on the changeset page.
Now you can easily check edits that are the size of a whole world:
The extension will also show whether there have been changes to the geometry and whether the objects made by the user still exist
But what if you need to check a lot of edits from the StreetComplete user? Now you can use Alt + ←/→ to navigate between user edits!
Tired of that osm.org/history spammed with big edits? Now you can hide large edits. Or filter them by user and comment.
And yes, now you don’t have to click Load More many times
Have you ever encountered a situation where you need to cancel a MAPS.ME user edits? Now it’s easy to do.
❗️ Do not engage in rollbacks of mass automatic vandalism! This will quickly make DWGs and manual rollbacks will make it harder for them to work ❗️
To reduce your worries about vandalism, the list of recent changesets highlights the accounts of moderators, blocked users and beginners.
The Internet remembers everything. OpenStreetMap is no exception.
I started my journey as an OSM contributor in August 2018. My knowledge was initially limited to the iD editor and HOT tasking manager platform, with minimal community mapathon contributions within Nigeria. Consequently, my contributions to OSM were very low and inconsistent.
In November 2023, while seeking more opportunities to volunteer and contribute to the growing OpenStreetMap community, I discovered the OM Guru fellowship organized by the Open Mapping Hub Asia-Pacific. I applied as a Mapper, which complemented my background as a Remote Sensing and GIS student.
During my six-month tenure in the fellowship, I was exposed to various aspects of mapping, from building data capturing using JOSM, to Amenities/POI mapping with Every Door, and street-level imagery capturing using Mapillary, focusing on Disaster, Humanitarian, and Climate action. Additionally, I learned and developed my skills in JOSM validation and field mapping. The weekly training sessions and webinars exposed me to more applications of GIS and Remote Sensing in open spatial data science, thus enhancing my geospatial expertise.
One significant highlight of the fellowship was the Climate Change Challenge, where OM Guru-led groups competed in 8 climate challenges. I led a team of OSM contributors, which provided me with valuable leadership and teamwork experience. I was exposed to more applications and tools within the OSM ecosystem, such as Mapswipe, Maproullete, and mapping with RapidID. I contributed to mapping high priority, disaster prone and impacted areas in Asia-pacific countries.
The OM Guru fellowship came to me at the right time, and I was fortunate to utilize this opportunity. It transformed my OSM experience and provided me with the skills and expertise needed henceforth within the OSM community and beyond. The last 6 months have been incredibly enriching, filled with knowledge and skill development. It was the best period of my OSM contributions. Moving forward, I am confident in my ability to lead mapping activities and motivated to continue contributing to OSM in general. Thank you, Open Mapping Hub Asia-Pacific, for the opportunity!
I can’t save the changes. It shows error instead
OpenStreetMap is a public good. Public goods should support all members of the public. OpenStreetMap has instead decided to forsake my fellow LGBTQ people this year by hosting State of the Map in a country where it’s illegal to be gay. This Draconian legal code is abhorrent, and the tacit support of it demonstrated by hosting an annual international conference there is equally so.
Perhaps more worrisome is that the State of the Map website seems to me to be lying about the situation. See the text at https://2024.stateofthemap.org/venue/#safety.
LGBTQ community members are allowed to enter Kenya but it is important to mention that the nation is conservative when it comes to traditions and practices and therefore public showcasing of such related acts might expose one to public criticism. Unfortunately, there are no proper legal frameworks to protect this group of people.
“Public criticism” does not begin to describe up to 21 years of imprisonment. That this is all they say on the issue is beyond troubling: it is actively misleading. I seriously hope nobody reads this, decides to attend, and is jailed in a foreign country for their sexual orientation.
I have been an OpenStreetMap contributor for 15 years, over half my life and my entire adulthood. But this is where I have to draw the line. I can no longer offer my volunteer labor for an organization that tacitly supports criminalization of my people. As such, this pride month, I have made the difficult decision to boycott OpenStreetMap for the remainder of 2024, unless the organization can commit to some meaningful action to right this wrong. I suggest all LGBTQ allies do likewise.
Travelling to Thessaloniki today and got a 10-hour bumpy bus drive ahead.
Mapping while travelling by bus is definitely a huge challenge, but I think I managed to map Hajdaraj.
I think the village includes another area close to it, but somehow it is separated in a different residential area. Ill double check to make sure I got it all.
“#100villagesin100days #day21”
Práce, úpravy, pot, a únava. Když lze spatřiti tu tmu na konci tak lze nalézt světla u té lampy ke koši vzdálené u mostu starého, tam daleko od hory mezi kopci hledící do údolí, vidím tu vodu téct, tam kam už se nikdo nepodívá. Tam kde jsem spatřil jiskru mého citu.
Welcome to the twelfth OpenStreetMap NextGen development diary.
This week brought some exciting updates and major news!
🔖 You can read my other development diaries here:
https://www.openstreetmap.org/user/NorthCrab/diary/
⭐ This project is open-source and publicly available:
https://github.com/Zaczero/openstreetmap-ng
🛈 This initiative is not affiliated with the OpenStreetMap Foundation.
We are now welcoming new contributors! To show our appreciation, we offer contributor incentives. If you’re familiar with Python, join us – it’s easy to get started!
This week, we made significant strides towards our NextGen vision. The new search functionality is nearly complete, and I’ve recorded a short video comparing OSM Ruby and OSM-NG side-by-side.
⬇ Click below to play ⬇
or click here: https://peertube.monicz.dev/w/c7Qwif6S4MpvuBBDu7x8LM
The search now toggles between global and local modes. By analyzing Nominatim responses, it determines the most relevant results for the user. We’ve also introduced a refreshed interface and new functionality.
A warm welcome to our four new contributors! Your valuable feedback has already led to notable improvements. It’s great to have you on board – let’s keep building! 👋
GPS traces are now rendered on an actual map, providing a useful point of reference and enhancing the user experience.
We’ve fixed a major issue: the white grid lines bug. This bug has been a significant problem for many users, affecting the overall OpenStreetMap experience by making it feel unfinished and unprofessional. This week, we found and implemented a solution that completely resolves this issue. Better now than never!
My development diaries highlight only a fraction of our work. For full transparency, you can always track our progress on the project’s GitHub repository. Again, thank you to the entire team for your dedication and hard work!
This week’s work was sponsored by 15 people!
8 donors on Liberapay, and 7 on GitHub Sponsors.
Thank you for your support! You are the foundation of our work. 💪
Please consider supporting the OpenStreetMap-NG development with any amount. As a thank you, you will be eligible for the unique OpenStreetMap-NG Founder profile badge. You will also help to push the project forward 🏋.
Na oficina, foram abordados: conceitos importantes de mapeamento colaborativo, modelo de dados, editores e aplicativos para dispositivos móveis, download e upload de dados; e demonstração de uso do editor iD e dos plugins do QGIS (OSMDownloader, QuickOSM e QuickMapServices).
Os arquivos da oficina e um roteiro para pŕatica estão disponíveis em português, na pasta virtual.
https://www.openstreetmap.org/node/9735481224
IVIDES.org® é uma marca registrada.
At the moment I’m only doing small edits, or edits using StreetComplete. I got frustrated by some people making bad edits which persuaded me there were other things that I could do rather than editing OSM.
Particularly annoying behaviours for me:-
My main goal with editing OSM is to improve route planning on foot, bicycle, or public transport, hence why I’m keen to get surface, tracktype, smoothness, access, and construction tags correct.
I can not believe it that it has already been 20 days into the challenge and I have mapped over 30 villages so far. For the next five days I will be in Thessaloniki with a group of Wikimedians from the Balkans and I hope I manage to map every day, but if I don’t, I promise I will catch up.
If somebody following this want to catch up and learn or contribute to enriching Wikipedia, Commons and Wikidata from 26 to 30 June, reach out and ill let you know where you can find us.
Today I mapped Perkola and the surroundings. Perkola was partially mapped, so I moved around the map and mapped some other areas too.
“#100villagesin100days #day20”
We have started to export and upload contribute all the GPS Routing Data we have collected from our motorcycle 360* data recorder for [Vietnam Street View project] (https://streetview.vn).
Check our our Trace History upload in here: (https://www.openstreetmap.org/user/openmap-vn/traces).
The data we contribute will partly support the construction of the navigation process for projects using the open map OSM.
We all know that you should never map for the renderer and you should only map what is on the ground. But I think I’ve found the third sin, changing the ground to match the map. This nine year old way is a service lane with a name, but doesn’t give a source for the name. Doing a survey showed no signs and historic photos show it as without signs. So I contacted the local council, City of Charles Sturt and asked if they could erect signs, which they have.
I don’t feel the least bit guilty. 😊😊😊
Today I mapped Leminot a village with a population of 860, in Korçë.
“#100villagesin100days #day 19”
Walked into town and along seafront down to Lancaster Gardens.
dsx dc fce qd
Wi fi 5G
Good news! Heavy goods vehicle and HGV have been accepted into the Oxford English Dictionary as of this month. Now that these are proper British English words, we can finally tag all those truck restrictions we’ve been holding off on.
The Creative Commons Zero (CC0) waiver is, in my opinion, the most free way to release open-source software. Unlike licenses that impose conditions on the use, modification, or distribution of software, CC0 allows me to waive all my rights to limit what users can do with the software. It effectively places the work in the public domain. This absolute waiver ensures that the software can be freely used by anyone, for any purpose, in any way. Here’s why I choose CC0 when releasing open source software and why I cannot – and will not – grant permission to use my CC0 software.
Other licenses impose various requirements on using software, such as:
In contrast, CC0:
This complete freedom fosters innovation, as developers can build upon CC0-waiver software without worrying about legal ramifications or compatibility issues with other licenses.
That means:
This last point (and sometimes these last two points) often gives open-source developers heartburn. However, I feel that I cannot prevent people I don’t like from using my open-source contributions without also harming the good that comes from my contributions being widely available for use. Broad adoption leads to a more vibrant and diverse ecosystem of software, where software can be reused and repurposed in innovative ways, driving technological advancement, and resulting in services and applications that make people’s lives better.
In some countries, you either cannot legally put software in the public domain, or “it’s complicated,” due to legal concepts that, as an American, I cannot even begin to comprehend. This can complicate or even prevent the dedication of software to the public domain. To address these legal complexities, CC0 attempts to waive as many rights as possible, providing the most free fallback license for jurisdictions where a public domain waiver is not recognized.
It is reasonable that open-source contributors want credit or attribution for their contributions, either for their résumés and career advancement, or simply out of pride. However, the desire for credit should not overshadow the potential benefits of contributing to the common good. For CC0-waivered software, credit is not a mandatory requirement, which can sometimes be perceived as a drawback. But this very aspect also eliminates any barriers for the adoption and use of the software, ensuring that the work can be freely incorporated into other projects without the need for complicated legal considerations.
By waiving all rights, authors of CC0-waivered software make a clear statement: they are contributing their work for the common good, with no expectation of control or credit. This selfless act can set and example to others to contribute similarly, fostering a culture of sharing and collaboration that benefits everyone.
CC0-waivered software prioritizes influence over notability. By allowing unrestricted use and distribution, the software has the potential to reach a wider audience and be utilized in more diverse and creative ways. This broad adoption can lead to greater impact and technological progress, ultimately benefiting the community as a whole. While individual authors might forgo personal recognition, the influence of their work can be far-reaching.
While CC0 grants complete freedom to anyone to use my software without seeking permission, my choice to not explicitly grant permission is to emphasize the point of choosing CC0 in the first place:
By releasing my software under the CC0 waiver, I have released all my rights to the work, including the right to grant or withhold permission for its use. This is not a matter of choice or preference; it is a fundamental aspect of the CC0 waiver. The CC0 waiver is irrevocable, meaning that the freedom it provides to users cannot be undone or restricted by the original author. Therefore, I cannot grant permission because I no longer possess the legal authority to do so.
True software freedom means giving up control, and CC0 allows me to do just that.
I started my journey in OSM Mapping contribution in September 2020. I have worked in multiple OSM HOT Tasking projects in ID editor and JOSM. The community has been a blessing for me as it was more engaging and conscious of OSM mapping and having a journey making the world a better place through OSM Mapping.
At the end of December 2023 Open Mapping Hub- Asia Pacific hosted a program call to all active contributors to embark on a journey with AP-Hub of fellowship of active mapping and community engagement with AP-Hub network and OSM community. I passed the exam with joyous remarks. I was selected for Mapping track out of 15 been selected for the Mapping Track of OM Guru Fellowship. There was 3 different track set by AP-Hub, one Mapping track (tasked for mapping), 2nd Validation Track (tasked for validation of OSM Mapping), and 3rd Training track (Tasked for training participants). On first month, we had 100 task mapping in HOT Tasking Manager. It was a rigorous mapping in Philippines, Vanuatu and Micronesia. On 2nd month, we have worked on Everydoor App POI collection. I have roamed around my neighborhood to taking detailed data of the POIs. On the 3rd month March 2024, we worked on Mapillary of 500 images. Then on 4th month April, we worked on QGIS mapping, before and after image of OSM Mapping and 100 mapping tasks in HOT Tasking Manager. On 5th month May 2024, we validated 200 tasks in HOT Tasking Manager.
The entire journey had made me a consistent mapper and having learnt many new applications to contribute to OSM Mapping, I am grateful to AP-hub for the amazing opportunity.
