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 highway=trunk to 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

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 name=20 Avenue and 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

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 osm.org/user/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.

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

… See full entry

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.

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.

I completed my first 100+ physical addressing on Magnolia Ave., Birch Run Ave., Redwood Rd., Hickory Rd., Elder Pl., Hemlock Dr., and Beech Pl. The project took about 3+ hours to complete. I’m new but will soon get into other tasks. ChangesetID: osm.org/changeset/145716852

addr:city=Denville

addr:postcode=07834

addr:state=New Jersey

addr:street=

addr:housenumber=

I got my husband to join me and help me with mapping today. We went from approx. State Line Road in KC on 43rd St (we think of it as 43rd though there is a stretch that’s Westport Rd) and down to the west end of it just beyond Mission.

We went to Sway Coffee Roasters and had a nice cup of coffee/tea, and got to say hello to some sweet dogs that another customer brought with them. The dogs visited everyone within leash distance and everyone seemed happy to see them. Little random encounters are what make me love the city so much.

My plan next is to visit the stretch of 43rd east of Gillham Park, and to touch some of the “nodes” I skipped over when going along the length of it, like St Luke’s and various parks etc.

QPFF+F9R, QPFF+CFR, Grand Trunk Rd, Wah, Cantt, Rawalpindi, Punjab 4700, Pakistan

Satellite Town is the Controlled Area near by GT road and Basti Lalarukh wah cantt. A ghost Town in triangle shape with the flavor of dead end.

Leboya Bay Edits

It was fun editing Leboya bay, it was missing some information and buildings. We went for three days camping and I had fun surveying the area and discovering what the camping site had to offer.

Based on a coincidence, I used Overpass in my area to try to identify objects marked for removal that are older than period X. Unfortunately, I didn’t manage it so easily and at the same time had the idea whether it wouldn’t be better to check this on site via street complete. In the course of the GitHub issue, however, it turned out that it doesn’t really fit the core of Street Complete.

So back to Overpass and the good old query in advance to be able to check it later on site. With the help of other OSM users on Telegram, the following query was created, which can be easily customized:

https://overpass-turbo.eu/s/1Fml

To be on the safe side, the overpass query is shown here as code:

//Check for Stages of decay
//based on the idea of:
//https://github.com/streetcomplete/StreetComplete/issues/5402

[out:json][bbox:{{bbox}}][timeout:800];
//gather informations about non-excisiting objects
//and store the data as "gone"
(
  nw[~"^demolished:.*$"~"."];
  nw[~"^razed:.*$"~"."];
  nw[~"^removed:.*$"~"."];
  nw[~"^destroyed:.*$"~"."];
)->.gone;

//substract any gone-object, that was last modified
//within the last X years
(.gone; - nwr.gone(newer:"{{date:1year}}"););

out geom;

Start time: 6:42pm End time: 7:49pm

Tidal and non-tidal wetland

A major rewrite here takes into account tags such as natural, reef, wetland, surface and tidal before deciding how to show wetland areas. See the picture above, which is here, and here in OSM.

The beach between high and low tide can be clearly seen here (in OSM, here). There are blue dots in the sand rather than black. A deliberate decision was taken to show more detail for areas above low tide. See e.g. here between Wales and the Wirral (see here in OSM).

Island and islet names

… See full entry

Over the last few days I have been chipping away at validating tasks for the #osmIRL_buildings project.

I have now just finished validating all of Howth. There is still a good bit left in the rest of the county, some of it will definitely be quick due to some areas being rather rural.

As I’ve noted elsewhere, I’m working on moving the JOSM plugin repository from svn to git.

I’ve managed to get something for most authors, but I am still missing attribution information for 47 authors with 95 commits between them.

If you have previously contributed to the JOSM plugin svn repository or the OSM svn repository (which used to include the JOSM plugin svn repository), please reach out to me via OSM messages or email (tsmock@meta.com, taylor.smock@kaart.com, or smocktaylor@gmail.com) if the attribution for your contributions is missing or wrong.

What I need from you:

• The name you want your patches to be attributed to
• The email you want your patches to be attributed to
  • As a reminder, this email will be publicly visible via git history. GitHub and GitLab both have noreply email addresses if privacy is a concern for you.
  • Grant Slater (firefishy) has the map used for migrating http://svn.openstreetmap.org/ to git. This will likely be used as a “last resort”; if the attribution from that conversion is OK, then no action is necessary.
• Optionally, the timezone offset for your patches (UTC±offset)

Notes on the conversion:

• patch by <foo> commits have been modified such that the originator (“<foo>”) is shown as the author, while the committer remains unchanged.
• Doesn’t do much to reduce repo size – git lfs could be used for this prior to the final conversion
• The dist directory for plugin releases has been excluded from the test repository due to size constraints
• Does not split plugins into their own repositories. This can be done later.
• plugin externals were converted to submodules; if a plugin had externals in it, those were not converted

WIP Repositories (please do not fork these; I may rebuild them at any time as I get new attribution information):

• JOSM core: https://github.com/tsmock/josm
• JOSM plugins + jmapviewer: https://github.com/tsmock/josm-osmsvn-svn2git

