🚘 أرجو أن تكون مده حفظ المسار أكثر من يوم واحد على الأقل أن تكون مده حفظ المسار شهر وبالتالى تكون ممتازة جدا جدا جدا وهذا للضروره القصوى وهذه الميزة كذالك تفيد فى أشياء كثيرة جدا لمستخدمى الخرايط وموظف المندوب الذي يتجول فى الشارع وعلى المحلات🙏🙏🙏

It is a privilege to address 2020’s humanitarian OpenStreetMap Summit today. This year marks HOT’s 10th anniversary, and my own 5th anniversary with HOT starting from 2015. Today’s theme is the past, present and future of humanitarian OpenStreetMap and we have been thinking a lot about the future.

I wanted to share my Summit address (which you can watch here) on an OSM diary simultaneously, so that people can engage in the comments if they want to.

This is something of a statement of intent for HOT within the humanitarian and OpenStreetMap ecosystems and, while it has been shaped by many conversations with community groups, collaborators and contributors in the universe in which HOT exists, it only seeks to represent my own perspective and some of the recent thinking within HOT the NGO. Please think of it as an early draft and a contribution to a conversation.

I also acknowledge that HOT’s presentation of itself has increasingly highlighted our successes while smoothing over or not acknowledging challenges and failures. Today’s Summit features “failfest” sessions for the first time where friends and colleagues are sharing learnings from where they didn’t necessarily get it right. This statement is not about what we’ve gotten right, but about how we’d like to embrace a stronger culture of feedback and learning and hope that, by doing so, we can achieve great things, with all of you.

This year, we received the phenomenal news of our selection as one of eight world-changing ideas by TED’s Audacious Project. In 2019, the HOT voting members told us they wanted an area home to one billion people living in countries experiencing high risk of disaster or high poverty levels, added to OpenStreetMap. We took them seriously and pitched to Audacious Project investors the idea of mobilising one million humanitarian OpenStreetMap contributors as a way to achieve this. After months of work and multiple stages of application and assessment, several extraordinary philanthropists behind Audacious invested in this vision.

However, we know that even if these headline ambitions are achieved, we will have failed if there are not also active and sustainable OpenStreetMap ecosystems in many of the 94 priority countries once the Audacious Project finishes in 2025. The approach over the next five years must be community-centred and strive for local sustainability and local power as key outcomes.

This is a gamechanger for HOT and, hopefully, for the ecosystem in which we exist. The project funding model that we’ve relied upon in the past has meant an underinvestment in longer-term community support and contributions. This can now change. But, before it does, we know that serious self-reflection is needed.

First, we need to recognise what HOT is and isn’t. Ten years ago the Humanitarian OpenStreetMap Team could more or less describe all humanitarian-focused OpenStreetMap contributors. The numbers of people and initiatives were relatively small and the players heavily networked. Today, that is no longer true, but we intentionally continued to use the word ‘HOT’ as a catch all, in a genuine, but perhaps naive attempt to be as inclusive as possible. That was a mistake. In conversations over the past months, some people have made it clear to us that this can be problematic. When we refer to HOT communities or the ‘wider HOT community’ or Tasking Manager users as ‘HOT community members’, we can make the mistake of associating groups of people and their work with HOT, even where they haven’t themselves chosen that association. We understand now that, for those groups, this can feel like HOT taking credit or assimilating and, while this was never our intention, we will stop doing this. We of course welcome all who share our mission to consider themselves part of the HOT family, while doing so on their own terms.

In fact, in trying to work through this and define what we mean by ‘HOT’ and ‘community’, we came to a realisation that maybe it is not our role to do this defining… groups contributing to OpenStreetMap already define themselves and that is as it should be, just as many contributors define themselves as part of one or many groups. Maybe our role is to work out what HOT should be in relation to them in order to achieve the ambitions articulated through the Audacious vision.

A friend from the OSM Africa network recently told us: “Communities stop talking to HOT because HOT only talks about HOT”. We recognise that while HOT was instrumental in creating and nurturing the space for dialogue and collaboration to happen around humanitarian use of OpenStreetMap, recently we have too often ended up occupying that space. We will now work towards contributing as a valuable and active constituent part of a much larger network and ecosystem.

To achieve our Audacious goals, we know that HOT needs to be a part of a movement that champions local people, local devices and open knowledge and data to solve local problems. The movement needs to be inclusive, representative and value must flow across it in multiple directions. The resources that come from the Audacious prize can be instrumental in supporting this, but only if they enrich the movement as a whole.

In any ecosystem, money and resources equal power. The microgrants programme is a great example of where HOT has been successful in developing a mechanism to redistribute money from donors and funders to local communities trying to solve local problems. We need to work out how to be much more radical, though. One example is putting community support funding decisions in the hands of OSM-related groups in each region. And supporting the already great work led by local OSM groups, in established and emergent local NGOs, in INGOs and across OSM in places such as the Local Chapters and Communities Working Group and the OSMF. We need help working out how to best contribute to these initiatives and aims, how to turn HOT into a community amplifier, into a humanitarian OSM super-spreader, into a vehicle for people who want to save or improve lives, alleviate suffering and restore dignity using open data, tools and knowledge.

