Introduction

Hi everyone! As GSoC 2021 is coming to a close, I am writing this diary entry as a final report on the progress of my GSoC project, the OpeningHoursEvaluator, in the second period of GSoC.

Previous entries

• Community bonding period
• First period

Project Summary

An evaluator for opening hours tag according to OSM opening hours specification.

Second Period’s Summary

Just to recap, the evaluator from the first period supports almost all the syntaxes defined by the specifications, ranging from something as small as time and a wider range such as year. Building from my previous progress, I have added geocoding to the evaluator, for use in calculation of variable time such as dawn, dusk, sunrise, sunset. I have also added support for holiday data for the corresponding opening hours tag PH and SH, which currently supports 168 countries. Combined with my progress in the first period, the current evaluator now supports evaluation of all the syntax defined by the grammar, and is ready for use in production.

Source code

GitHub repository: https://github.com/goodudetheboy/OpeningHoursEvaluator

Timeline

… See full entry

District Court, Aurangabad, Government Polytechnic Aurangabad, Collector Office Aurangabad, Zila Parishad Aurangabad, Regional Commissioner office, Municipal Corporation, MSEDCL, BSNL Customer Care Centre, BSNL Mobile, HP Gas, Government College of Engineering, CIDCO, HUDCO, MIDC, ASCDCL, Siddharth Garden and Zoo, DTE, ITI, Central Bus Stand, CIDCO Bus stand, City Smart Bus, Railway Station, Airport, Police Commissioner office, High Court, Cannaught place, IT park, Stadium, Theatre, Market, Canteen, police station, post office, CADA, TV Centre, Akashwani, Old Mondha, New Mondha, Bank, ATM, Government Hospital, petrol pump, Ration Distribution Centre, University, College, School, Maharashtra State Board Of Secondary & Higher Secondary Education Pune Divisional Board, RTO

Important Links

Source Code

Nominatim-Feedback-Reporter

Previous Posts

• Community bonding
• Phase-1 Update

Hosted server

• Nominatim-Feedback-Reporter-UI
• nominatim-Feedback-Reporter-API

About the project

This is a Google Summer of Code project, which has been developed over the Summer of 2021 by Yash Srivastava (darkshredder). This project is mentored by Marc Tobias (mtmail) and Sarah Hoffmann (lonvia).

Project Description

OpenStreetMap’s main search engine Nominatim did not provide a way to report feedback on the search results that they think to be wrong.

This project aims to provide a web interface to report such feedback and store them in a logs file. So that the feedback can be analyzed, fixed and can be re-run by the maintainers to see if the problem is still there.

Implementation

The following step was followed to implement this project:

• Selecting the frontend and backend framework for the project.
  • For frontend we used svelte.
  • For backend we used falcon.
• Finding a way to fetch multiple results for reverse geocoding as nominatim only returns a single result.
  • We used overpass API to fetch multiple results and then to provide an option to select a correct result base on reverse search results.
• Hosting the frontend and backend code on the server.
  • Our frontend UI can be found here.
  • Our backend API can be found here.
• Testing the frontend and backend code.
  • We used puppeteer and mocha to add integration tests to the frontend.
  • We used pytest for unit testing backend code.
• Setting up the continuous integration pipeline.
  • We used GitHub Actions to integrate the CI pipeline to test as well as build our frontend and backend code.

Final product at the end of the GSoC

… See full entry

Nota: Esta traducción al español es posible gracias a Cyberjuan, ¡gracias! Puedes leer la versión en inglés aquí. (Note: This translation to Spanish is made possible by Cyberjuan, thank you! You can read the English version here).

Tuve la suerte de ser seleccionada como uno de los académicos de la conferencia State of the Map 2018 (mis reflexiones aquí). Este año, tuve la oportunidad de ser parte del Grupo de trabajo (WG) del SotM 2021 organizando la conferencia en línea SotM 2021.

