Diary Entries in English

Recent diary entries

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:

  1. Connectivity checks: https://maproulette.org/browse/challenges/21203
  2. Building-Road intersection checks: https://maproulette.org/browse/challenges/21201
  3. Inconsistent Road Classification checks: https://maproulette.org/browse/challenges/21207
  4. Intersecting Buildings checks: https://maproulette.org/browse/challenges/21208
  5. Correcting mixed name case: https://maproulette.org/browse/challenges/21215
  6. Connectivity checks: https://maproulette.org/browse/challenges/19892
  7. Invalid Turn restrictions checks: https://maproulette.org/browse/challenges/19890

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.

See full entry

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.

Solved by design

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.

See full entry

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.

Posted by Homosaur on 9 October 2021 in English.

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.

Location: Boera, Kairuku-Hiri District, Central, Southern Region, Papua New Guinea
Posted by DUGA on 9 October 2021 in English. Last updated on 10 October 2021.

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.

See full entry

Location: Roland Place, Bel Air, Harford County, Maryland, 21014, United States

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

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.

Challenges

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.

See full entry

Hi all,

I hope you are all well and safe.

As many of you know, we have been working on a new model to ensure Tasking Manager (TM) continues to get the love and attention it well deserves. As we unpacked the value of the project, we started to realise just how much we value the inputs and contributions of a large collective of contributors lodging issues, PRs, code, resources etc. I went through every single issue on TM’s Repo and was really blown away by just how much support the project gets both in front of and behind the screens.

Moving forward, we really want to return TM to its former community-lead glory and as such have put together this proposal for what TM’s Tomorrow could look like.

https://docs.google.com/document/d/1tTT4oKUN34FThzbNFZKfj0lhQOMRB4uTF1n2rO1iHrc/edit?usp=sharing

I invite everyone to comment in the doc on things they like or don’t like or questions they have so we can reenergise our love for the TM and it’s sustainability and evolution. There is a long list of Frequently Asked Questions (FAQ’s) at the end of the doc, but I also invite you to add your questions as a comment to the FAQs so we can endeavour to answer them as well.

I really look forward to your feedback.

Kindness,

bo

p.s. we are also now on the hunt for a possible community representative product owner for TM, so if this sounds like something you could be interested in, please get in touch.

Location: Naz, Esserts-Salève, Monnetier-Mornex, Saint-Julien-en-Genevois, Upper Savoy, Auvergne-Rhône-Alpes, Metropolitan France, 74560, France
Posted by SebastianHelm on 6 October 2021 in English.

Now it is one week since I started working with OSM. Sadly, my initial enthusiasm has waned. While there were many nice experiences, above all encountering some helpful fellow mappers, a feeling of meaningful connection with the purpose of the project did not develop.

The apps I used show little consideration for what’s meaningful to the average mapper or end user. The below example from iD may serve as an illustration for how haphazardly it has been decided what gets displayed and what gets hidden. This matters because the UI displays no settings button to override that decision. iD visibility example

See full entry

Hi everyone,

A new version of MapComplete has been deployed. It has a lot of exciting new themes and features, which I’d like to highlight in this diary entry.

New themes

The Flemish touristical agency (Toerisme Vlaanderen) has asked me to create a tool to help them to map charging stations, restaurants, café’s, …

This has resulted in quite some fun new themes:

At last, the theme I’ve quickly made as demo with hackerspaces and makerspaces is online as well.

Other improvements

At the same time, I’ve been doing lots of work on improving performance. A lot has changed under the hood, resulting in a way more robust and fast experience. On high zoom levels, the OSM-API is used directly, bypassing overpass all together. If overpass-api.de is down, failover to other instances is now builtin. At last, caching is a bit more aggressive and if the data on your machine is recent, no new data is loaded at all.

Earlier releases had some important features to, which I’d like to highlight as they can be important for theme builders:

  • A layer can configure filters
  • A layer can demand to have ‘precise input’, showing an extra draggable map (with e.g. aerial photography) when a new point is added to the map.
  • A new point can be snapped to an already existing road, e.g. when adding a bollard
  • A layer can define that a point can be (soft) deleted
  • The new Mapillary-API has been integrated
  • Some themes have a download-button enabled to download as GeoJson or as CSV

I need your help!

See full entry

Posted by LySioS on 5 October 2021 in English. Last updated on 6 October 2021.

Disclaimer #1 I’m not used to speak english anymore, I apologize if some sentences sound clunky.

Disclaimer #2 Last time I added pictures in the diary post, they would not always show up. Click on the link if it happens.

Introduction

So now, I’d like to start with a provocative joke :

Marck Zuck. comes into his office and asks his colleagues :

– Hey, do you know why there’s a magnifying glass on the OpenStreetMap logo ?

– Well, it means that OpenStreetMap helps you find places and amenities on the map.

– Not a all ! It’s because you won’t notice the credits without one.

Text Vs Logo

My point is that OpenStreetMap lacks a strong visual identity. I believe I started to notice it when I read some Facebook employee saying that a logo would be easier to credit on a map than the (c) openstreetmap contributors. 🤨