What does this mean, practically? Beyond this statement, we have already started to operationalise this intent.

FIRST You may have noticed that this event is no longer called the HOT Summit, but the humanitarian OpenStreetMap Summit - a space and time for all those who care about open data for humanitarian action to come together, share and learn. We are happy to resource and coordinate the event, but it must serve h.O.S.M not just H.O.T. This small step is the start of a process of de-occupation of the humanitarian OpenStreetMap space by HOT - think mailing lists, working groups, communication channels. For this world-changing movement to map our world to get bigger, we at HOT must create space for others to evolve and lead. Supporting the movement, inspiring it, amplifying it, but not controlling, or defining it - and making sure we get out of the way! As one small example of this, we have committed to stop opening new long term country offices and will support our country office staff in transitioning to fully independent local entities in 2021.

SECOND We have committed to resourcing four regional hubs as part of the Audacious project, moving decision-making and resources away from a remote, global team and closer to where we want to support people and communities. How these hubs evolve is something we need help with, particularly from contributors and communities in those regions.

THIRD We also commit to doing much more of our thinking in public. While it hasn’t been through bad intentions, we have gradually stopped documenting our work, thinking, and decisions in the open. This leads to a less rich ecosystem, limits our contribution to a commons of open knowledge and makes it hard for others to have an open dialogue with us. As part of that, we are going to re-prioritize channels for constructive feedback, criticism, suggestion and discussion. We have further work to do on how we welcome and facilitate these conversations, but we have made a start at hotosm.org/feedback.

At the heart of this is the will to work out what it really means to be a community-centric NGO in this ecosystem. It’s not easy: we all truly are trying to do something that’s never been done before: a map of our world by and for the people of our world. 1 billion people, 94 countries - we need to think ambitiously, even audaciously, as local and international humanitarian and development partners are relying on us for data that can lead to life-changing impact. But as our OSM Philippines colleagues suggested, we also need to ask ourselves “Audacious for who?”

How do we transform HOT and make it something that enables people living in areas vulnerable to humanitarian crises or with high levels of poverty to achieve their own audacious goals? Coming back to the future of humanitarian OpenStreetMap. The future is not HOT. It is all of us here today, across hundreds of organizations and groups working to make an impact through data. Imagine the realm of what we could make possible, together, if we get this transformation right. Thank you for reading and I look forward to this conversation continuing.

By the way, if you didn’t manage to make it to the Summit and would like to see the presentations and discussions, the videos will be made available - details at the Summit website shortly.

Objective

My objective is to represent Dominion Land Survey (DLS) land descriptions in OSM to aid with agricultural accounting and navigation in areas of Western Canada where civic addressing is either not fully implemented or not known. To that end, this entry serves as a draft proposal.

Background

Approximately 800,000 square kilometres of Western Canada (Manitoba, Saskatchewan, Alberta and parts of BC) were subdivided according to the DLS. While many regions have implemented civic addressing (e.g. 12345 Road 321 W) for yard sites, DLS land descriptions (also known as legal descriptions) are still prevalent. Agriculture in particular relies on them to identify fields for crop insurance and on-farm food safety programs.

It it not uncommon for a field to span four land descriptions; I have personally worked with fields that spanned six due to their shape and placement. In the other direction, it is not uncommon for one land description to have multiple properties on it.

My initial focus is on Manitoba but I believe the process I’ve outlined below can be applied to the other Western provinces with minimal changes.

Steps to Implement in Manitoba

1. Import municipal boundaries from MLI (admin_level = 6). The datasource in question is named “Municipalities/Local Govt. Districts”. Cities and towns also show up in this dataset and will need to be filtered out.
2. Clean up shapefiles representing quarter sections, river lots and wood lots so each one is its own entity. They are currently a collection of lines with a centroid label.
3. Import land descriptions into OSM, ensuring a relationship marks them as part of their municipality. I suggest admin_level = 10 to put them on par with neighborhoods in urban areas since these, too, can contain more than one property.

Steps to Implement in Alberta

TBD

Steps to Implement in BC

N.B. admin_level = 8 for municipalities

TBD

Steps to Implement in Saskatchewan

TBD

Closing Thoughts

DLS land descriptions are verifiable administrative boundaries and, for better or for worse, are still used. I believe adding them to OSM would be a great help in rural areas but I lack the skillset to take this project beyond theory. Any and all input, no matter how minor, would be appreciated.

Yet another big issue with a user mapping with Maps.Me In Bamako (Mali) this user https://www.openstreetmap.org/user/seydoukone mapped 3000 POIs, all with the office=government tag. You can left comment to his/her changeset, but Maps.Me doesn’t implement any messaging system. So, what can we do? Erase all the POI is not a good idea, because the user add pharmacies, fuel, etc. The only way is make pressure on the Maps.Me developers I think

test

Retzer Nature Center is preserving and maintaining over 450 acres of prairie, forest, wildlife habitat, nature trails, and environmental learning facilities in Waukesha County. Includes; Planetarium; Nature displays.

