User talk:Mateusz Konieczny

Building:part staircase

Hi Mateusz, I reverted your revert here: Key:building:part —Dieterdreist (talk) 20:31, 29 September 2025 (UTC)

@Dieterdreist: if you reviewed this edit and can vouch that it was fine: then it is OK Mateusz Konieczny (talk) 09:59, 30 September 2025 (UTC)

Yes it looks fine to me. I guess you also reviewed it to come to the conclusion it should be reverted. Was it because of the relatively low numbers, or do you think the value is not suitable as a "building:part", or something else? --Dieterdreist (talk) 11:32, 30 September 2025 (UTC)

@Dieterdreist: I was mass-purging all edits by banned account of User:Rtfm (they made next sock), this was done without any review of content Mateusz Konieczny (talk) 12:59, 30 September 2025 (UTC)

Ah ok, I think this one is ok. —Dieterdreist (talk) 15:53, 30 September 2025 (UTC)

Resolved: Mateusz Konieczny (talk) 09:23, 20 January 2026 (UTC)

Examples for pedestrian roads

Hi, I would like to discuss our edits on the Tag:highway=pedestrian page – particularly this partial restoration of content I had removed. To me, this image depicts a wide, comfortable footway – but that's still a case for highway=footway. Unless there are other arguments than what's visible on the image (e.g. signage), I don't see it as a good example of a pedestrian road. --Tordanik 17:28, 27 April 2018 (UTC)

Google using OpenStreetMap data

Re: "When Google stopped map maker? Maybe it was added not by Google employee but by someone convinced to work for corpo for free?"

I was offered a chance to be approved as a unpaid mapper for Google a while back, when I had been still adding photos and POIs to Google Maps. I believe if you are a trusted volunteer contributor you can still get access to update street names and perhaps even geometries, though I decided not to give a corporation free labor anymore. I suspect that you are right, these changes were probably copied from OpenStreetMap by a volunteer mapper who did not properly understand the copyright issues. --Jeisenbe (talk) 23:03, 6 February 2021 (UTC)

Re:Source of file

Hi Mateusz, the image was generated only by OSM data, it was a screenshot from JOSM. I had initially uploaded the image to my account on a free social network that no longer exists called gnewbook. Here you can see other similar images from the mapping event in 2011. --Ovruni (talk) 08:40, 10 March 2022 (UTC)

Hi Mateusz, the file which I used in Mashhad OSM wiki page is produced by myself via a web page that produces a .GIF file of mapping history of a location over the time. Unfortunately this useful site doesn't works yet, but I know that we could download and use its images whenever and where ever we want.

Getting compound key documentation from the MediaWiki API

Hi, this is sort of tangential to the discussions we're having over in Talk:Wiki, so I'm splitting this off here for convenience. It sounds like you're building an interesting tool in Python. I'm surprised that you're finding it necessary to scrape user-facing pages, even from Python. If something about this wiki led you to that approach, versus something more structured, please let the administrators know so we can look into improvements. In general, scraping should be a last resort, so that in the future we don't end up constrained by what's essentially tagging writing for the renderer scraper.

I was just going back and double-checking one of my suggestions to make sure I wasn't misleading you. The following code is a port of the compound key description stuff in Module:Tag – everything but the language name fallback. It requires the Requests package, but there's also a built-in json module if you need to work with a different HTTP client library. I wouldn't be surprised if this runs faster than scraping the 404 page using something like BeautifulSoup.

#!/usr/bin/env python3

from itertools import product
import requests

key_parts = "construction:turn:lanes:both_ways".split(":")
# Enumerate all possible slices of the key, putting longer slices before their subslices.
key_part_range = range(len(key_parts))
key_part_slices = [key_parts[s:e] for s, e in product(key_part_range, reversed(key_part_range)) if e > s]
# Convert the slices into article titles.
titles = ["Key:{0}".format(":".join(s)) for s in key_part_slices]

