OpenStreetMap logo OpenStreetMap

Users' Diaries

Recent diary entries

The Municipality of Crowsnest Pass is bounded on the west by the BC/AB boarder and on the east by the municipal district of Pincher Creek.

Alberta Highway 3 passes through this municipality.

My edits in Changeset: 145865015 are as follows.

Change https://wiki.openstreetmap.org/wiki/Tag:highway=trunk to https://wiki.openstreetmap.org/wiki/Tag:highway=primary

From the Canada Tagging Guidelines for Primary Roads primary roads are typically 2-lane, undivided, provincial highways. This description is accurate for Highway 3 through the Crowsnest Pass.

See also the Alberta Highway Classification Guidelines

https://wiki.openstreetmap.org/wiki/Tag:highway=trunk, however, is suggested for “the national highway system”.

Contrary to my change, the National Highway System page on Wikipedia lists Highway 3 as a core road in the national highway system. This may need reversion.

Change to https://wiki.openstreetmap.org/wiki/Tag:name=20 Avenue and https://wiki.openstreetmap.org/wiki/Tag:nat_name:en=Crowsnest Highway

Within the Municipality of the Crowsnest Pass, Highway 3 is labelled on street signs as 20 Avenue. This is similar to how Highway 1 is also 16 Avenue through the City of Calgary.

The Canada Tagging Guidelines for Named Major Highways explains that when a named highway also has a street name, tag:name should be used for the street name and tag:nat_name should be used for the highway name.

Changes to maxspeed

I have personally surveyed the speed zone changes.

The Municipality of Crowsnest Pass also posted a map of speed zone changes that took place in 2019

Other resources

Crowsnest Pass GIS

Posted by Zkir on 3 January 2024 in Russian (Русский). Last updated on 5 January 2024.

Друзья, всех с наступившим новым годом!

Пусть в новом году будет отрисовано то, что раньше даже не приходило в голову. Как говорится, то, что не видел глаз и не слышало ухо, во всяком случае глаз и ухо осм-сообщества.

А я между тем поборол tilemill и всё-таки сделал онлайн-карту ландшафтов (покрытий, landcovers).

Смотреть можно тут:

http://osm2.zkir.ru/landcovers/

картинка для привлечения внимания, было-стало

Показываются ландшафты (natural+landuse), населенные пункты и, по приколу, горные вершины. Отображаются зумы с нулевого по восьмой. Обновление по требованию.

В ближайших планах:

  • Наладить автоматические обновления. Похоже, это проблема, потому что обновление через osm2pgsl пока еще ни разу успешно не завершилось.
  • Вспомнить ради чего я всё это затеял. Кажется, я собирался сделать картостиль, имитирующий фотореалистичный спутниковый снимок.
  • Пофиксить отображение городов, чтобы показывались пунсоны, как в стандартном стиле.

В предыдущий раз мы говорили о покрытиях и генерализации тут:

See full entry

I’ve created a changeset which fixes 117 links to Wikipedia disambiguation pages on segments of I-15 in Utah as identified by https://matkoniecz.github.io/OSM-wikipedia-tag-validator-reports/Utah,%20USA.html

In a nutshell, this change updates the wikipedia tag value, changing it from a disambiguation page to a specific article:

Old Link: https://en.wikipedia.org/wiki/Veterans_Memorial_Highway

New Link: https://en.wikipedia.org/wiki/en:Interstate%2015%20in%20Utah

This work is part of a larger MapRoulette challenge, https://maproulette.org/browse/challenges/40609, created by @Mateusz%20Konieczny to address problems with Wikipedia links in OSM data.

Rather than completing 117 separate MapRoulette tasks I downloaded JSOM data using the following Overpass API query and performed a bulk edit.

[out:xml][timeout:90][bbox:{{bbox}}]; ( way["wikipedia"="en:Veterans Memorial Highway"]; ); (._;>;); out meta;

As this is my first large-scale edit I have tagged the change as needing a review –I will also ping matkoniecz so that the validator report summary page can be updated.

Posted by qeef on 2 January 2024 in English.

Welcome to the summary of work done in the fourth year of Divide and map. Now. – the damn project that helps mappers by dividing a big area into smaller squares that people can map together.