Waukesha County Park System is located in Waukesha County, Wisconsin. It is composed of eight different parks throughout the county: Fox Brook Park, Fox River Park, Menomonee Park, Minooka Park, Mukwonago Park, Muskego Park, Naga-Waukee Park, and Nashotah Park. “From swimming to camping to hiking and cross-country skiing, each park has its own personality.” The park system also has five lake accesses: Ashippun, Nagawicka, Nemahbin, Pewaukee, and School Section, three golf courses: Wanaka, Naga-Waukee War Memorial, and Moors Down, two ice arenas: Naga-Waukee and Eble, Retzer Nature Center, and the Expo Center. Dogs are permitted at all parks with the exception of Retzer Nature Center. Minooka Park, Mukwonago Park, and Nashotah Park offer the community fenced-in dog parks.

I used 10 foot long 0.5 inch diameter electrical conduit for mapping outside. I connected pieces with some screw fastener thing.

1 pole works and is short.

2 poles kind of bend.

3 poles result in a tube bending and the far tip never leaving the ground.

現在開催中のMapping Adventure Japan 2020についてお伝えします。
Mapping Adventure Japan 2020は PoliMappers Adventures(2018/2019)や OSM streak、OSM USの 30 Days of Mapping などを参考に、12月1日からクリスマスまでの25日間、楽しみながらマッピングを続けるために開催しているマッピング企画です。

1日ごとにお題が出され、お題に沿ってマッピングを行い、変更セットのコメントに #MappingAdventureJapan をつけて投稿することで参加することができます。
日々のマッピングを続けられるように、お題はそれほどハードなものは用意しなかったつもりです。

日本では年末進行でマッピングから離れてしまいがちかもしれませんが、この機会を利用して是非楽しみながらマッピングを続けてみてください。
お題は OSM Wiki の他、 Twitter のハッシュタグ #osmjp で、なるべく前日に投稿しているのでチェックしてみてください。

また、企画は25日までですが、企画が終わってからも OSM streakなどを活用してマッピングを続けてみてください。 現在の参加状況は result maps や uMapで確認できます。

Weil im Talk zum sac_scale Artikel im OSM-Wiki der Verdacht geäußert wurde, höhere Grade würden einem, nicht weiter benannten Missbrauch Tür und Tor öffnen…

Im Hochgebirge in Österreich kann man auf Wegweisern im Hochgebirge dem Symbol “! Alpine Route” begegnen. Der Alpenverein weist damit darauf hin, dass man sich, anders als auf Talwegen und Bergwegen, keine durchgehende Markierung zum angeführten Ziel erwarten darf, ja nicht einmal einen schön ausgetrampelten Steig, sondern “exponierte, ausrutsch- und absturzgefährdete Stellen sowie ungesicherte Geh- und Kletterpassagen” und dementsprechend “gute Kondition, ausgezeichnetes Orientierungsvermögen, sichere Geländebeurteilung” usw. vonnöten sind.

Geht es nur mir so, oder liest sich das wie die Beschreibungen aus der Schweizer Wanderskala in ihren höheren Schwierigkeitsgraden? Ein paar mit diesen getaggte Wege finden sich sicher auch in Openstreetmap. Mal schauen, was es mit denen auf sich hat.

Die overpass turbo Abfrage “sac_scale=difficult_alpine_hiking in Tirol” (da kenn ich mich selbst am besten aus) liefert aktuell 157 Wege - Meistens die letzten (50 bis ein paar hundert) Meter zum Gipfel beziehungsweise Gratwanderungen zwischen zwei oder mehr Gipfeln, seltener den komplette Gipfelanstieg vom Mittelgebirge aus. Einige Treffer markieren Zugänge zu Klettergärten; Einer ein Stück eines Wegs im Mittelgebirge, an der Stelle eines Hangrutsches; Einer das Wegstück vor dem Gastgarten der Hütte - eventuell verwechseln Amerikaner 6 mit 1, frei nach Schulnotensystem? Nichts wirklich aufregendes.

Für “demanding_alpine_hiking” liefert die Abfrage 341 Wege, bei “alpine_hiking” 899 Wege; Beides ziemlich gleich wie “difficult…” verwendet - zu allermeist im Hochgebirge, in den weißen/hellen Bereichen der mapnik Karte. Der zahlenmäßige Anstieg wirkt nicht unerwartet. Mir unverständlich kommt es bei T5 schon zu Kombinationen mit mtb Tags.

Potential für Kollateralschäden: Wer es zum Anfang schafft, bzw. bis dorthin wo es brenzlig wird, der sollte erfahren genug sein, entscheiden zu können, ob den Weiterweg wagen; von daher gering. Die Chance, dass nichtsahnende, blind dem Navi vertrauende Personen, die z.B, nur den Weg zum nächsten Milchautomaten gesucht haben, dann durch die Hölle geschickt werden halte ich ebenfalls für vernachlässigbar.