# Query Wikibase for the data items' descriptions.
params = {
    "action": "wbgetentities",
    "format": "json",
    "sites": "wiki",
    "titles": "|".join(titles),
    # The OSM key name is always stored as the English label.
    # It needs to be part of the response so we can associate keys with their descriptions.
    "props": "labels|descriptions",
    "languages": "en",
}
request = requests.get("https://wiki.openstreetmap.org/w/api.php", params=params)
response = request.json()

# Annotate the key parts with their descriptions.
remaining_key_parts = key_parts
items = []
for qid, entity in response["entities"].items():
    # Omit missing data items.
    if type(qid) != str or "missing" in entity:
        continue
    label = entity["labels"].get("en") and entity["labels"]["en"]["value"]
    description = entity["descriptions"].get("en") and entity["descriptions"]["en"]["value"]
    key_part_slice = label.split(":")
    # TODO: Actually search remaining_key_parts for a common slice.
    if description and key_part_slice == remaining_key_parts[0:len(key_part_slice)]:
        del remaining_key_parts[0:len(key_part_slice)]
        items.append((qid, label, description))

# Output the list of key parts.
for item in items:
    print("* {1}: {2} ({0})".format(*item))

Output:

* construction: Used together with the higher-level tags like highway/building=construction to describe the type of feature which is currently under construction. (Q172)
* turn:lanes: A diagram of the turn lane indications on a one-way road. Each lane is represented by a direction such as left, through, or right, and the lanes are separated by vertical bars. Use key:turn:lanes:forward and key:turn:lanes:backward on a two-way road. (Q796)

The code is a bit dense, but it comes pretty close to the original Lua veresion, so let me know if you have any questions about how it works. Hope this helps.

 – Minh Nguyễn ^💬 06:18, 25 July 2022 (UTC)

@Minh Nguyen:

Thanks!

"I'm surprised that you're finding it necessary to scrape user-facing pages" - in this case I want to verify existence of user-facing pages for https://github.com/streetcomplete/StreetComplete/discussions/3442 and to lesser extent https://github.com/streetcomplete/StreetComplete/issues/4225 - I want to link specific key pages where documentation exists. So I want to catch cases where all necessary building blocks exist but for some reason user generated compound page is missing, such as https://wiki.openstreetmap.org/w/index.php?title=Key:name:mos where compound page is not displayed

Right now specifically it is a Kotlin code (for https://github.com/streetcomplete/StreetComplete/issues/4225 ), but it would be easy to adapt. Still, this code cares what is shown to user - so checking generated pages is deliberate. After all, even if data items are listed and compound page lister is broken or disabled by design on some pages: it is still not shown to users. Mateusz Konieczny (talk) 06:48, 25 July 2022 (UTC)

OK, the scraping should be workable as long as it isn't coupled so tightly that StreetComplete would be broken by routine formatting changes. Others have been tinkering with the site stylesheets and banner templates lately, so it's only a matter of time before the 404 page gets some interior decoration too. :^) I guess the infobox needs classes/IDs/microformats too. It'll be interesting to see how this feature turns out. iD took a very different approach by hitting the MediaWiki API for data items and displaying that information inline. However, it doesn't have any compound key logic, because arbitrary combinations of key parts tend not to have dedicated fields anyways. Maybe that would change if it ever gains lane-editing functionality like StreetComplete has. – Minh Nguyễn ^💬 07:54, 25 July 2022 (UTC)

@Minh Nguyen:: It is less fragile as the plan is to blindly link wiki pages based on simple rules (do not link values of freeform pages such as width=* or name=*, do not link value pages with cycleway: prefix like cycleway:surface=asphalt, link all building values such as building=office, always link key pages and so on). Right now only name:lang pages are not working as expected (as sometimes compound info is not shown). With script just verifying that linked OSM Wiki pages are actually containing info (useful compound pages or existing pages or redirects leading to an useful documentation page), and not running in app itself. Script above may be useful to test whether compound pages are missing some info and just assume that if this info is present then it will be used. As side effect I reviewed keys used by SC and created for example building=pagoda Mateusz Konieczny (talk) 11:02, 25 July 2022 (UTC)