Principalmente he trabajado en el Equipo de Comunicaciones. Comparto en este diario mi experiencia como organizadora y mis aprendizajes, ya que esto puede ayudar a otros organizadores a planificar sus eventos en línea, o similares.

¡A continuación una larga lectura!

1. Reclutamiento de voluntarios para SotM WG (vea la invitación a la Convocatoria de voluntarios mediante la lista de correos)

Debido a la pandemia, el SotM se volvió virtual. Dado que no había un ofrecimiento comunitario involucrado, la presidenta de SotM invitó a los miembros de la comunidad de OSM a unirse al SotM WG. Ella promovió esto a través de la lista de correo y fue compartido por miembros de la comunidad a través de las redes sociales y otros canales comunitarios.

Clave: Definir claramente la estructura del grupo de trabajo (sub-grupos/sub-equipos), sus funciones y quién dirige los equipos, y cómo unirse (tan simple como enviar un correo electrónico).

2. Organización de la estructura/flujo de trabajo del equipo (comunicación sincronizada y asincrónica)

Como se ve en la invitación, hay pequeños grupos/sub-grupos de trabajo dentro del Grupo de trabajo del SotM para una coordinación más organizada.

Claves:

… See full entry

What I did in OpenStreetMap in July 2021

… See full entry

Moin!

ich muss jetzt einfach einmal einige Worte loswerden.

Wir mappen in der ganzen Welt wenn irgendwo eine Flutwelle über das Land herbricht oder auch die Erde erbebt.

Mir ist bekannt, dass zu Beginn der Hochwasserkatastertrophe im Ahrtal und auch in den anderen Gebieten, die vermutlich nicht so bekannt sind - dennoch schwerst getroffen sind, darum gebeten wurde die Karte unverändert zu lassen.

Zwischenzeitlich erkennt man in den Karten die eine oder andere Behilfsbrücke und auch die als zerstört gekennzeichneten Straßen.

Aber ansonsten ist es in den OSM-Kanälen sehr ruhig um das Human-Mappen im eigenen Land.

Ich sehe gerade einen Bericht mit Markus Wipperfürth, einem der Helfer der ersten Stunde, und wieder wird auf Google Maps verwiesen. Dabei sind das doch mehr als veraltete Daten vermutlich.

Irgendwo hatte ich einmal von Bilder einer Befliegung etwas gehört, aber dann ist es wieder stumm geworden.

….

Ich lasse hier meinen Beitrag einmal offen enden.

Gruß Jan

This is a follow-up to a pedrito1414 diary entry on Silvester 2020, which itself, at least from my point of view, was a follow-up to a IRC chat the two of us held on 2020-12-15.

From our chat Pete distilled a short list of nine more or less urgent “issues to address / aspects to improve”. We’re 8 months later and a few days ago I downloaded the online HOT projects summaries, to choose some statistics that might let us measure the process and how it has been improving. Of these 9 points I think that the easiest to measure are #6: “TM projects don’t always get closed out” and #2: “Tasking manager transparency - project creators”.

Let’s start from #6 about non closed projects.

The one thing that HOT is not doing, they are not systematically setting a limit to the projects they host nor directly run: of the 3009 still active projects, 2848 (94%) does not have a due date. for the 587 projects that have been created this year 2021, 460 (78%) does not have a due date. it is a small improvement. limiting this to directly HOT owned projects, it’s a total of 315, of which 297 (94%) do not have a due date. This year it’s 111 projects directly owned by HOT, 94 (85%) of which without due date.

I’ll mention the two top outliers, which did set a due date goal for all their projects: osm-libya (37 projects) and unique-mappers-network-nigeria (5 projects).

Without a due date, it’s easy to let things slip through your fingers, so no surprise there’s still 2 open projects from 2012, 24 from 2013, 27 from 2014, and a total of 1378 unclosed projects published before 2020.

The other issue, #2 about project creators, in my opinion it has to do with local involvement, or lack thereof.