Es sieht also sehr danach aus, dass die Tags ganz im Sinn der Erfinder angebracht werden. Nicht wenige dieser Routen/Steige/Wege in der OSM sind sogar ausgeschildert bzw. die Gipfel in den Beschreibungen der Hütten in der Umgebung, so es welche gibt, als Tourenziel erwähnt und gut getrampelt. Auf anderen dieser Routen wiederum kann so viel Zeit allein für Orientierung draufgehen, dass kein schnelles Vorankommen mehr ist! Eine weitere Hilfe im Gelände zu unscheinbaren Steigspuren und, wie es sich gehört wenigen und dezenten Markierungen kann da jedenfalls nur nützen. Zu diesem Zweck wäre übrigens der nackte “highway=path” ausreichend, das Attribut “sac_scale” unterstützt mehr die Planung, aber das steht ja eh schon im Wiki-Artikel, wenn auch nicht so deutlich.

The International Day of Persons with Disabilities is observed every December 3rd, and OpenStreetMap marks this day by saying “Our aim is to be the best world map for accessibility”. OpenStreetMap has long been a resource to map and share open data on features related to disabilities.

We asked community members gathered on the accessibility mailing list about why and how OpenStreetMap is so useful.

Jean-Marie Favreau of the Université Clermont Auvergne explained…

The strength of OpenStreetMap is that it allows anyone to contribute accessibility data, whether they are local authorities, user associations, or individual contributors. Being a global project, it facilitates the sharing of observations and learnings of how the equipment, habits and practices of accessibility vary in different coutnries. Finally, the data is in a commons and managed by a community, so it more accurately reflects the reality of the territories it maps.

Nick Bolton of the University of Washington adds…

When people with disabilities seek out map information, they find that accessibility information is missing or doesn’t account for their personal preferences; neither companies nor government agencies are consistently creating connected pedestrian map data flexible enough to meet the diversity of pedestrian concerns expressed by people with disabilities. OpenStreetMap is well-suited to fill this informational gap as it has a flexible and democratically extensible data model, can be mapped out by locals without waiting for an agency or company to dedicate resources or take on liabilities, and all data is immediately published and examined by the public.

We are so glad OpenStreetMap fulfills this need. Read on to learn about applications for persons with disabilities, and ways to contribute to the map.

Apps for accessibility

There are many applications and research projects for persons with disabilities that use OpenStreetMap for collecting and sharing accessibility data, and for communicating that data in appropriate ways.

One of the most well known applications for tracking and sharing accessibility data is Wheelmap. Wheelmap helps find and tag the wheelchair accessibility of points of interest. There’s both an android app and iphone app. They are currently running an important campaign to map the accessibility of Covid-19 testing sites. Svenja Heinecke shared more about Wheelmap at the 2018 State of the Map.

Data on sidewalks is critical to accessible navigation.  OpenSidewalks focuses on developing tagging schemes and tools for collecting accessibility data of sidewalks, and its sister project AccessMap creates individualized accessible routing plans for people with mobility impairments. Both are projects of the Taskar Center at the University of Washington. This approach has been picked up by the Italian OpenStreetMap community in Padova and Milan, with people with disabilities, high school students, and other new mappers contributing.

And then there is navigating indoors. AccessbileMaps is a project of the Technische Universität Dresden in cooperation with the Karlsruher Institut für Technologie and focuses on indoor accessibility. They develop tools for mapping buildings with the Simple Indoor Tagging scheme, especially accessibility information, and produce applications using indoor data from OSM for blind, visually impaired and mobility impaired people to plan trips.

Then this data needs to be used in appropriate ways, and the creativity and innovation is inspiring.

Tactile maps help people who are blind or partially sighted navigate their surroundings. Touch Mapper uses 3D printing to create tactile maps from OSM data.

Soundscape from Microsoft Research helps users with visual disabilities to create better mental maps of their surroundings for navigation. Using audio to describe places, they can naturally and intuitively explore more and feel more comfortable and connected in new environments. The app is built on OpenStreetMap data.

Compas research project at the University Clermont Auvergne develop ACTIVmap in partnership with other academic and private sector researchers to build multimodal maps leveraging tactile, sound and haptic feedback to represent and interact with geographic information.

How can you help?

You can of course also add disability-related tags with regular OpenStreetMap editors like JOSM and iD, and mobile apps like Vespucci, StreetComplete, OsmAND, and Go Map!!

The OpenStreetMap wiki has a comprehensive guide to tags useful for the needs of people with disabilities. Here are just a few of the kinds of features that can be tagged in OpenStreetMap, many of these can be added quickly and easily with StreetComplete:

• Tactile paving (tactile_paving=yes/no) and tactile information maps (information=tactile_map)
• Designated parking spaces (amenity=parking_space + access=no + disabled=yes/designated)
• Traffic signals with sound (traffic_signals:sound=yes/no)
• Accessibility information for steps, such as the presence of handrails (handrail:left/right/center=yes/no), the number of steps (step_count=*) as well as whether there is a ramp (ramp=yes/no) and which kind
• Wheelchair accessibility at shops and other amenities (wheelchair=yes/limited/no) as well as bathrooms (toilets:wheelchair=yes/no)

There are many other ways to help, documented on the wiki as well. For example, promote OpenStreetMap with friends who have a disability, and ask them how else OSM can help. You could organize a mapping party focused on mapping these kinds of features. Translate our wiki pages on disabilities to other languages. Or build new routing and rendering applications for people with disabilities.

