Cartographic #OpenStreetMap wallpapers? Yes please!
Remote
Kevin Ratzel
@kevin@en.osm.town
mastodon 4.7.3OpenStreetMap contributor & Wikimedian
42 Followers
61 Following
33 Posts
Joined June 11, 2025
OpenStreetMap:
Some new updates to my little Suggest-A-Brand tool to help add to the Name Suggestion Index (NSI) for #OpenStreetMap
- Moved from GitHub/Pages to Codeberg/Pages: https://ga-kevin-codes.codeberg.page/Suggest-A-Brand/
- Search is now in the Wikidata field
- Adds field for Wikidata URL, location URL and count to be shared with NSI maintainers
You should give it a try it if a brand you know isn’t already on the NSI!
Getting my first e-bike tomorrow from a local shop, first bike I’ve had since a kid (I used to LOVE riding)! I’m very much looking forward to getting back on the saddle!
Updated Suggest-A-Brand to check for possible duplicates before submitting a pre-formed issue to the Name Suggestion Index. Notes to editors now shares this result too, preventing maintainers from having to check for duplicates manually.
Check it out! Now on Codeberg Pages, not Github!
Some more updates to the Pedestrian Working Group Visualizer:
- Curb icons now utilized the new “Pinhead" style by @waysidemapping@mastodon.social (https://pinhead.ink/)
- Improved readability with less transparency and a dark map by default.
- Icons now disappear at low zooms, allowing for higher-level QA without the visual clutter.
Visualizer: https://overpass-ultra.us/#query=url:https://raw.githubusercontent.com/GA-Kevin-Codes/PWG-Visualizer/refs/heads/main/pwg-guide.ultra&m=10.32/40.6823/-73.8914
GitHub (PRs welcome!): https://github.com/GA-Kevin-Codes/PWG-Visualizer
New improvements to the Pedestrian Working Group Visualizer thanks to @nickrsan@mapstodon.space!
- Simplified definitions of bronze-level crossings.
- Added a visual identifier for crossings that lack any tier level (previously bronze was displayed.)
Visualizer: https://overpass-ultra.us/#query=url:https://raw.githubusercontent.com/GA-Kevin-Codes/PWG-Visualizer/refs/heads/main/pwg-guide.ultra&m=10.32/40.6823/-73.8914
PR: https://github.com/GA-Kevin-Codes/PWG-Visualizer/pull/2
Replying to
@hector@mapstodon.space oh yes, it’s on the road map! I’ll have to figure out about Bing API keys and such!
Replying to
@simon no one is excusing an error (or calling it out), they’re saying it can be done kindly (in a mentor way.) See: https://en.osm.town/@watmildon/116313932959735165
Replying to
@simon issue is too many “experienced” OSM-ers act as managers not mentors or *gasp* equals.
Replying to
@FediFollows @kevin no doubt they’re doing wrong, but how else to know your opponent than to study them? Otherwise you get an echo chamber. Which if I follow only what you share is what I’ll get.
Replying to
@wikidata@wikis.world One of my favorite features is easily being able to add an image or pronunciation to Commons + Wikidata in one go. Making fields that typically take several steps and connections into a single, <10 second interaction.
Loving the new bike! Went up to the local zoo and recorded my way home!
RE: https://mementomori.social/@juergen_hubert/116429168342399754
Every single time there’s a new technology shift, you’ll get these posts. Man yells at clouds as the wheel of progress keeps turning.
RE: https://fosstodon.org/@ianthetechie/116436653288979708
Seriously impressive!!
Replying to
Yes, this is in addition to my other app, also in beta, for #Wikidata, Data2Go. That is much further along in the beta process and should be ready for release within the month I’d imagine. Both are hosted under the 2Go organization on Codeberg: https://codeberg.org/2Go
Replying to
@simon we can agree to disagree on that. Rude comments about volunteer work is also antithetical to OSM ideals IMO (not you, @vespucci_editor )
Replying to
@FediFollows @lawfare @GovTrack @heidilifeldman @jensorensen @z_everson @news certainly an interesting list but I do try and at least know what the other side is talking about. Any accounts from the right?
Replying to
@shisma@chaos.social @wikidata@wikis.world I’ve toyed with the idea of including a tip jar just to cover the cost of the account (maybe with a progress bar and cutoff when it hits $100) but also I am working on a mobile OSM editor (Map2Go - shh I haven’t talked about that yet!) so maybe when both are ready and stable I’ll do it :)
Replying to
@amapanda@en.osm.town if so, cisgender man and woman are allowed values: https://www.wikidata.org/wiki/Property_talk:P21
RE: https://flipboard.com/@thenewsdesk/news-i8koidj5z/-/a-T4b5RfXpRCykXQQc5gnd4A%3Aa%3A43591897-%2F0
I love how they have to put “not the price!” In the headline because there would be riots that would make the French blush if Costco raised that price 😂
The product CEO replaces the logistics/finance CEO, and I am hopeful
https://www.theverge.com/tech/915213/tim-cook-apple-ceo-stepping-down-john-ternus
Replying to
@shisma@chaos.social @wikidata@wikis.world not yet! To release on iOS on either TestFlight or the App Store you need a paid developer account and I have not bit the bullet yet on that $100/year cost!
You should be able to build it yourself on Xcode by cloning the repo if you’d like! This does require a Mac with Xcode installed.
Replying to
@shisma@chaos.social @wikidata@wikis.world it currently has features that let you upload to Commons, query OSM, and similar but that’s in service of adding to Wikidata right now. I’m open to more, just not there right now. What would you want to see?
Replying to
@amapanda@en.osm.town hey I’m a pretty big fan of Wikidata, and I’ll admit that I’m not the most up-to-date on all this, but how does WD model it vs what would be expected?
Replying to
@amapanda@en.osm.town meaning P21 as in https://www.wikidata.org/wiki/Q60964 or a different property?
Replying to
@amapanda@en.osm.town yes, because you’d need to add for woman (unspecific), cisgender woman, or transgender woman to find all women so it covers generic and specific values.
Kinda like how OSM has yes/no sometimes or a more specific value if you know it.
Replying to
@amapanda@en.osm.town I think I understand. I was seeing woman more as “we know she was a woman, unsure of anything more” whereas if we know she’s a black transgender woman we could specify that.
Absolutely is an issue if we’re defaulting to white cis instead of using it as a generic. I missed that part. I’ll bring it up in the telegram if I have time today :)
Replying to
@amapanda@en.osm.town Yeah, that user is absolutely wrong. I’d be happy to put something in the project chat explaining that, albeit years later it’s still relevant. Queries can easily reach for syntax of containing “woman” anywhere in the value with regex.
If you’d rather go the generic route then use P21 with start and end times (if known), that may be more flexible (especially if a subject has multiple changes in identity over the course of their life.) We’d just need to document that use-case somewhere
Replying to
@amapanda@en.osm.town The documentation for P21 would probably be your best bet. https://www.wikidata.org/wiki/Property_talk:P21 And right, if that's the case, P21 would have a start time of the subjects birth date. Only if the subject had a different P21 value would multiple + start/end time apply, capturing those complexities (hopefully) gracefully.
Replying to
@amapanda@en.osm.town right but the “allowed values” is what I would point to as man/woman being generic (not saying cis, just that we don’t know any more detail) and many options if you know more specific. I’m not going to force you to like Wikidata, but it is a huge open data project that could use your help if you wanted to contribute to the conversation.