… See full entry

GIS Addict Agriculturalist🙂 Hardworking Scientist Catholic Charismatic Christian🙏

Tried to produce map files for apps like Orux/Locus and such using the mapwriter plugin using an i3 and SSD disk.

Managed to get to zoom 4 before getting yeeted with thread error (or something) after 63 minutes of processing. Ughhh…

Részleteket lásd:

https://wiki.osm.org/wiki/Hungary/20210818

Javasoljuk, hogy aki jelentkezik erre az eseményre, lépjen be az OpenStreetMap-Hungary GetTogether csoportba és állítson be email címet, hogy értesüljön a jövőbeli eseményekről is.

With my dear love, Tanya Unger

the idea is to map waste as it transits from source to environment, and work to apply data and public awareness to reverse that trend.

ทั่วไป หนึ่งสามารถอัพเกรดใบอนุญาต? ปัญหานี้เกี่ยวข้องกับ ODbL เท่านั้น (สำหรับสิทธิ์ใช้งานอื่นๆ ทั้งหมด ไม่มีอะไรให้ ‘อัปเกรด’) สำหรับ ODbL คำตอบคือใช่ - อยู่ภายใต้ข้อแม้บางประการ คล้ายกับใบอนุญาตที่เหมือนกันของครีเอทีฟคอมมอนส์ ODbL มีประโยคที่อนุญาตให้งานลอกเลียนแบบได้รับอนุญาตภายใต้ a) ว่า ODbL เวอร์ชัน b) ODbL เวอร์ชันที่ใหม่กว่า c) ใบอนุญาตที่เข้ากันได้ (ใบอนุญาตที่เข้ากันได้จะเช่น ต้องมีข้อกำหนดการแบ่งปันที่คล้ายกันหากจะเข้ากันได้) ความตั้งใจที่นี่คือการให้ความยืดหยุ่นแก่ผู้ที่ผลิตผลงานลอกเลียนแบบในอนาคต ในขณะเดียวกันก็ดูแลให้องค์ประกอบหลักของข้อกำหนดที่เหมือนกันทุกประการได้รับการอนุรักษ์ไว้

ทำไมคุณถึงแยกความแตกต่างระหว่าง “ฐานข้อมูล” และ “เนื้อหา” คำตอบที่ง่ายที่สุดคือเพราะพวกเขาอาจมีสิทธิแยกต่างหาก ตัวอย่างเช่น พิจารณาฐานข้อมูลของภาพถ่าย ที่นี่มีสิทธิในฐานข้อมูลและค่อนข้างแยกลิขสิทธิ์แต่ละภาพในภาพถ่าย หรือพิจารณาตัวอย่างของ Freebase ซึ่งมีเนื้อหาที่เป็นข้อความและรูปภาพจาก Wikipedia รวมถึงเนื้อหาที่ผู้ใช้มีส่วนร่วม แม้ว่า Freebase จะควบคุมฐานข้อมูล แต่เนื้อหาแต่ละรายการจะต้องมีใบอนุญาตแยกต่างหาก

แน่นอนว่าบ่อยครั้งที่ผู้อนุญาตของฐานข้อมูลอยู่ในฐานะที่จะอนุญาตสิทธิ์ (ถ้ามี) ในเนื้อหา — ตัวอย่างคลาสสิกจะเป็นฐานข้อมูลที่มีข้อมูลที่เป็นข้อเท็จจริง ด้วยเหตุนี้ เราจึงได้สร้างใบอนุญาตเนื้อหาฐานข้อมูลอย่างง่าย ซึ่งคุณสามารถใช้ร่วมกับ ODbL เพื่อให้แน่ใจว่าคุณได้รับสิทธิ์ใช้งานทุกอย่าง

สรุป:

… See full entry

我首先在使用该网站地图数据的游戏中发现了路网不全的情况（三线小城市），当我来到这里编辑地图时发现这些卫星图像已经非常过时了，有很多新建的道路和建筑物没有在供参考的卫星图中被更新。好气哦QAQ