How about subkeys unrelated to names, like change:lanes:both_ways (Q9383) and seamark:virtual_aton:mmsi (Q20907)? Should the individual parts be listed even though there's a pretty comprehensive description in the infobox? Or should the description be repeated outside of the infobox? – Minh Nguyễn ^💬 00:38, 27 July 2022 (UTC)

@Minh Nguyen: I would also expect listing compound part there, important part is providing links to pages with actual documentation and explanation. Without that I feel that creating OSM Wiki description pages would be substantial improvement and therefore worth doing. I am also considering "dedicated nonempty data item exists for this tag" as reason to create OSM Wiki description page but it is much weaker Mateusz Konieczny (talk) 04:30, 27 July 2022 (UTC)

Uses of access=permit

In [1] you removed my warning against different and unknown uses of access=permit and ask "Are you aware of anything indicating that access=permit has serious use in a different meaning?" . I think I do. I see many people put this like motor_vehicle=permit tag on many forest roads, that are signposted "Only for motor vehicles of National forest authority" or "Only with permission from National forest authority". I really doubt the authority will grant permission to random tourists wanting to park their campervan on top of a hill. I tried to contact the mappers on how they meant it, but they never reply, they often seem to be ocassional drive-by changes from people with few changesets. So as the tag hasn't been approved yet, nobody knows how people use it and what it means for them. I just do not want people slap access=permit on any road with a sign having "permit" in its text, without understanding the implication. We do not need another access=permissive which is a really unfortunatelly chosen word that 50% people use wrongly thinking it means "needs permit" (and one that is not granted "regularly", thus basically it is "private"). I don't know if it is caused by bad translations in editors, or why that is. So let's not create the same situation here. Aceman444 (talk) 11:09, 11 July 2023 (UTC)

OSM attribution in MAPS.ME

In the current version of the app, the attribution is located at the top of the screen for a few seconds. It seems that this can be considered compliance with the attribution, although partial

https://i.imgur.com/Bga3t77.png

E8 hiking path

Hi Mateusz, I recently saw you are involved in editing at Germany/Wanderwege-Netz. I am completely overwhelmed with editing here myself, so I would like to ask for your help. The E8 long-distance hiking path has a northern and southern variant in Germany, more precisely between the Donnersberg mountain and the city of Tauberbischofsheim. However, as you can see here, there is a huge gap between Speyer and Buchen, where the path is also existing in reality, but missing on the map. Here is a PDF document of the local Odenwaldklub (Association) what is accustomed for this section of the path. It contains the local hiking paths which are congruent with the E8 in the Odenwald (all existing on OSM), so it should be no problem to add the E8 southern variant on OSM. Is it possible for you to help out here? I hope it's not much of work to do. Regards Stefan1893 (talk) 11:00, 26 August 2025 (UTC)

@Stefan1893: sadly, I was only doing technical maintenance. I would ask for help at https://community.openstreetmap.org/c/communities/de/56 - login with OSM account, German seems preferred there (note: I have no idea can we use that source) Mateusz Konieczny (talk) 13:47, 26 August 2025 (UTC)

Thank you for your reply, I asked there. Regards Stefan1893 (talk) 14:09, 26 August 2025 (UTC)

Proposed Blocked Tiles page revision

With the aim of clarifying the different reasons for blocks, separating the "user" and "developer" content from each other and making it more actionable (i.e. more descriptive in how to fix the block issue), I've drafted a new proposal to replace the Blocked tiles with User:MarkWoodbury/Blocked_tiles_draft. As I see you've recently been involved with editing the original, I'd welcome your input and comments/proposals on the new draft. Thanks! --MarkWoodbury (talk) 14:04, 14 September 2025 (UTC)

User:Mateusz Konieczny/notify uploaders/ - labeled for deletion

Is it OK that emptied pages in "User:Mateusz Konieczny/notify uploaders/..." have been labeled for deletion? In case of yes could you deal with it? --Chris2map (talk) 19:26, 19 January 2026 (UTC)

@Chris2map: done Mateusz Konieczny (talk) 09:21, 20 January 2026 (UTC)

Resolved: Mateusz Konieczny (talk) 17:16, 21 January 2026 (UTC)