OSM’s freeform tagging system is always evolving, if there’s something you think should be mapped in OSM, but isn’t, you can help guide that process to wider adoption.

Join us

Let us know how you’re contributing. And to connect with our community, join the list at https://lists.openstreetmap.org/listinfo/accessibility by sending an email to accessibility-subscribe@openstreetmap.org.

The OSMF Board is asking the membership to approve an amendment to the Articles of Association that will allow Board committees (specified in the AoA as only consisting of Board members) to include any Foundation member, associate or full, to serve on a Board committee. The reason for this is that some of the Board’s administrative work, such as handling our finances, has proven very time consuming, more than one person can handle. Another sphere is the budget preparation, and yet another is fundraising. Since the Board is also hiring fulltime staff and engaging contractors, it needs help with oversight.

Some board members have been asked if this is intended to supplant the Working Groups. At least one diary entry has been posted by a community member asserting that this is the case, and urging Foundation members to vote against the amendment.

The proposed AoA amendment is NOT intended to supplant Working Groups. The Working Groups handle the substantive and administrative issues of the community, which is separate from the Foundation and the Board. The Working Groups would therefore not be affected. As I envision it, the Board committees would deal with personnel, budget, and fundraising, none of which fall in the remit of any Working Group.

I urge Foundation members to vote in favor of the AoA amendment, and then to volunteer to serve on one of the Board committees (and on Working Groups, too, but separately!)

Back in September we launched the new osm2pgsql.org website. At that time it was still quite rudimentary. Over the last months a big part of my work for the OSM Foundation was to work on that site.

Osm2pgsql has been around for a long time but never had a real project web site. Most information about the project was in its git repository, some on the OSM wiki, and more information strewn here or there in blog posts etc. So my first job was to see what’s out there and what’s missing and create a structure that I could fill with content. Over time the website grew to contain all the sections that software projects tend to have, like documentation, installation instructions, news, support information, etc. Where possible I tried to use existing documentation, but it all had to be checked first, a lot of it was outdated or too complicated or slightly wrong. I filled it into the structure, re-wrote, re-organized, added more content, more documentation, examples. And I also removed much of the old content on the wiki pages or in the repository.

We also needed a bit of color, a few icons, a layout that works on big screens and small phones and in a screen reader. Over time the content and its presentation grew together. I am pretty happy with what we have now. Not perfect, not complete, not done, and it never will be. But I believe we have something now that will help new and old users alike to use osm2pgsql in their projects. And now that everything is in one place, it is much easier for the developers to fix something small here or there or add the documentation for new features that they are building. From now on the website can just be updated as part of the other work we are doing on osm2pgsql.

Two sections of the website I want to talk about in particular: The manual and the examples. Having a manual is, of course, necessary for any software. One document that, as a whole, should describe everything there is to know about osm2pgsql. There are some chapters that are still rather short, but there is lot written down now that was never before explained anywhere. But a manual only shows you the “how”, it’s great once you have decided that you want to use osm2pgql and want to figure out how to solve your problem with it. But often the question is: Can this tool even solve my problem? And that’s where the examples come in. They are not tutorials, but they show a wide range of problems and that and how osm2pgsql can solve them. I hope this gives current and potential users of osm2pgsql more of an idea what’s possible and where to start.

Making osm2pgsql more user friendly is not only about the website and documentation. Another part of that, also paid for by the OSMF, was going through the code and improving the logging output, error messages and such. All messages that the program produces have a time stamp now, the verbosity is configurable from “show only errors” to “show every SQL command and all the data sent to the database” for debugging. What’s shown is more concise and more consistent then before. And if you want to send the output to a log file, you can switch off the progress reports. All of these were long-standing open issues that I could close now.

I believe the result is much better than what we had before, but there were a lot of changes, so I am sure there are some place where I screwed up and some important message isn’t shown any more or so. But we’ll fix the problems as they come up.

Next up: We have some loose ends to tie up, but will publish a release soon. This contains not only all the changes I wrote about above but also many fixes and new features. But that’s for another blog post.

http://weeklyosm.eu/ru/archives/14005

I pointed out some of my concerns with the change to the OSMF articles of association and changes to who is to become eligible to a member on the the OSMF mailing list a couple of weeks back, see https://lists.openstreetmap.org/pipermail/osmf-talk/2020-October/007231.html

Those comments were just on the general concepts that were being proposed not the actual text, which we have now received as part of the formal general meeting announcement.

Unluckily my concerns not only persist, they have increased with respect to the proposed change to the OSMFs articles that will allow the board to create committees that include non-board members.

Currently a large part of OSMFs business is carried out by working groups, in particular the OWG running the infrastructure, the CWG communicating on behalf of the OSMF and the LWG handling licence and other intellectual property matters.

The working groups go back to a OSMF board meeting in November 2008, https://docs.google.com/document/d/1OcoOqas1NnOLyhiyFZk12K_BpjhWeXvVU7Nl4MDSGeU/edit?usp=sharing and it is clear that these were established to have topic specific groups in which the board could work on OSMF business with additional participants without having to have the full board present. With other words, working groups have always been board committees with additional members, that this practice wasn’t quite inline with the foundations articles was and has been just a bit of fuzziness among a lot of other issues that the OSMF has had.