Four years ago, the damn project was developed to constructively criticize the HOT Tasking Manager. (HOT stands for the Humanitarian OpenStreetMap Team.) I see that the limitations of the HOT Tasking Manager persist, that it is not getting better, and that the developers of the HOT Tasking Manager can still benefit from constructive criticism.

In this diary, I will first recap the functionality and scope of the damn project. Then I will write about the work in 2023 and the work for 2024.

Functionality and scope

To understand the damn project, let us break it down into four main components, each of which has its own repository: the server, the web clients, the JOSM damn plugin, and the deployment guide. The deployment (for sysadmins) brings up the damn project. The damn server (for backend developers) contains the core service – JSON API to the PostGIS database. The JOSM damn plugin connects to the damn server so that mappers do not have to open the web browser to contribute to OpenStreetMap when using the damn project. Finally, the web clients repository (for frontend developers) contains the code base for multiple web clients.

The features available to mappers are divided into the JOSM damn plugin and the web clients, as the damn project serves multiple groups of mappers and recognizes these groups.

See full entry

Posted by amartineau on 1 January 2024 in French (Français).

J’ai ajouté la Rue des Pruniers qui part de Cap-Aux-Corbeaux Nord, c’est un ancien chemin privé devenu chemin public dans les dernières années. Et là où habite mon beau-frère qui a des problèmes avec les livreurs d’Amazon. Google Maps avait le même problème.

Aussi modifié le nom du ruisseau qui croise cette rue de Ruisseau du Bois-Blanc à Ruisseau Chez Lucien, d’après les cartes de la MRC.

Location: Baie-Saint-Paul, Charlevoix, Capitale-Nationale, Québec, Canada
Posted by kucai on 1 January 2024 in English.

I have the suspicion that my phone is tagging the GPS location for some photos rather wrongly (timed offset is my guess). Found this out when comparing the locations against those indicated on JOSM photo overlay.

This despite the phone getting both L1 and L5 signals, and running with no sim card which should reduce cpu load further since there’s not much background processes that need to be handled.

To say I’m pissed is rather an understatement. Moving on, I will try leaving the phone to only record gps track and then matching photos from my cameras to that. No electronic shutter so extra wear and tear on that mechanical one! Shoulda bought that oly em10 back then.

Posted by soumendrak on 1 January 2024 in English.

Day-27

  • I wish you all a fantastic new year, 2024 to you. I hope this year will bring new challenges, new things to learn, and new findings with atma samikhyan.
  • Pascal’s sites are up; I am in the top 4 now.

Bhubaneswar, Odisha

  • Almost all central Bhubaneswar building mapping I have completed.
  • The next task will be to complete the peripheral areas.
  • Next, I will start adding PoIs into the buildings. I am unsure if marking buildings and adding PoIs simultaneously is recommended or if I plan to return for the PoIs in the next phase.
  • I am going to Bhubaneswar next month to gain some on-the-ground knowledge on new developments around.

Rest of Odisha

  • Malkanagiri roads addition is almost complete.
  • Koraput roads addition just started near the Andhra Pradesh and Odisha border.

Looking ahead

  • The progress is pretty slow, and I do not know how many days or months I will need to map the entire Odisha. Can I do it?
  • To speed things up, should I start an OSM Odisha group? I’m not sure if any other person will be interested.
Location: BHBCS Layout, BTM Layout, Bangalore South, Bengaluru Urban, Karnataka, 560076, India

Heute, beim erstmaligen Versuch des Mappings mittels streetcomplete versuche ich vergeblich, die Funktion der Längenmessung auf einem Smartphone zu aktivieren. Ich nutze ein Fairphone4, das Google ARCore nicht unterstützt. Es funktioniert also nicht. Keine Augmented Reality, keine Entfernung. Ich benutze also eine einfache Variante, um die Breite von Fahrwegen zu bestimmen: die Schrittlänge. Die beträgt bei meiner Grösse durchschnittlich 75 cm. Also einfach die Fahrbahnbreite abgegangen (Achtung, Verkehr!) und dann auf die vollen Meter auf- oder abgerundet. Mehr verlangt die App auch gar nicht: runde Meter.

Man kann es sich auch schwermachen in der digitalen Welt, oder einfach, indem man sich ein wenig unabhängig macht und selber denkt!