hessen.social ist einer von vielen unabhängigen Mastodon-Servern, mit dem du dich im Fediverse beteiligen kannst.
hessen.social ist die Mastodongemeinschaft für alle Hessen:innen und alle, die sich Hessen verbunden fühlen

Serverstatistik:

1,6 Tsd.
aktive Profile

#mapstodon

6 Beiträge6 Beteiligte0 Beiträge heute

Experimenting with showing custom icons for stations. Inspired a bit from our highway shield rendered (derived from OpenStreetMap Americana)

gitlab.gnome.org/GNOME/gnome-m

It's making use of the "network:wikidata" OSM tag.

Currently rendering these icons in map view itself is not tested (this needs an extra addition to our planetiler generator for the vector tiles to be run in the next import).

#gnomemaps#gnome#Transit

watching @nakaner 's talk on completing #OpenStreetMap tags like surface=* I'm thinking about more goal directed ways.

Idea for surface=* tags

1. Use a routing engine such as osrm, remove all surface tags from ways, and compute many alternative routes between cities on that

2. For all alternative routes make sure that the osm ways all have surface tags on them

This approach gives us a heuristic for prioritizing completing the map where it matters most.

Dear #mapstodon community, we are moving! 📦💼

We have made the difficult decision to move our account to another fediverse instance, in order to better comply with our data protection regulations.
But we do love this map-loving community and we hope not to loose any contacts!

If you want to stay in touch and keep seeing our posts, follow us here: @heigit@mastodon.social

Done mapping all 40 #barangays of Luna, La Union, #Philippines 🇵🇭 in #OpenStreetMap, creating their #Wikidata items, and linking the two with each other.

A huge thanks to JR Dizon of the Luna Municipal Planning and Development Office for the boundary data. 🙏

Wanna play around? Here is the Overpass Turbo query: overpass-turbo.eu/s/21s0

And here is the Wikidata Query Service (WDQS) query: w.wiki/DfYz

Previously: en.osm.town/@seav/114092122864

I love #OpenStreetMap and I love #Mozilla but I do not understand what the strategy is here:

blog.mozilla.ai/map-features-i

It reads like looking for problems to apply AI to for "thought leadership" — and some ten years late at that.

OpenStreetMap has many players using machine learning; from big players to open source pipelines and models. It's not a technical problem to solve.

What are you doing Mozilla? Have you talked to anyone in the OpenStreetMap community?