Contributing to Open Street Map has given me a ton of satisfaction. Knowing that my somewhat minor efforts to correct one address, add one feature, correct one trail will propagate to so many different places and help other people not get lost, find something new, or just be able to navigate more safely in the world makes me feel like I am leaving the world a better place more than a decade of working at FANG ever did.
THIS. My comment is somewhat tangential but I thought still relevant. I used to work for huge financial investment company with over a trillion dollars of assets for over 10 years. I never thought I was making positive difference in people's lives. However, my job offered me so many opportunities to volunteer and I would jump on every single one of those, and that made working there totally worthwhile. I still work for another huge company these days, which offers similar opportunities to make a difference in the community and that is what keeps me going here too.
There is something to be said about building tools out of kindness and not for greed. Thank you for your contributions to OSM and Thank you OSM developers too - big fan and user!
True, I use mapcomplete or streetcomplete to kill time when traveling. I use public transport a lot. I've racked up thousands of minor edits, addi g opening hours, accesability info and what not to the map. It's been very satifactory.
I work in public service and I've grotten so many people on board that the map in my region is pretty darned good.
I absolutely love OpenStreetMap. Back when I first started building (legal) mountain bike trails I realized that without a map they aren't the most useful. OSM gave me the system in which to document them, and then from there I was able to reuse the data to make print maps and eventually my current project: https://trailmaps.app
If you want a fun and easy way to contribute to OSM I recommend StreetComplete. You get a bunch of game-like quest icons for things like "what is the surface of this path?", and "does this road have a cycle path?", then you walk around and fill them in.
Very satisfying and feels like you're doing something actually useful. Also nudges you to visit parts of your neighborhood you might never have been to before.
Gamifying the map definitely helps to pull in contributors. StreetComplete got me editing more than anything else. I went a bit sideways with it: I used OSM data to build a territory game for cyclists, where you claim roads by riding them.
It's heavily processed OSM data with PostGIS. The fun part was figuring out how to decide what counts as a claimable road in the first place.
I used OpenStreetMaps to create a map with a theme that fits the website theme. There were no other free options that I could find to accomplish this goal. Moreover, the map works on just about every browser under the sun. Great work by their team.
Your attribution is hidden by default and it looks like you are doing it on purpose by running `attrib.classList.remove( 'maplibregl-compact-show' );`.
For the panel discussion "Why do you contribute to OSM?" one of the questions sought to be understood is "What stops or demotivates you to contribute (more) to OSM?".[1]
My response would be the incorrect application amongst the OSM community of sweat-of-the-brow doctrine in copyright law within jurisdictions it very clearly doesn't apply.[2][3]
I hazard a guess some of this incorrect application comes from large companies becoming involved in OSM, and they've signed unrelated enterprise agreements with the likes of Google, or whoever. Within those agreements there may be private agreements that the companies cannot redistribute data of Google (or whoever) without explicit permission. The companies contributing to OSM don't want to have to navigate this problem when they contribute to OSM and would prefer OSM incorrectly applies sweat-of-the-brow doctrine to exclude any non-copyrightable but otherwise "problematic" data (to themselves only) that the likes of Google could possibly argue were obtained through their enterprise agreement.
I also hazard a guess there are numerous OSM community members that strongly hold copy-left views of their contributions. They want/need the sweat-of-the-brow doctrine to be able to control consumers of OSM data (not necessarily just rendered tile maps) as in the example of [5]. In this example, someone complains that a third party brand extracted 100k+ water tap coordinates from OSM and added them to Google Maps.
I also hazard a guess there are some small number of vocal OSM community members that hate "armchair mapping", or want to keep new mappers out of areas they're trying to control, and raising licensing disputes can be a convenient way to encourage such mappers to stay away. If the mapper disputes the claim, it'll probably just fall back to "None of are lawyers so we err on the side of extreme caution". And hence tragedy of the anticommons tends to result.
Some ridiculous examples I've come across:
- Franchise website lists store locations with Google Maps Place IDs only. OSM community members get in a panic because someone opened up every link to determine the address or coordinates of each store, then add store locations to OSM. Somehow they fear a copyright infringement has occurred, even though case law in most major jurisdictions very clearly demonstrates factual data (such as address of a store or coordinates of a store) is not copyrightable.
- Government department publishes some dataset, let's say a shapefile of points of park benches, under a CC-BY licence. They then host public competitions and conferences encouraging people to use the data and create apps and websites based on it. OSM community members panic because the government department hasn't also signed an OSM-specific form or otherwise provided approval that explicitly permits OSM's website to show attribution as just "OSM contributors" with a link to a page that lists the government department amongst 100's of others. As opposed to the bottom of openstreetmap.org having a list of 100,000+ individual contributors. No one stopped to question whether a shapefile of points of park benches could even be copyrightable in the first place. And the government department never responds to a request to clarify how they should be attributed because no one thought of that question when using the CC-BY license.
- Someone on the ground walks past a restaurant with opening hours published on the window and enters them into OSM. Or they visit the restaurant's website to learn what their opening hours are, and enters them into OSM. Oh no! Has there been a copyright infringement?
As far as I'm aware, [4] is probably the most official OSM position resolving some of these sweat-of-the-brow problems. However, other OSM Foundation and Wiki pages are in conflict and would typically scare many community members away from contributing per the examples provided above (e.g. contain strong vague statements such as (paraphrased) "Do not copy features from other maps to OSM"). Additionally, the example of [5] indicates OSM chasing up consumers of OSM data for supposed lack of attribution, and seemingly relying on non-existent (in many jurisdictions) sweat-of-the-brow doctrine to do so.
Copyright law is severley broken with the invention of AI so I guess we'll have to wait and see how jurisdictions change their copyright laws for AI. And then by extension, maybe some of these sweat-of-the-brow ambiguities for mapping/databases may finally be better resolved.
Weird little quirk I've recently encountered, somewhat related to OSM: the `mkgmap` tool used to convert OSM data to Garmin map files display Chinese pronunciation as English names next to POI names in Japanese, due to 1) Japanese OSM maps have a lot of entries written in Japanese without indication of language, 2) no one is doing anything about it, due to Wikipedia style community nuances or something, and 3) the tool have no "--assume-language=$LANG" style of options(plus Japanese script->pronunciation mapping isn't even remotely bijective).
e.g. There's a bicycle parking next to the parkside exit at Ueno station, "上野駅公園口自転車駐車場". This is:
meaning: Ueno station park entrance bicycle parking ground in English,
read IRL: ue no eki kouen guchi jitensha chusha jou in Japanese, but written
on the map: shang ye yi gong yuan kou zi zhuan che zhu che chang as Chinese(in Pinyin but I don't know how to type it).
...I would imagine that utility of that is limited for non-Japanese users. Makes me wonder what are the reasons why master OSM data hadn't had missing pronunciations autogenerated or mkgmap tool given an auto selected language flag, but I'm not intending to be OSMian nor am I wanting to be the one to define national borders for bunch of nation states, so there's that...
I have a hard time making sense of your post. What do you mean with 'Japanese OSM maps'? There is just one OpenStreetMap, which includes Japan.
On OpenStreetMap all entities which are named have at the very least the tag `name`. There is no need to specify which language that name is in, because this is geographically determined. For the whole of Japan, `name`-tags are considered to be in Japanese.
This specific bicycle parking has no other names but that one `name` tag, which is the Japanese 上野駅公園口自転車駐車場:
This is totally normal. Most named entities only have a local name. A random bicycle parking is not likely to have a name in any other language but the local one. For things which actually have an exonym (like countries and larger cities), you will find additional namespaced language tags like `name:ja` and `name:en`, but a bicycle parking in Japan usually doesn't have an English name (although you can translate the Japanese name).
As for why you are seeing Chinese, that has nothing to do with OpenStreetMap. Some other tool in your chain is doing that (mkgmap?).
The naming policy is generally quite sensible, although individual mappers sometimes do weird things (OpenStreetMap is sort of an anarchistic collective). As long as most English speaking people around Lake Ontario and the Gulf of Mexico use those names, the `name` and `name:en` tags will reflect that. Usually the way media like quality newspapers use such a name is a good bellwether, and the normal name stays as long as it is evidently in common use.
If in the future most Americans do end up saying 'Lake America', `name` could follow that too, and Lake Ontario would end up in `alt_name`.
Or perhaps Americans from the White House to the New York Times to the school curriculum will call it Lake America, but Canadians will stick with Lake Ontario. In that case the top-level local language `name` might end up as 'Lake America/Ontario' (combining all local languages and variants) and `name:en` (English in general, so America would be a minority there) and `name:en-CA` would say Lake Ontario, and `name:en-US` would say Lake America. Time will tell. OpenStreetMap adjusts accordingly.
For the official name there is simply a different tag (`official_name`, or in this case `official_name:en-US` because the lake borders more than one country). Having that available makes it possible to search for it by that name.
The President of the United Stated doesn’t actually have the authority to tell anyone besides the executive branch what to name geographic places. So the order only forces official US government maps created by USGS and the like to be updated. Other maps can choose to update if they want to.
Open Street Map tends to reserve the “name” tag for what things are commonly called by the local community. It appears that for the Lake Ontario and The Gulf of Mexico they’ve added an “official_name:US” tag to capture the names in the executive orders.
It's up to the renderer what to display. OSM tags data according to global consensus, they use Gulf of Mexico for 'name'. There is an attribute for 'official_name:en-US' that returns Gulf of America. Same approach for other disputed names/places.
"Few if any renderers consume official_name=* or any of its subkeys; in practice, the purpose of this key is for geocoders to find the feature when a user searches for the official name."
Well, when you visit it https://www.openstreetmap.org/#map=7/23.765/-87.100 there's no naming of that area at all. At least when looked at from a US IP. And when you search "Gulf of America" it returns "Gulf of Mexico". So take from that what you will.
Also https://www.openstreetmap.org/#map=8/43.622/-78.852 shows "Lake Ontario". But it does carry the tag "official_name:en-US": "Lake America", so search will find Lake America and a mapping app could decide to show the official name
Though generally official names are the names nobody uses. For example the country labeled "France" also has the attribute "official_name:en": "French Republic"
One of its purposes is to annoy serious adults. If legislation is created, I would estimate it would extend its life somewhere between 3 weeks and infinity.
It’s interesting how the “preserve traditional historical names - don’t change the names on things for political reasons” role flipped to the left when that particular person started renaming things. In this case especially - a body of water that is between two countries has no “correct” namesake. It merely has a “traditional” name justified by “that’s just always what we’ve called it.” Tradition suddenly became very important to the American left wing when that rename happened.
good to know both parties apparently feel that “petty renaming of things” is a good use of time for the government. So we’ll just start every change in party control with a raft of renames to thumb our noses at “The Former Guy.” Productive.
So the clever ones should just leave the damage the stupid one did and just wait for their term to run out so the stupid ones can cause more damage, the clever ones can ignore and repeat?
There is something to be said about building tools out of kindness and not for greed. Thank you for your contributions to OSM and Thank you OSM developers too - big fan and user!
I work in public service and I've grotten so many people on board that the map in my region is pretty darned good.
Very satisfying and feels like you're doing something actually useful. Also nudges you to visit parts of your neighborhood you might never have been to before.
https://remap.earth
I used OpenStreetMaps to create a map with a theme that fits the website theme. There were no other free options that I could find to accomplish this goal. Moreover, the map works on just about every browser under the sun. Great work by their team.
Your attribution is hidden by default and it looks like you are doing it on purpose by running `attrib.classList.remove( 'maplibregl-compact-show' );`.
My response would be the incorrect application amongst the OSM community of sweat-of-the-brow doctrine in copyright law within jurisdictions it very clearly doesn't apply.[2][3]
I hazard a guess some of this incorrect application comes from large companies becoming involved in OSM, and they've signed unrelated enterprise agreements with the likes of Google, or whoever. Within those agreements there may be private agreements that the companies cannot redistribute data of Google (or whoever) without explicit permission. The companies contributing to OSM don't want to have to navigate this problem when they contribute to OSM and would prefer OSM incorrectly applies sweat-of-the-brow doctrine to exclude any non-copyrightable but otherwise "problematic" data (to themselves only) that the likes of Google could possibly argue were obtained through their enterprise agreement.
I also hazard a guess there are numerous OSM community members that strongly hold copy-left views of their contributions. They want/need the sweat-of-the-brow doctrine to be able to control consumers of OSM data (not necessarily just rendered tile maps) as in the example of [5]. In this example, someone complains that a third party brand extracted 100k+ water tap coordinates from OSM and added them to Google Maps.
I also hazard a guess there are some small number of vocal OSM community members that hate "armchair mapping", or want to keep new mappers out of areas they're trying to control, and raising licensing disputes can be a convenient way to encourage such mappers to stay away. If the mapper disputes the claim, it'll probably just fall back to "None of are lawyers so we err on the side of extreme caution". And hence tragedy of the anticommons tends to result.
Some ridiculous examples I've come across:
- Franchise website lists store locations with Google Maps Place IDs only. OSM community members get in a panic because someone opened up every link to determine the address or coordinates of each store, then add store locations to OSM. Somehow they fear a copyright infringement has occurred, even though case law in most major jurisdictions very clearly demonstrates factual data (such as address of a store or coordinates of a store) is not copyrightable.
- Government department publishes some dataset, let's say a shapefile of points of park benches, under a CC-BY licence. They then host public competitions and conferences encouraging people to use the data and create apps and websites based on it. OSM community members panic because the government department hasn't also signed an OSM-specific form or otherwise provided approval that explicitly permits OSM's website to show attribution as just "OSM contributors" with a link to a page that lists the government department amongst 100's of others. As opposed to the bottom of openstreetmap.org having a list of 100,000+ individual contributors. No one stopped to question whether a shapefile of points of park benches could even be copyrightable in the first place. And the government department never responds to a request to clarify how they should be attributed because no one thought of that question when using the CC-BY license.
- Someone on the ground walks past a restaurant with opening hours published on the window and enters them into OSM. Or they visit the restaurant's website to learn what their opening hours are, and enters them into OSM. Oh no! Has there been a copyright infringement?
As far as I'm aware, [4] is probably the most official OSM position resolving some of these sweat-of-the-brow problems. However, other OSM Foundation and Wiki pages are in conflict and would typically scare many community members away from contributing per the examples provided above (e.g. contain strong vague statements such as (paraphrased) "Do not copy features from other maps to OSM"). Additionally, the example of [5] indicates OSM chasing up consumers of OSM data for supposed lack of attribution, and seemingly relying on non-existent (in many jurisdictions) sweat-of-the-brow doctrine to do so.
Copyright law is severley broken with the invention of AI so I guess we'll have to wait and see how jurisdictions change their copyright laws for AI. And then by extension, maybe some of these sweat-of-the-brow ambiguities for mapping/databases may finally be better resolved.
[1] https://2026.stateofthemap.org/sessions/GXXCFE/
[2] https://en.wikipedia.org/wiki/Sweat_of_the_brow
[3] https://en.wikipedia.org/wiki/Threshold_of_originality
[4] https://osmfoundation.org/wiki/Licensing_Working_Group/Minut...
[5] https://osmfoundation.org/wiki/Licensing_Working_Group/Minut...
e.g. There's a bicycle parking next to the parkside exit at Ueno station, "上野駅公園口自転車駐車場". This is:
...I would imagine that utility of that is limited for non-Japanese users. Makes me wonder what are the reasons why master OSM data hadn't had missing pronunciations autogenerated or mkgmap tool given an auto selected language flag, but I'm not intending to be OSMian nor am I wanting to be the one to define national borders for bunch of nation states, so there's that...On OpenStreetMap all entities which are named have at the very least the tag `name`. There is no need to specify which language that name is in, because this is geographically determined. For the whole of Japan, `name`-tags are considered to be in Japanese.
This specific bicycle parking has no other names but that one `name` tag, which is the Japanese 上野駅公園口自転車駐車場:
https://www.openstreetmap.org/node/3395310504
This is totally normal. Most named entities only have a local name. A random bicycle parking is not likely to have a name in any other language but the local one. For things which actually have an exonym (like countries and larger cities), you will find additional namespaced language tags like `name:ja` and `name:en`, but a bicycle parking in Japan usually doesn't have an English name (although you can translate the Japanese name).
As for why you are seeing Chinese, that has nothing to do with OpenStreetMap. Some other tool in your chain is doing that (mkgmap?).
If in the future most Americans do end up saying 'Lake America', `name` could follow that too, and Lake Ontario would end up in `alt_name`.
Or perhaps Americans from the White House to the New York Times to the school curriculum will call it Lake America, but Canadians will stick with Lake Ontario. In that case the top-level local language `name` might end up as 'Lake America/Ontario' (combining all local languages and variants) and `name:en` (English in general, so America would be a minority there) and `name:en-CA` would say Lake Ontario, and `name:en-US` would say Lake America. Time will tell. OpenStreetMap adjusts accordingly.
For the official name there is simply a different tag (`official_name`, or in this case `official_name:en-US` because the lake borders more than one country). Having that available makes it possible to search for it by that name.
Open Street Map tends to reserve the “name” tag for what things are commonly called by the local community. It appears that for the Lake Ontario and The Gulf of Mexico they’ve added an “official_name:US” tag to capture the names in the executive orders.
Interesting that he changed the name to that of the entire continent, so Mexicans and Venezuelans can feel part of it.
https://wiki.openstreetmap.org/wiki/Key:official_name:en-US
"Few if any renderers consume official_name=* or any of its subkeys; in practice, the purpose of this key is for geocoders to find the feature when a user searches for the official name."
Though generally official names are the names nobody uses. For example the country labeled "France" also has the attribute "official_name:en": "French Republic"
If they ask what the rules of the game are, they've just lost again.
They didn't invent being deliberately obtuse.
Now, I'd love for each geographical region to take their very worst area, and rename it after a certain politician for the lulz.
Doesn't seem to be very clever to me.