Bringing the articles more in line with actual practice is naturally a good thing however it hasn’t been framed that way by the OSMF board, instead the reasoning is that the board needs to have groups that can actually work on behalf of the OSMF, and by extension commit the foundation, for example on human resources related matters. This naturally pulls the proverbial rug out from under the working groups, calling in to doubt every single action and statement they have made over the last dozen years.

Now back in October when I discussed this with Allan, I let the matter lie because there was an obvious quick fix the OSMF could have applied once it had realised what it had done. It could have been made clear that the working groups are such board committees and the AoA change was just an adaption to previous practice. Unluckily since then the actual text of the change includes that a board member needs to be the chair of such a committee, which would upend all the current working group chairs and is incompatible with how that working groups have operated since roughly 2012.

The rule that the chairperson cannot be a board members was created out of the experience of misuse of the WGs and, while it existed, the management board. Essentially by creating a working group and being its representative on the management board, a board member could multiply their weight in decision making by having multiple votes on a matter, when a run of the mill board member would only have one.

My recommendation would be to reject the change as is, and have the board, as this seems to be a high priority item for it, arrange for a vote early 2021 on a correctly framed change with the requirement for a board member to be chair removed.

On to the 2nd controversial item. The board is asking for a mandate to investigate restrictions on who is eligible for OSMF membership. Obviously there is no harm in investigating this, however again I believe this is framed in the wrong fashion. Membership eligibility should follow from the organisations goals, and as a concretization of that its mission statement.

The OSMFs mission statement https://wiki.osmfoundation.org/wiki/Mission_Statement clearly states
The OSMF membership is open to all who want to support the project and participate in the OSMF’s democratic process.

At the time it was a conscious decision to not limit membership only to active participants, but far more leave this as open as possible. Even though this would likely lead to the OSMF being a “Friends of the opera” organisation and not the “Union of the opera singers”*.

The membership can and probably should breach this subject again, but it shouldn’t be framed as a mere administrative detail inline with providing free membership to active contributors and other similar measures, it is a discussion about the fundamentals of the organisation and should be treated as such.

* had to sneak one of my dreaded analogies in there :-)

굉장히 유용한 사이트를 찾았습니다. 모두 오픈스트리트맵의 데이터를 사용합니다.

https://osmbuildings.org/ 건물을 3D로 보여주는 지도 https://openstreetbrowser.org/ 지물들을 카테고리별로 보여주는 지도 https://www.cyclosm.org/ 자전거 지도. https://anvaka.github.io/city-roads/ 도시의 모든 도로를 티셔츠,머그컵 등등에 담을수 있는 사이트 https://osmlab.github.io/show-me-the-way/ 지도가 바뀌는 모습을 실시간으로 볼수있는 사이트 https://print.get-map.org/ 인쇄 가능한 지도를 손쉽게 만들수 있는 사이트 지도 옆에 도로명을 나열할수 있다. https://hanshack.com/figuregrounder/ 피겨 그라운드 지도(건물이 있는 부분과 없는 부분을 표현하는 지도)를 생성하는 사이트. https://pic4review.pavie.info/#/ 도시 사진만 보고도 기여할수 있는 사이트.

I live in Fort Worth, TX, and have recently geolocated 367 emergency location signs that appear in parks and trails in Tarrant County, of which Fort Worth is the county seat. I would like to contribute them to OSM, but so far have not figured out the best/correct way to tag them. Any ideas or help out there? Thanks in advance!

Over the last couple of years the Microsoft Open Data Team in Serbia has been very busy. They've contributed over 1,000,000 images on 8,000 km of roads. They've also validated 300,000 traffic signs and made more than 4,000 traffic sign related edits in OSM.

I’ve made OpenStreetMap a major part of my life and work since 2005. It’s not just an audacious, community-built, complete, freely-licensed, street-scale map of the world. OSM is also a big tent that collects the skills and support of a huge range of individual and organizational contributors.

In 2021, OSM’s community has two opportunities to grow stronger together: we should make the OSM organization support a wider diversity of participants and we must succeed at starting to manage our technical operations professionally.

I’m a good candidate to help with both of these existing 2020 OSMF board goals. As a product and engineering leader in several organizations, I can help the Foundation succeed at finding and keeping great engineering talent. With my history on the community and business sides of OSM, I am experienced in making open data attractive to new community members and soliciting support from large organizations.

I’d like to make myself available for conversations with anyone who has questions about my candidacy, manifesto, priorities, or really anything else. I’m blocking these four times over the next two weeks prior to the close of voting and AGM on Dec 12; get in touch here or via my personal email if you’d like to chat by text, voice, or video!

• Dec 1, 16:00 PST
• Dec 3, 8:00 PST
• Dec 4, 16:00 PST
• Dec 9, 8:00 PST

Read my complete manifesto on the Wiki for more about why I think I’d make a good OSMF board member.

C’est sur le terrain que l’on puise nos ressources pour mapper le terrain … Mais quand les panneaux présents sur place sont faux on fait comment ? Heureusement qu’on en a parlé avec un élu du secteur qui m’a signalé que ce panneau avait toujours eu la mauvaise orthographe. #priziac #bretagne