In this blog post we want to count addr:housenumber nodes across all EU member states, broken down by country. That’s a bit above 34 million nodes in total.

Queries are tested on different Overpass instances: two rather busy public ones, one idle private instance and a dev instance. With the exception of the latter, queries run on offical Overpass releases. Database contains a full planet (including metadata and history).

Query: https://overpass-turbo.eu/s/1adO

[out:csv(name, count)];
rel(2668952);rel(r);
map_to_area -> .areas;
foreach.areas->.area (
  node["addr:housenumber"](area.area);
  make data count = count(nodes),
            name = area.set(t["name"]);
  out;
);

Result: https://gist.github.com/mmd-osm/5219028c9fa93db17ac7c271a99183a1

Runtimes

kumi.systems:     gateway timeout after 1h
overpass-api.de:  gateway timeout after 2h
private server:   timeout after >2h
dev branch:       30s

NB: dev branch is exploring alternative implementation options and is currently not released.

Well, today I checked in my first JOSM edits.

First was a boo boo. I cheated and used iD to revert… hah.

Second was what I intended as the first checkin - found out that iD was deliberately nerfed to not allow the edit I wanted to do. Still haven’t figured out the best way but oh boy, JOSM was much easier to move a node 10 miles away. Did a few in iD and that was really no fun.

Then a few more edits in JOSM… just to not get annoyed when iD nags “You didn’t fix the warning I flagged.”

“But I didn’t make the warning… and I don’t know enough to actually fix the warning!”

grumble grumble…

I was doing some HOT mapping on an old project in Nigeria recently and noticed that depending on how I access the project, I get different versions of the Bing imagery.

If I use the HOT tasking manager (either using iD or JOSM) or direct JOSM download as a starting point I get a lower resolution image that is clearly a different vintage than if I open it direct from the OSM page through the iD editor.

I can’t tell which is more recent as buildings appear and disappear in Nigeria so no telling without some local knowledge.

Someone suggested that it’s likely due to accessing different API endpoints (which I don’t quite know what this means).

Time for some more investigating. I’d love to be able to use both sets of images. Maybe I’ll post on why I want to do that as a separate entry when I get a free moment.

Here’s how to check cycling mapping mistakes and fixme’s in your area:

1. Go to Bicycle tags map
2. From upper left corner, select “bugs in tags”
3. Zoom into area of interest
4. From menu on the right you can select/deselect features to show

This way I could see a few fixme’s in my area, plan a route with OsmAnd application, observe and make necessary updates to the map in Oulu area.

And on my way yesterday I was able to visit the new separated cycleway opened the same day. Really liked to ride it. Have a look from our Baana Engineer’s twitter video.

Happy cycling, everyone!

Juhani

This event was an interaction with local youth contributors of various universities and organizations. Along with a three-day long Mapathon was held in this program.

Dom

I have just updated some structures( as-builts) around National Capital District in Port Moresby in PNG. After seeing some street having awkward shapes(partially incomplete), I have deleted these and updated with correct tags. Most of the roads did not have correct tags( as most roads in PNG residential and rural areas have 6.0 m width as approved by Department of Works-PNG). I even updated the road surface based on the type of material the roads are built with( mostly asphalt, gravel and dirt/grass). Most Building do have Heights/Levels and using correct level tags, those Buildings not having the correct heights/Levels have been re-edited with correct tags. When also checking on Power transmission Pylons, the average Height is 30.0m, I have re-edited the pylon height again by setting the correct height. The type of landcover( whether grass, forest, concrete asphalt etc.) has also been updated of some streets that I was rechecking/verifying around National Capital District(NCD).

Thanks to the use of F4map.com, I was able to see the update in 3D after the edits were made 48Hrs later. Please do use correct tags in OSM to improve OSM maps.

Once again, thankyou and happy mapping to you all Mappers.