|
Top-level
 For the @sotm in Firenze I went all-out with the remote participation part. One thing I did was a Telegram bot, where people from anywhere could introduce themselves. The idea was to put a face to hundreds of names on online channels. Because once you have a face and a voice attaches to words, it's impossible not to feel a proper conversation going when you type. Not many people contributed, but still, was fun. The bot was disabled after the conference ended of course. 13 comments
For a very long time the leading repository on my github was "leaflet-grayscale" with a hundred stars. I love @leaflet and made too many plugins for it. This one was quite simple — but I guess useful enough. It just makes the map grayscale. There are too few layers fit for a visualization background. Sometimes removing colors (and labels if possible) is good enough.  Back to OSM, here's one you'd ban if you could. Sisyphus make a person's mapping work as pointless as rolling a stone up a mountain. It plain reverts every changeset a person uploads to OpenStreetMap. We used it in Maps.Me for reverting edits of our QA team. Not ideal, which Frederik noted, but it works, the map is clean, no hassle with moving data to the sandbox. Uses simple_revert as a library, of course. That library is underrated. People usually need three things from maps: tiles, geocoding, and routing. Three things too mundane to work on. For Maps.Me Changes Monitoring, I filtered edits by countries. For that I wrote a simple reverse geocoder: QueryAt. It returns a country, a region, and a populated place for a given location. 3 GB database for the entire world, no configuration or query parameters. Won't recommend using it now though: 8 years later, you could do better.   |
Gregory's Server
I feel like I've invented another job for myself, posting those tweets regularly. Let's do a few small things now.
Like, I love doing efficient focused tooling. GeoJSON Point Editor, while not entirely related to OSM, is exactly that. Faced with making a GeoJSON for ~100 point amenities, geojson.io was frustrating to use.
So I made this. Double click for a new point, type some words for properties (in a already focused field!), filter by keys, download the result.
https://zverik.github.io/point_ed/
I feel like I've invented another job for myself, posting those tweets regularly. Let's do a few small things now.
Like, I love doing efficient focused tooling. GeoJSON Point Editor, while not entirely related to OSM, is exactly that. Faced with making a GeoJSON for ~100 point amenities, geojson.io was frustrating to use.