User talk:Mateusz Konieczny

From OpenStreetMap Wiki
Jump to navigation Jump to search

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 Mashhad History 2008-2011.gif 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.


A place to drop of books does imply a place to pickup books…

That would be an amenity = library as stated in the proposal. If anything your opposing vote might indicate that more tagging options might be needed for self service pickup options that can be on or offsite of the library.

I would however state that 99% of the time the pickup location for books would be the library itself and pre-Covid 99% of all locations that offered drop off options still required going to the library itself to pickup and drop off books. Hence why this has been the focus for of the tagging proposal.

I respect your vote and thank you for your feedback. I just wanted to offer this perspective and see if I’m misunderstanding or understanding your objection so that if I need to revisit this for future votes I know I’m addressing all concerns.

Thanks, JPinAR JPinAR (talk) 11:36, 26 June 2022 (UTC)

@JPinAR: "That would be an amenity = library as stated in the proposal" - where it is stated? "99% of all locations that offered drop off options still required going to the library itself" - I agree, but some places have such cases and leaving such obvious gaps almost always leads to misuse of approved tags Mateusz Konieczny (talk) 11:38, 26 June 2022 (UTC)

Thanks I will consider a follow-up pickup location tag especially since now pickup via kiosk has become a thing. Thank you for the constructive feedback and community contribution. JPinAR (talk) 13:03, 26 June 2022 (UTC)

@JPinAR: That would be really helpful! It would be nice to avoid repeat of say historic=wayside_shrine that is used for all shrines, not only wayside ones. I managed to push man_made=cross forward but it was likely too late to solve historic=wayside_cross from being used for all crosses Mateusz Konieczny (talk) 13:05, 26 June 2022 (UTC)

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)

File:Mixed fence.png

https://wiki.openstreetmap.org/wiki/File:Mixed_fence.png Nie pamiętam, skąd wytrzasnąłem to zdjęcie, ale Google Photos nie pamięta, żebym je zrobił, poza tym pewnie byłby to JPEG. Najprawdopodobniej wyciąłem clipping toolem skądś. Pewnie będzie bezpieczniej wywalić je i zastąpić innym.

Saddle holder removement

Hi Mateusz, i cannot understand the change https://wiki.openstreetmap.org/w/index.php?title=Template:Bicycle_parking&diff=2387687&oldid=2422493 where you also remove the saddle_holder. The comment for the change does not explain it. Can you please explain why it got removed? --Strubbl (talk) 10:32, 21 October 2022 (UTC)

Oh i see, it got re-added again with https://wiki.openstreetmap.org/w/index.php?title=Template:Bicycle_parking&diff=2423771&oldid=2389381 This version history is so confusing. Do you know how can this happen? --Strubbl (talk) 10:34, 21 October 2022 (UTC)
@Strubbl: no idea - maybe I edited old page version for some bad reason? Looks like I made some mistake there Mateusz Konieczny (talk) 11:25, 21 October 2022 (UTC)
I think it is more a version history problem than a user problem, because in my change https://wiki.openstreetmap.org/w/index.php?title=Template:Bicycle_parking&diff=prev&oldid=2422493 i only added the saddle_holder value and did not change any other lines. But they occur as changed by me, which is not true. Maybe the version history of that template page is broken. --Strubbl (talk) 11:53, 21 October 2022 (UTC)
Resolved: Mateusz Konieczny (talk) 16:12, 10 June 2025 (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)

Your revert on Russian–Ukrainian war

On Russian–Ukrainian war I changed "territory of Ukraine" to "Ukrainian controlled territory" and you reverted that. Your change summary shows "have you actually discussed this change with anyone? if yes, please link discussion in edit description". No, I have not. Nobody of the prior Editors did so. And I also don't need to. There is no rule that changes need to be discussed beforehand. This is just how Wikies work. Now you did not give a reason for the revert. Why do you think my contribution was harmful and needed an immediate revert instead of discussing conflicting opinions on the talk page? I think my edit was constructive and to the benefit of the OSM Community and the Ukrainians. The relatively new User:Bezdna initially added the text (User:Velikodsky just translated it) and I did not find any community reference for the rules given. Beforehand I read the talk page and after your revert Russian–Ukrainian war @ OSM community, but I found no evidence that a majority of the Ukrainian community backs what is written on the Wikipage. Please abstain from further reverts of such edits unless there are clear signs of vandalism, disruptive edits, or unexplained content removal. See wikipedia:Help:Reverting! --phobie m d 07:12, 10 June 2025 (UTC)

