Open-Planet turns OSM data into a playable world. Pick any place, the game downloads its extract from Geofabrik, adds Copernicus 30 m heights and ESA WorldCover land cover, and builds it: roads laid out from their tags and each country's design rules (lanes, widths, junctions, bridges, tunnels), buildings from their footprints and levels, forests, water and golf courses as mapped.

It's a nice way to see your own mapping: drive the streets you mapped. Where the map's thin, it shows.

Free and open source (AGPL-3.0), with OSM credited in the game and README.

https://github.com/inlighten420/open-planet

If GIF on this post doesn't work https://i.imgur.com/nvUx4Zc.mp4

Music: https://www.audionetwork.com/browse/m/track/after-the-fall_84169

Motion extraction tutorial: https://youtu.be/NSS6yAMZF78?t=226

As nobody mapped this part, I decided to waste my time only for map this house, supermarket and this bar.

I don’t know the name of this bar, but anyway, look for this link:

https://www.openstreetmap.org/#map=19/-22.293772/-42.518667&layers=N

Does anyone else wander around town updating business opening times like I do hahahaha

I'm #1 this week!

Hi all, one thing has always bugged me: OSM and Wikidata hold an incredible amount of geographic knowledge, but it mostly ends up in navigation apps and routing. There’s hardly anything that just lets you explore the world the way a good old atlas does, with rivers, lakes, mountain ranges and countries, their records and rankings.