Dishonesty aside, he makes a point. The (not so) new OSM logo is gorgeous and deserve more consideration and would help OSM maps being more recognizable and popular. In times where we are constantly facing pictures, logos, visuals, a brand/company/project/whatever need a clear visual identity to exist in our digital world. The actual text only credit looks like good oldies websites.

Besides, sometimes, OSM credit is in competition with some other logo. I was thinking of Mapbox but I couldn’t find an example with an OpenStreetMap map.

See full entry

You may have heard people talk about ‘priority countries’ in relation to HOT’s work and the regional Open Mapping Hubs (the Asia Pacific hub for example).

HOT has committed to furthering its longer-term vision across 94 countries through 2025. Initial priority countries were selected based primarily on disaster risk and acute deprivations needs (measured through the multidimensional poverty index).

I just wanted to flag that if you ever need to know which countries they are or the process for updating the list, there is now a page on the OSM wiki at https://wiki.openstreetmap.org/wiki/Humanitarian_OSM_Team/Priority_countries.

Please let me know if there is any information missing that you think should be there…

Posted by drolbr on 4 October 2021 in English.

While the heart of OpenStreetMap is the community of mappers, it has also a remarkable ecosystem of software developed and used for OpenStreetMap. Many people are surprised to learn that it is so federated that the OpenStreetMap Foundation does only a tiny part of it.

The key to understand that is that many software projects have developers out of personal passion. The long time editing tool Potlatch has been developed and kept alive by Richard Fairhurst, JOSM luckily has a whole team behind it, and also Vespucci, OSMAnd, Nominatim and Osmium each are closely tied to names, as well as many other tools. This both keeps each of the tools focused and gives them a direction. Large organizations cannot offer that, because more often than not the managerial fashion of the season will interfere with pursuing long term goals.

Nonetheless, outsiders that expect a single point of contact shall have one. This is where the idea of the Engineering Working Group comes into play: it has a more specific mission than the board in general, but it still can send people and inquiries to the right places.

The EWG does not replace issue trackers. The EWG is not the right venue for comprehensive visions of the future. But it shall help to improve the flow of information related to development of OpenStreetMap related software.

I’m happy to chair the just restarted EWG.

See full entry

Location: Gemarkung Elberfeld, Elberfeld-West, Wuppertal, North Rhine-Westphalia, Germany
Posted by bryceco on 3 October 2021 in English.

Go Map!! v3.0 was released today for iOS, and while superficially not much looks different, there are some big changes under the hood: All 38,000 lines of code are now written in Swift after a laborious conversion from it’s original Objective-C implementation. This make the code faster, easier to understand, easier to debug, and brings it in line with Apple’s direction for modern apps. It also greatly simplified a lot of refactoring to improve general readability of the code base. If you’re a developer this is a great time to get involved with the code.

Background

My involvement with OSM started in March 2012 and I wanted to be out surveying and mapping on my iPhone. I had downloaded the few iOS apps that existed at the time (remember iLOE and Pushpin?) and found them too limited. Although I had a strong Windows/C++ programming background I was new to iOS, Objective-C, OSM, and GIS. Nevertheless I began work on the first version of Go Map!! writing in Objective-C and learning about the OSM API along the way. (Apple did not introduce the Swift programming language until several years later, and it took an additional several years to become stable.)

I wasn’t really sure whether a new mobile editor was something of interest to the OSM community, but in October 2012 I drove down to Portland, OR for my first SOTM US, where RichardF (author of Potlatch, the OSM web editor at the time) delivered a talk titled (IIRC) “Let a thousand editors bloom” where he suggested that OSM should have a wide variety of editing tools, and the more the better. I’d been working on the app for only a couple months and his talk inspired me to continue.

See full entry

Was doing some mapping, and noticed the shoreline in OSM didn’t line up with the latest aerial photos… By like 50 meters.

Doing some spot checking around the great lakes, the other lakes seemed fine, except in a spot in Lake Huron, the water was about 25 meters more in shore.

I guess according to NOAA’s data, in 2020 Huron-Michigan had really high levels, and 2021 is going down (2 feet) almost halfway to the mean. So… maybe in 6 years, the water level will be back down, so no changes need to be made to the map.

Location: Macatawa Park, Macatawa, Park Township, Ottawa County, Michigan, 49434, United States

(FR: L’anglais a été utilisé pour atteindre une plus grande auditoire parmi les contributeurs OSM)

This journal entry serve as my comments for the changes I made on the Réservoir Beaudet. (Changeset: 112010724)

There are currently major ongoing constuctions at the area marked as landuse: consctuction- that is principally the verification I needed on my changeset; If somebody more experienced can double check I dont break things, that would be great.

The end result is half of the area will be converted to a park and the rest will be converted into a water area. Source: Embedded Youtube video on the project announcement web page: https://www.victoriaville.ca/nouvelle/202104/4090/lancement-des-travaux-de-restauration-du-reservoir-beaudet.aspx (all in french)

Changes made are up to date as of October 2021 with a local survey as a source, with surrounding cycleways being completely closed to the circulation. I added the temporary cycleway which is part of the “railway:abandoned” way east of Route de la Grande Ligne.

Thanks OSM!

Location: Victoriaville, Arthabaska, Centre-du-Québec, Quebec, Canada