Voilà longtemps que je n’ai pas publié dans ce journal, pourtant les activités se poursuivent en garrigues ! Le projet que nous menons actuellement avec le Collectif des Garrigues est la cartographie du patrimoine en pierres sèches de notre territoire.

A cause du confinement imposé pour lutter contre l’épidémie de coronavirus, il est difficile de nous retrouver sur le terrain. J’ai donc proposé aux membres du réseau de contribuer via l’outil MapContrib afin de leur faciliter la tâche : https://www.mapcontrib.xyz/t/7d0f27-Petit_patrimoine_des_garrigues

5 thématiques peuvent être ajoutées à la carte : * Les capitelles : abris en pierres sèches * Les garennes : terrier artificiel en pierres sèches * Les cabanes de charbonniers * Les charbonnières (ne sont pas en pierres sèches, mais associées à cette exploitation de la garrigue) * Les tours de bergers

Une présentation détaillée du projet est faites ici : https://cartographie-collaborative.eu/?CartopartiePierreseche

17/11/2020-23/11/2020

Mapping

• User mahdi1234 published a quick note on how to show the latest OSM data on-the-fly on umap using a query to link directly to Overpass.
• In a thread on the talk mailing list about ‘bad’ edits, Andy Townsend outlined some guidelines for good changeset discussions which are well worth a read.
• Voting for the ‘pumping proposal’ is open until 3 December. Although the initial impetus was for better mapping of pumps associated with water wells, the proposal considers other uses as well, as InfosReseaux describes in a diary entry.
• Jochen Topf describes how coastlines are processed in OSM. He explains the reasons why updating of land/water polygons (based on natural=coastline) can be seen as too slow and unreliable.
• Marcos Merino wrote > about the role of big Silicon Valley companies in contributing to OSM and the fact, probably surprising, that OSM is older than Google Maps.
• Robert Whittaker (user rjw62) has added extra features to his Survey Me tool hosted on the OSM part of his site. Survey Me highlights potential mapping issues in the UK largely based on comparisons with a suite of external open data sources. New sources include Geolytix open data on food retailers.

Community

• The National University of Singapore (NUS) recently invited Jinal Foflia, an OSM community member, to lecture on OpenStreetMap and the OpenStreetMap community.
• Florian Lainez wrote about the importance of building resilience in local OSM communities. Through examples from Myanmar, Mali and Morocco and his own experience as CEO of JungleBus (developing OSM-based public transport solutions), he showed that mapping priorities will vary according to country or region specific needs, which can only be successfully mediated locally.

Imports

• Minh Nguyen explained, on the Imports-US mailing list, that Code for San José volunteers want to import 14,000 shops via MapRoulette.

OpenStreetMap Foundation

• Allan Mustard, chair of OSMF, welcomed new, and old, local chapters at the Local Chapters Congress on 21 November.
• Michael Collinson, acting as facilitator for the presentation process of the new OSMF candidates, published the official set of questions, asking the candidates to answer by 25 November.The answers and manifestos are here.
  Suggested community discussion period: 28 November to 5 December (when voting opens).

Local chapter news

• Joost Schouppe (Secretary OSMF) asks the Slovakian OSM community about Freemap Slovakia’s application to become an official Local Chapter of the OSMF. Please forward your questions, comments or concerns before 7 December.
• Joost Schouppe (Secretary OSMF) asks the OSM community of Uganda and the OSMF Membership about OpenStreetMap Uganda’s application to become an official Local Chapter of the OSMF. Please forward your questions, comments or concerns by 7 December.
• Mapper of the Month: Diseret (Belgium) – OpenStreetMap Belgium.

Humanitarian OSM

• The Collective for the Protection of Sugamuxi Province requested support from OpenStreetMap Colombia and its Tasking Manager to update the map of the Lake Tota Basin. High levels of lead contamination alarmed the population and the authorities, who still do not know the origin of this heavy metal in the ecosystem. The map update > aims to help identify and solve the health and environmental problems of the second largest lake in the Andes.
• Pete Masters (pedrito1414) summarised a remote workshop held by HOT to consider how the community relates to the goals of the Audacious project.

Maps

• In his #30DayMapChallenge Sebastian Meier shows us a new map of Berlin based on open data every day. Day 20 and other days also use data from OSM. The code is available on GitHub.
• The Federal Agency for Cartography and Geodesy showed a map of water bodies in Germany on Twitter. Florian Lohoff responded with a much more detailed map of the river basins of Central Europe by Martin Kompf, based > on OSM data. Martin Kompf describes on his page in detail how he created the map and the source code is also available
• [1] eBin, a member of the Polish OSM community, has produced a vector overlay map of the European electricity grid based on OSM data.
• Hernan J. López reports that after a year and a little more work, the categorised protected areas > of Argentina are now visible on OpenStreetMap.

Software

• HeiGIT has extended their OSM history explorer with new features.
• Richard Fairhurst announced the availability of development versions of Potlatch 3 for testing. Potlatch 3 is a desktop editor using Adobe Air, and has some new features compared with Potlatch 2, perhaps most importantly remote control support. Currently Apple MacOS and Windows are supported: some testing of use on Linux is reported in the comments.