Earlier this month during Wikidata Data Modeling Days Hannah Bast from University of Freiburg presented QLever, a SPARQL query engine with some really cool features (slides, recording). After a month of using it, in this post I’ll discuss how it’s relevant for the OSM community and my experience so far.

What’s SPARQL and why should we care?

SPARQL is a query language for RDF data, which can come from RDF-native knowledge graphs (there are thousands of them, public and private, the best known in the OSM community is Wikidata) or other sources (for example OSM) converted in RDF with some tool or middleware

SPARQL includes an optional extension for geospatial data, geoSPARQL. Query services implementing it allow to run all kinds of spatial queries with a naming similar to other query languages based on OGC standards (like SQL on PostGIS).

One notable feature of RDF and SPARQL is that they are made from the ground-up for interoperability between different data sources (“linked data”). SPARQL natively supports querying multiple RDF data sources in one single query through “federated queries”. This works by specifying inside the query to the first service the URL of the second service and its query, then specifying how the result should be merged or joined to the data from first service. If the second service is not blacklisted, the first service will handle autonomously the communication, merge the data and return directly the final output.

QLever

QLever and osm2rdf are two projects by the University of Freiburg; they were introduced respectively in 2017 and in 2021 but only recently started getting attention in the OSM world.

osm2rdf is a tool for converting OSM data into RDF. It transforms geometries from OSM’s node-way-relation format to Well Known Text (WKT) and can indirectly materialize containment and intersection relations between elements to improve spatial querying speed. It’s FOSS and extracts of the data it generates are available online.

… See full entry

I have started an independent collection of OSM SLA statistics. Approximately once a month, I will publish my results with the aim of enhancing transparency regarding the reliability of OSM services. I use uptime-kuma to run monitoring. I also verify connectivity with non-OSM services (to prevent false positives). The current configuration includes checking the availability of openstreetmap-website and openstreetmap-cgimap (API). Tile layer availability is not currently included in the checks. The health-check resolution is set to 30 seconds, and the checks are executed from a single server in the Hetzner datacenter in Germany. For the endpoint to be marked unavailable, two consecutive checks must fail. This should be well-representative of an average user experience.

Summary

Total API downtime: 2 hours 34 minutes 13 seconds

API SLA: 99.643%

Total website downtime: 43 minutes 15 seconds

Website SLA: 99.900%

Note that some functionalities of the website require API to also be available.

Details

2023-11-30 10:07:24 - 2023-11-30 10:09:40

• Total downtime: 2 minutes 16 seconds
• 🚩 API unavailable

2023-11-30 10:16:16 - 2023-11-30 10:21:31

• Total downtime: 5 minutes 15 seconds
• 🚩 API unavailable

2023-11-30 21:34:44 - 2023-11-30 21:36:14

• Total downtime: 1 minute 30 seconds
• 🚩 API unavailable

2023-12-01 04:27:18 - 2023-12-01 04:29:00

• Total downtime: 1 minute 42 seconds
• 🚩 API unavailable

2023-12-01 17:26:20 - 2023-12-01 17:29:20

• Total downtime: 3 minutes
• 🚩 API unavailable

2023-12-01 17:45:06 - 2023-12-01 17:50:39

• Total downtime: 5 minutes 33 seconds
• 🚩 API unavailable

2023-12-01 17:50:39 - 2023-12-01 18:04:09

• Total downtime: 13 minutes 30 seconds
• 🚩 API unavailable
• 🌐 Website unavailable

2023-12-01 18:04:09 - 2023-12-01 18:06:51

• Total downtime: 2 minutes 42 seconds
• 🚩 API unavailable

2023-12-01 18:09:38 - 2023-12-01 18:10:23

• Total downtime: 45 seconds
• 🚩 API unavailable

2023-12-01 18:12:25 - 2023-12-01 18:17:09

… See full entry

The 30th of November saw the 4-year anniversary of the #osmIRL_buildings project, an ambitious project of the Irish OSM community to map all the buildings on the island. Co. Kilkenny had been the first project to be finished in the task manager in April of 2020, and I thought that it was high time to look at it again.

Since I live in that county, I had noticed missing buildings once in a while being on the road or mapping other things remotely. Relatively new (summer 2022) aerial imagery had been made available by Esri World which wasn’t as clear as Bing, but more recent.

So I decided to make a private task in the task manager and update the whole county by myself. I like to have side quests to make it more interesting, so I decided to also look for unrecorded archaeological sites. The summer of 2022 had been very dry, so crop marks would be more visible on the Esri World imagery. I wanted a private task, so nobody would map any of the tiles, and I might miss something. I usually map the bulk of the other tasks anyway, but I did not want to take any chances. This was going to be the most thorough search for crop marks and other clues to archaeological sites Kilkenny had ever seen. Or so I believe.

All in all, it took me 11 days or 75.5 hours (average time per task multiplied by tasks), but I had excluded Kilkenny city, because I usually have an eye on that all the time.

… See full entry

I started mapping by updating shop details in my area and have now moved on to helping OSMirl in completing the various tasks to get all of Ireland on the map.

I have also started adding buildings to my home city of Port Elizabeth, South Africa. The majority of the suburb (that I’ve worked on) does not have any of the houses mapped.