OpenStreetMap
This entry will be constantly updated based on my findings in USA.
Please be advised that a correct solution depicted below is not the only one. You are welcome to brainstorm in the comment section!
Hint: Right click on the picture to view in a new tab so you will see it in a better size.
1:
Wrong:
The reason why the intersection originally looks like this is to prevent reckless driving in rural area.
| Versões: English / | French / | HOT website (English) |
Juntamente com as comunidades/contribuintes locais do Vietname, Madagáscar e Moçambique, e os Centros Mapas Abertos (Ásia-Pacífico, e África Oriental e Austral), tenho muito prazer em partilhar convosco a colaboração Projecto: Localização como um facilitador de inclusão e participação (também disponível em Francês, Português e Espanhol).
A barreira linguística e a omissão do inglês coloca os não falantes de inglês em desvantagem sistémica nas comunidades de mapeamento aberto e nas actividades humanitárias de mapeamento aberto que o HOT tenta apoiar, resultando numa falta significativa de participação e impacto (Gayton, 2021) .
Acreditamos que a localização linguística permitirá a inclusão e participação de grupos subrepresentados no mapeamento, diálogos e outras actividades humanitárias de mapeamento aberto.
O nosso objectivo é desenvolver dados de base para informar uma estratégia de localização*** auto-sustentável para colmatar a lacuna entre linguagem e acessibilidade dos recursos de cartografia aberta que servem as comunidades envolvidas no trabalho humanitário / de desenvolvimento (ver Países Prioritários do HOT).
Iremos realizar pequenas experiências (isto é, fluxos de trabalho de tradução, e compromissos) com comunidades locais para testar como a localização de recursos poderia funcionar nas principais línguas de 3 países prioritários: Vietname (Tieng Viet), Madagascar (francês) e Moçambique (português).
| Versions: English / | Portuguese / | HOT website (English) |
Avec les communautés locales/contributeurs du Vietnam, de Madagascar et du Mozambique, et les centres Open Mapping (Asie-Pacifique, et Afrique de l’Est et Afrique australe), je suis très heureux de partager avec vous la collaboration Projet : La localisation comme outil d’inclusion et de participation (également disponible en français, portugais et espagnol).
La barrière de la langue et le choix par défaut de l’anglais désavantagent systématiquement les non-anglophones dans les communautés de cartographie ouverte et les activités de cartographie ouverte humanitaire que HOT tente de soutenir, ce qui entraîne une participation et un impact manqués (Gayton, 2021).
Nous pensons que la localisation de la langue permettra l’inclusion et la participation des groupes sous-représentés dans la cartographie, les dialogues et autres activités de cartographie ouverte humanitaire.
Nous visons à développer des données de base pour informer une stratégie de localisation autonome afin de combler le fossé entre la langue et l’accessibilité des ressources de cartographie ouverte qui servent les communautés impliquées dans le travail humanitaire / de développement (voir [Pays prioritaires de HOT] (osm.wiki/Humanitarian_OSM_Team/Working_groups/Community/Terms_of_Reference#How_we_define_our_community_focus)).
Nous allons mener de petites expériences (c’est-à-dire des flux de travail de traduction et des engagements) avec les communautés locales pour tester comment la localisation des ressources pourrait fonctionner dans les principales langues de trois pays prioritaires : Vietnam (Tieng Viet), Madagascar (français) et Mozambique (portugais).
Juin-Juillet: Brainstorming initial, mise en place et analyse des besoins (terminé)
| Versions: French / | Portuguese / | HOT website (English) |
Together with the local communities/contributors from Vietnam, Madagascar and Mozambique, and Open Mapping Hubs (Asia-Pacific, and East & Southern Africa), I am very happy to share with you the collaboration Project: Localization as an Inclusion and Participatory Enabler (also available in French, Portuguese and Spanish).
Language barrier and the default to English puts non-English speakers at a systemic disadvantage throughout open mapping communities and humanitarian open mapping activities that HOT tries to support, resulting in significant missed participation and impact (Gayton, 2021) .
We believe that language localization will enable inclusion and participation of underrepresented groups in mapping, dialogues and other humanitarian open mapping activities.
We aim to develop baseline data to inform a self-sustainable localization strategy to bridge the gap between language and accessibility of Open Mapping resources that serve communities involved in humanitarian / development work (see HOT’s Priority Countries).
We will be running small experiments (i.e. translation workflows, and engagements) with local communities to test how localisation of resources could work in the main languages of 3 priority countries: Vietnam (Tieng Viet), Madagascar (French) and Mozambique (Portuguese).
I can’t find my neighbors house or my front yard. Yep! This seems perfect for me
## G. Montesanto leg.
It was great going through the challenges in part 1. We have a few more interesting tasks as the next maproulette challenges for you all. They are for mappers who are just starting or are experienced. Here are the tasks for you all:
Put your mapping hats on and let’s do some mapping!
We would love to hear suggestions and feedback from you on these tasks so that we could better ones next time.
W tym poradniku dowiesz się, jak przy pomocy programu QGIS i wtyczki mbtiles w JOSM zmienić wybrany rysunek projektowy…
…w podkład do JOSMa.
HOT Tasking Manager (TM), SimpleTaskManager (STM), and Divide and map. Now. (damn) are tools for collaborative mapping, with different philosophies and different approaches. In this diary, I discuss some issues of the first two from the perspective of the third one.
DISCLAIMER: I’m the damn project developer.
Which issues to consider: I filter out bug reports and issues that oppose the damn project philosophy. Then, I pick up issues I think are interesting and categorize them, describe the category, and provide some comments how the particular issues are or would be solved.
About naming: TM’s and STM’s project corresponds to damn’s area. TM’s and STM’s task corresponds to damn’s square. Where TM uses validation, damn uses review.
There are many issues of both managers that wouldn’t be an issues for the damn project because of it’s design. Let’s quickly recap that design.
There are areas divided to squares. Any change to an area is stored as commit. So, creating new area leads to creating new squares as well as new commit with to map type for each square. During collaborative mapping, new commits of different types like locked or done are added with area and square identifiers, always updating particular square of the area. It’s not possible to delete something.
One of OpenStreetMap’s greatest strengths is our worldwide platform backed by a worldwide community. As such we need to give our full support to our mappers around the world, including the ones in countries whose cultural and legal norms you may dislike and wish to work against. Supporting these mappers isn’t an endorsement of those norms; rather it is a commitment to worldwide mapping.
Any suggestion of ostracising countries would be a stand against inclusion of mappers, depriving them of the opportunity to talk about their specific issues both with each other and with the rest of the world.
StreetComplete is an application allowing to contribute to OSM by answering simple question. It makes possible to contribute without learning about tagging schemes and without learning how to handle interface of more general editor like JOSM, iD or Vespucci.
I contributed to StreetComplete in past. Recently I received a grant that will allow me to spend more time on improving it.
Grant is funded by a NLnet as part of NGI Zero grants. StretComplete grant is mentioned by NLnet at https://nlnet.nl/thema/NGIZeroDiscovery.html and https://nlnet.nl/project/StreetComplete/ pages. It will allow me to spend far more time on improving StreetComplete.
I will participate in project as usual, sending pull requests that will be reviewed and accepted (or rejected) by StreetComplete author, Tobias Zwick and minor changes commited directly (and still subject as review).
Note that I selected topics of work to be done (based mostly on open issues on the bug tracker) on my own, and it was accepted without any requested changes. I am sole beneficiary of the grant.
Total grant will depend on how much I will manage to do before deadline.
See osm.org/user/Mateusz%20Konieczny/diary/368849 for earlier, very similar entry.
I created osm.wiki/NLnet and submitted it OSM weekly as it seems to me that other OSM projects also may be funded.
I just converted over from mapbox tiles. I think I did everything right?
Looks nice to me Fediverse Observer
A well.. appears I cant accurately add building to this map since the satellite images are old. The images available show the site before the foundations where put so it is hard (or maybe impossible) to add buildings without any reference point (plus I’m new to this so I know nothing).
Anyway, I’ll just keep studying the site and hopefully, I may figure out a way to add the buildings.
People should be wary of the imagery offset especially using high resolution products. In OpenStreetMap, Mapbox often provides high resolution images in densely populated areas within the US. However, just because Mapbox provides high resolution imagery does not mean the offset is not a thing. In fact, Mapbox has created a lot trouble as it pretends to be accurate but actually not.
Keep in mind that whenever your local municipality has its own orthoimagery published, always use it to draw features (of course it has to be compatible with OpenStreetMap, if it is missing in iD, maybe you can bring it in). The imagery could be dated, but it is accurate. Your local municipality will spend more time to process with the data. These “commercial” providers, like Mapbox or ESRI or Bing, do not have a lot of time to carefully examine everything in a specific area especially when it is not that popular.
I’m going to post an example here. The orange area is OSM data fetched by QuickOSM in QGIS, drawn by a random person who has not noticed the offset for years.
De Felipe
L’association OpenStreetMap France a été créée le 8 octobre 2011, il y a 10 ans.
C’est l’occasion de revenir sur cette première décennie et pour commencer sur la génèse de l’association.
La première trace de discussion sur le principal canal de communication (talk-fr) date du 16 novembre 2009:
https://lists.openstreetmap.org/pipermail/talk-fr/2009-November/016188.html
Robin Prest pose la question “Voulez vous créer une association OSM France ?” après que Pieren et Etienne Chové mentionnent “une association française qui mettrait en place des serveurs (avec peut-être un soutien pour l’administration) et qui a surtout besoin d’un porte-parole”. Le sujet des serveurs est en effet important à l’époque, pour mettre en place des services (comme osmose) et les dons ne sont envisageables qu’avec une structure officielle. L’Université de Nantes fera ainsi le “mirroir” pour le don d’un lot de serveurs venant de chez free (voir: https://lists.openstreetmap.org/pipermail/talk-fr/2009-November/016284.html).
Un vote est lancé sur un Doodle… une cinquantaine de “OUI” se dégage en quelques jours.
Le mode de fonctionnement proposé par Robin est le suivant:
D'ailleurs, je suggère que les statuts prévoient de "soutenir" le projet
plutôt que de le "diriger" - référence au message de **sly** sur la république
bananière - ce qui permet une certaine souplesse dans le fonctionnement
général. D'ailleurs, on peut avoir OSM tel quel avec sa communauté de plein
de gens anonymes qui participent sans se prendre la tête avec le côté
administratif et une assoc OSM france dont un des buts est de soutenir le
projet d'une façon ou d'une autre (par l'hébergement via des serveurs, par
la collecte de dons, par les communiqué de presse, par ses relations, etc),
l'un n'empêche pas l'autre.
Just realized that I didn’t notice that on Tuesday (the 5th) I sent out the 10’000ths welcome message to a contributor.
I’ve been doing this for SOSM since December 2013, nearly 8 years ago, averaging a bit over 100 messages per month.
I’ve discussed our expectations (or rather the absence of them) before see osm.org/user/SimonPoole/diary/40071
PS: The happy “winner” was osm.org/user/JFischli
I was surprised no one had added the historic Green Gables house near the intersection of U. S. 1 (Harbor City Blvd) and Hibiscus Ave.
Added that and may add more buildings of historic interest later.
Dear HOT Voting members, HOT staff, HOT volunteers and people interested in HOT, Humanitarian and Open Mapping,
I hope this message finds you and your loved ones well and healthy. I would like to present to you my end of term report as President of the Board. On 10 February 2021 I shared a detailed annual report for 2020. In this new report I would like to focus on challenges, ongoing efforts, key learnings and achievements.
Of all the anticipated challenges while participating as a Board Member, a global pandemic was not on our list. It was a difficult and challenging time for Voting members and staff and the Board members were not an exception. Board members, like many other people, were facing difficult situations with loved ones getting infected, trying to find a balance between working from home and taking care of their families, among many other difficult situations.
This could be one of the reasons why not every Board member was contributing equally. Being part of a Board requires certain commitments such as time and asynchronous participation to be able to be part of the decision making process, often outside of Board meetings. Some Board members were not responsive or slow on providing feedback in discussions, this caused delays in progress and decision making.
My suggestion to future Board participants is to review in advance the Board Procedures and other relevant documentation to make sure you can commit to this two year period.
.jpg){kind=small}