@Phobie: Previous edits there were in fact discussed. You even mention this discussion, but to make it easier I linked it in the page. Maybe request stated there is in fact outdated, maybe it is position of minority of mappers. Maybe page should be edited to make clear that it is request from part of community not official policy (I am NOT encouraging you to do so). Maybe you can create poll at Ukrainian subforum or global one (I am NOT encouraging you to do so) But editing request made by others to change its phrasing and meaning and introduce internal contradictions is at best dubious. And if we are linking Wikipedia pages then I am going to link https://en.wikipedia.org/wiki/Wikipedia:BOLD,_revert,_discuss_cycle Mateusz Konieczny (talk) 08:16, 10 June 2025 (UTC)
No, previous edits where in fact not discussed. First the Wikipage had been created, without a link to some consensus. Second the Wikipage had been advertised on the forum. Third a critical discussion started on the talk page. Fourth a critical discussion started in the community forum. You just added the forum-advertisement and not the critical-discussion to the Wikipage. Talking about dubious: There is still no reference to a consensus of the Ukrainian OSM community and the request needs shaping/editing. If something should never be edited "Wiki" is the wrong platform. Talking about BRD: I was bold, you reverted, fine but you missed the "be specific about your reasons in the edit summary". Not having discussed something beforehand is NOT a reason. Now I prefixed the appeal with a disclaimer. This should help people stumbling over that page. --phobie m d 10:28, 10 June 2025 (UTC)
@Phobie: I see no obvious version with current page version, though changing meaning of appeal made by someone else without discussing it with them still seems dubious to me (where such appeal should be posted, how much context should be given and how it should be presented is a separate can of worms) Mateusz Konieczny (talk) 16:11, 10 June 2025 (UTC)
It was meant as clarification. It is currently unclear what "territory of Ukraine" means, but "currently controlled" or "including occupied and annexed" would be unambiguous. My new edit lists the problems of the appeal without editing it, but just to pleases you personally. I still think the appeal itself should be adjusted, preferable by a consensus. Discussions have shown that there is no consensus and therefore I think it is good if individuals are bold and change the appeal to be less ambiguous. A discussion on the talk page would be more productive than a revert in this case. --phobie m d 07:27, 11 June 2025 (UTC)

= Incorrect item description

1) Found problem with item description, cause of discrepancy: Incorrect_item_description. The eng. description of this item was erroneously created by Oivo357 (see: first description). There are many such erroneous descriptions of him on OSM, then nonsense, errors and untruths creep in. Do you understand now? --HaPe-CZ (talk) 07:49, 11 June 2025 (UTC)
2) Moreover, Oivo357 made a revert without justification in the discussion. That is, he violated your request for an explanation. --HaPe-CZ (talk) 07:54, 11 June 2025 (UTC)
@HaPe-CZ: "Moreover, Oivo357 made a revert without justification in the discussion. That is, he violated your request for an explanation" can you link it? Is it different one that one they got blocked for already (see https://wiki.openstreetmap.org/w/index.php?title=Special:Log/block&page=User%3AOivo357 ) Mateusz Konieczny (talk) 08:43, 11 June 2025 (UTC)
The answer has been added: https://wiki.openstreetmap.org/wiki/Wiki:Requests_for_administrator_attention#Edit_war_User%3AOivo357_and_User%3AHaPe-CZ.
Now it is possible to solve Item Q2082 ... https://wiki.openstreetmap.org/wiki/Item_talk:Q2082. --HaPe-CZ (talk) 09:37, 11 June 2025 (UTC)
Resolved: Mateusz Konieczny (talk) 13:15, 13 June 2025 (UTC)

Error in description of Labels/Items in iD editor

In the Czech version of the iD editor there is one text label description for two Items. Concretely Item amenity=fuel (Q4716) and Item man_made=fuel_pump (Q16807). In the iD editor and in the Czech translation of the label, both items have the same description.
Item Q4716 has the correct description amenity=fuel and label in iD editor: “Čerpací stanice”, that's Ok.
Item Q16807 has the correct description man_made=fuel_pump but the label in the iD editor, “Čerpací stanice”, is wrong (same as the previous one).
Item Q16807 should have the (correct) label “Čerpací stojan” in the iD editor.
Who translates these labels or where can this error be corrected? Thank you for your help. HaPe-CZ (talk)

This is not a wiki article or wiki data item issue. This needs to be done in the iD editor translation. --MalgiK (talk) 07:31, 13 June 2025 (UTC)
It seems the provided link (https://www.transifex.com/openstreetmap/id-editor) on iD editor translation doesn't work, maybe try instead this: https://explore.transifex.com/openstreetmap/id-editor --MalgiK (talk) 07:47, 13 June 2025 (UTC)


Resolved: https://github.com/openstreetmap/iD/blob/develop/CONTRIBUTING.md#translating Mateusz Konieczny (talk) 10:09, 13 June 2025 (UTC)

File:Area affected by landuse imports.png

File:Area affected by landuse imports.png - unknown background image, uploaded by You. Please fix or delete. Thanks. Something B (talk) 22:40, 13 June 2025 (UTC)

https://wiki.openstreetmap.org/w/index.php?title=File:Area_affected_by_landuse_imports.png&diff=prev&oldid=2866052 Mateusz Konieczny (talk) 23:50, 13 June 2025 (UTC)
Resolved: Mateusz Konieczny (talk) 23:50, 13 June 2025 (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

Retrieved from "https://wiki.openstreetmap.org/w/index.php?title=User_talk:Mateusz_Konieczny&oldid=2866841"