So I built one: Open Earth Atlas (https://openearthatlas.org/en/), a free interactive globe built entirely on open data. No account needed.

Questionable values aren’t hidden. Instead of quietly patching odd values from other sources, the atlas shows them as they are, marks them with ⚠ and links to where they can be fixed. All open issues are collected on one public page, currently about 1,900: https://openearthatlas.org/en/improve-data

When something is fixed upstream, the next update picks it up and records it as “improved”, with the old and new value. The idea is that the atlas helps make the source data better, not just use it.

How OSM fits in:

• River courses come from OSM (ways and river relations), about 59,000 rivers.
• Lake outlines come from OSM wherever a matching water polygon has a wikidata tag. HydroLAKES only fills the gaps.
• Every river and lake page has a link that opens iD on the exact object.
• When an OSM lake outline differs a lot from the satellite-derived one (typically reservoirs mapped as river sections), it shows up on the improve-data list instead of the atlas silently picking one.

Example: Lake Constance, https://openearthatlas.org/en/lakes/europe/lake-constance

To be upfront: I vibe-coded this over the past few weeks, and with 250,000 pages built from messy real-world data, I’m sure there are plenty of bugs and odd results I haven’t found yet. This is very much a start, and I plan to keep working on it for a long time.

So I’d really like to hear what you think of the idea in general. Is this useful to you as a mapper? What’s missing, what feels off? And if anything about how it uses OSM data clashes with community conventions (e.g. matching lakes via the wikidata tag), I’d like to know that too.

Hi! We’re building WikiPowder, a free ski resort guide with interactive piste maps powered by OpenStreetMap (OSM) data via OpenSkiMap and OpenSkiData.

We wanted to share a few things we’ve learned along the way and, of course, express our gratitude to the OSM community for making this project possible. We all come from tech backgrounds, so about 90% of it was vibe-coded. However, that also brought some challenges we had to overcome along the way, which ultimately helped us deliver what we think is a solid foundation.

Working with ski data at scale has surfaced some interesting challenges and insights that might be useful to fellow OSM contributors:

1. Commercial ski domains rarely map to OSM ski areas on a 1:1 basis. Large ski domains are often split across several OSM ski areas, sometimes even across national borders.
2. Resort names aren’t always unique. The same name can refer to resorts in different countries or even on different continents, making naive name matching risky. Automating this process is complicated, so manual verification was required in many cases.
3. Official resort coordinates can be misleading. They often point to the village centre, town hall, or tourist office rather than the actual ski slopes, so they don’t always align with OSM geometries.
4. Published piste kilometres vary significantly by source. Resort operators, third-party guides, and measurements based on mapped geometry can all report different figures because they use different methods. This is a nightmare. We can’t provide accurate or 100% reliable kilometer coverage.
5. A single named piste may consist of multiple OSM segments or sectors. This makes matching and aggregating piste data more complex than it might seem at first. We found a way to structure the data, but representing it is still complicated.

We’re still working through some known issues, but we’ve now reached a stable enough version to start rolling it out (just in time for the next season!).

That’s it for now! We’d love to hear your feedback, and we hope you find the project interesting.

Thanks to everyone in the OSM community for making projects like this possible!

Update:

Folks! We’ve been trying to respond to your feedback, but it looks like all the comments have been removed or moderated, perhaps because the user account is brand new.

Just wanted to let you know that we really appreciate your feedback! 🙏 One of the first decisions we've done is pivot towards a more community-driven approach, allowing people to edit and improve existing OSM slopes. The data is already good, but it’s not perfect, and we want to help the OpenStreetMap community make it even better. The idea of setting a general map with all the slopes is also quite interesting.

We’re also considering developing an open-source library to make it easier to manage multiple OSM segments. That’s currently our main focus, although we’re also fixing bugs along the way.

Thanks again for taking the time to share your thoughts and help us improve!

I make Runplanner, a free running route planner built on OSM, and used its loop generator to draw 40 random 5 km running loops in each of 25 cities, then counted the mapped traffic lights each loop crosses.

Two things OSM people may find interesting:

- Tagging style matters. Counting only highway=traffic_signals missed a lot: adding crossing=traffic_signals, crossing:signals=yes and UK crossing_ref (pelican/puffin/toucan/pegasus) raised the total by 22%, and doubled Birmingham. Lights within 20 m are merged, so a junction mapped both ways counts once.

- Jakarta and Bali had to be left out: their centres have about 2 mapped junction lights per km², against about 43 for the middle city. Probably a mapping gap more than a lack of lights.

Full method, limits and a CSV for all 25 cities: https://runplannerapp.com/blog/traffic-lights-per-km. © OpenStreetMap contributors, ODbL.

Boys my run query in quick OSM not working please help

Working on an app that permanently stores places an location data. But we have run into compliance issues with Google. Which provider offers reliable POI search with permanent storage and commercial redistribution rights? Can its place data be displayed on MapTiler maps and used offline? Does it reliably find places? What are the storage, attribution, and per-query costs?

I'm looking for some advice on how best to map a new type of transport infrastructure being introduced across the West Midlands, UK, called Local Travel Points (LTPs), which are essentially small neighbourhood mobility hubs. (see image below)

TfWM (Transport for West Midlands- the county council department responsible for public transport) is rolling these out to encourage sustainable, shared transport. Unlike traditional transport interchanges, they aren't necessarily located at existing railway stations or bus stations. Instead, they're often standalone facilities in residential areas, parks or town centres, although they may be within a short walk (5 mins) of existing public transport.

Their facilities vary between locations, but typically include a combination of:

• Cycle hire stations (Lime) and secure bicycle storage
• Bicycle repair facilities
• Seating, shelters and landscaped public spaces
• Local maps, wayfinding signage and digital information terminals
• Improved lighting
• Car club / car-sharing facilities (Enterprise)
• EV charging points
• Public artwork and other community features

Not every hub has all these facilities, and their layouts and sizes vary considerably.

I've already mapped one of these hubs in Halesowen, which you can see in this changeset.

I've mapped the individual facilities using their respective tags and attempted to group them together using a relation to represent the overall Local Travel Point.

However, I'm not entirely sure whether this is the most appropriate approach, and I'd really appreciate some feedback on how I've mapped it, particularly whether using a relation to combine these features is appropriate, and whether I've structured and tagged that relation correctly.

Generally, I'm looking for feedback regarding:

1. Tagging: Is there an established or emerging tagging convention for these types of mobility hubs? Would a site relation, an area, or a single nodes be most appropriate?
2. International examples: Have similar neighbourhood mobility hubs been mapped elsewhere, particularly in other countries? I'd be interested in seeing examples of how others approach them.
3. Grouping facilities: Where a hub contains several separately mapped features (cycle rental, car sharing, benches, etc.), is there a sensible way of associating them with the overall hub without duplicating information?
4. Distinguishing them from transport interchanges: Given that these aren't necessarily connected to a railway station or bus stop, how should they be distinguished from more conventional public transport facilities?

For reference, the link below explains the concept and shows examples of the design and layout of these hubs:

CoMoUK – Mobility Hub Development in the UK (PDF, October 2024)

I'd really appreciate any (good or bad) feedback on my existing mapping before adding any more of the hubs, suggestions for alternative approaches, or links to similar hubs already mapped elsewhere in the world.

I'm keen to establish a consistent approach as more of these are installed across the region, ideally following existing OSM conventions rather than introducing unnecessary new tagging.

Thanks!

I want a way that is easiest from either the street or remotely (somehow). I live in a non-touristy city in South Korea, so OSM support sucks, same with Mapillary streetview, it's very rare (Even Seoul has a pretty big lack of data on OSM). I am adding a ton of buildings around my city Pyeongtaek, and I want to add addresses too.

I need to find the most efficient driving route between two points on US Roads and also show the distance.

These routes will either be in one or two counties and I need to show the distance traveled in each county if the route crosses the county line.

Is there a tool utilizing OSM that would be able to show/calculate this?

Looking for a simple, free tool to draw lines, shapes & legend over a map/image (for site maps & work instructions)

I’m looking for a simple and free tool to create clean site maps/work instruction maps.

​Right now, I take a map or satellite screenshot and need to add basic elements like:

​Lines (e.g., access routes, driving paths)

​Shapes/polygons (e.g., work zones, storage areas, site boundaries)

​Text boxes and a clear legend

​I’ve tried tools like Google My Maps and basic drawing programs (like MS Paint), but I’m looking for something a bit more user-friendly and polished that automatically gives a neat, professional look without a steep learning curve (so no complex software like full QGIS if possible).

​It would be ideal if I can easily export the final result as an image (JPG/PNG) or PDF with a clear legend attached.

​Does anyone have recommendations for web apps, simple mapping tools, or software that work well for this?

​Thanks in advance!

I'm currently in this region of Brazil, and I'm contributing to the map as I travel.

I use OsmAnd app on my phone and, after the updates, I'm getting this weird sqaures on the map where I contributed...

Am I doing something wrong?

https://www.openstreetmap.org/#map=18/-22.292730/-42.516038&layers=N

can i look at street view in osm? If it is possible, how can i look?

(i use translator)

I couldn't find any explanation for these lines (the ones with arrows & squares) in the legend page.

Hi everyone!

I'd like to share a small side project I've been building: Maparium.

The idea is simple: what if you could instantly explore specific types of places and infrastructure across the entire world on one interactive map?

Maparium lets you display OpenStreetMap features globally like wind turbines, power plants, castles, spaceports and more. You can switch between predefined layers and explore patterns that are difficult to spot when looking at individual locations.

I'm using MapLibre GL JS, a Protomaps basemap and custom MBTiles generated from OpenStreetMap data. A big focus has been making the experience fast and lightweight, even when displaying features on a global scale.

Try it here: https://maparium.pl
Source code: https://github.com/matymm347/maparium

As nobody mapped this football field located in Catarcione neighbourhood, I decided to take my time to map this football field.

Including, I added two schools, more houses, two market, two trees, and two woods.

If you want to see: https://www.openstreetmap.org/#map=19/-22.290940/-42.513716&layers=N