Programming

• The OSM Ops Team are looking for beta testers for a new torrent distribution of the latest OSM planet PBF file.

Releases

• Walter Nordmann (wambacher) has his newly established OSM SoftwareWatchlist under control again. It provides a continuously updated list of the latest releases of all software products in the OSM cosmos. If the cosmos is not currently wide enough to include your favourite piece of OSM-related software then let wambacher know on the forum.

Did you know …

• … that CheckTheMonuments provides suggestions and detailed information on quality assurance of historical objects as well as a map? > .
• … the wide range of bridges which can be encountered on a single trail? A few years ago Kevin Kenny documented some of the more unusual examples on the Northville Placid Trail.
• … streetmangler > and shrtnms? They are tools to abbreviate street names in Russian, Ukrainian and English.
• … about Web to OSM Opening Hours? It’s a tool which parses opening hours from free text or a URL where the opening hours can be found. The tool will work if the website uses the OpeningHours specification of Schema.org and will convert it to OSM format and put it on the clipboard.

OSM in the media

• Joe Morrison has blogged about how large companies are actively contributing to OSM. There are some interesting comments on the article on Hackernews.

Other “geo” things

• Nick Giles reports, in The Guardian, that use of the OS Maps Get Outside adventure planning app has increased by 78% since Feburary, with around 3.5 million people using it now.
• Misinformation about the 2020 US Presidential Election result was trending on social media and elsewhere in mid-November. But you might have missed this Fox News map ceding part of Michigan to Canada. We will gladly not seek OpenStreetMap attribution for this fantasy map, and nor will we add provocative border polygons to the map!Such misunderstandings of geography are so common that academic geographer Peter Gould studied them 50 years ago, coining the term ‘isoignorans’ for contours of equal geographical ignorance in his book Mental Maps.
• In an article in CNRS News (French National Centre for Scientific Research), Erwan Bocher explains the ins and outs of the new SymCore standard of the OGC (Open Geospatial Consortium), which he developed with Olivier Ertz.
• ALPIN explains > the basics of using GPS devices and explains how one can install OSM maps on them.
• Procedural GL JS now is open source. It is a library that allows 3D maps to be embedded into web pages.
• It seems Amazon is starting to map pavements (sidewalks) for autonomous delivery – a mapping robot has been spotted in Everett.

Upcoming Events

Where	What	When	Country
London	Missing Maps London Mapathon	2020-12-01
Stuttgart	Stuttgarter Stammtisch (online)	2020-12-02
Bochum	Bochum OSM-Stammtisch (Online) [2]	2020-12-03
Dresden	Dresdner OSM-Stammtisch (online)	2020-12-03
online	HOT Virtual Summit (online)	2020-12-04
Taipei	OSM x Wikidata #23	2020-12-07
Michigan	Michigan Online Meetup	2020-12-07
Heidelberg	Mannheimer Mapathons e.V. – Int’l. Mapathon (online)	2020-12-08
Salt Lake City / Virtual	OpenStreetMap Utah Map Night	2020-12-08
Munich	Münchner Treffen	2020-12-10
online	OSMF Public Board Meeting	2020-12-10
Berlin	150. Berlin-Brandenburg Stammtisch (Online)	2020-12-11
Berlin	OSM-Verkehrswende #18 (Online)	2020-12-15
Cologne Bonn Airport	134. Bonner OSM-Stammtisch (Online)	2020-12-15
Nottingham	Nottingham pub meetup	2020-12-15

Note: If you like to see your event here, please put it into the calendar. Only data which is there, will appear in weeklyOSM. Please check your event in our public calendar preview and correct it, where appropriate.

This weeklyOSM was produced by AnisKoutsi, MatthiasMatthias, Nordpfeil, Polyglot, rogehm, SK53, Sammyhawkrad, TheSwavu, derFred, richter_fn, tordans.

While working with the high-resolution data of the German census 2011, I noticed that there are still surprisingly many residential areas that are neither recorded as landuse=residential nor as building=*. This concerns mainly linear settlements or farms in the northwest of Germany.

There is now a MapRoulette-Challenge to map at least the landuse for these areas:

Unmapped residential areas in Germany

Please jump in and help if you are interested!

As a source for the challenge I compare the 100m×100m grid cells with the landuse and building polygons, which indicate residential areas: landuse=residential, but also landuse=farmyard, landuse=allotments and some more. For the buildings the residential types building=detached, building=house, etc. are used, but also building=yes.

In the process all census raster cells are deleted, which are at least touched or covered by these polygons. Then all clusters of connected grid cells are combined into one polygon. Of these, again only those are used, in which there are at least 12 persons living according to the census and which contain at least 2 raster cells. The priority of the tasks is set according to the number of inhabitants, so that “worse” cases are presented first in MapRoulette.

With this rigorous filtering I hope that really only the legitimate cases will be left. After all, there are still 2760 cases, so enough to do. The 2011 census is already quite old. Where several people lived 10 years ago, hopefully some of them will still live today.

A map of the mainly affected areas in northwest Germany:

More technical details and source code: https://github.com/hfs/unmapped-census