A few years ago I wrote a fast parser for OSM data. I know that using parsed data would soon become out of date, but I guess mvexel's server could handle it better. If you want me to export the whole world's contributors as CSV or SQLite, I'd be happy to help.
The tool is interesting for me because I'm looking for a job in NZ/Australia/Canada. I've had more success contacting people rather than sending job applications - most job listings require me to already have a visa. I think that collaborating on open-source projects is a good way to make industry contacts, demonstrate my skills, and also benefit the community.
If you're looking for something OSM related, be sure to join the OSM US Slack channel and join #jobs there. It's formally for OSM US but people hang out there from all over. Join here: https://osmus-slack.herokuapp.com/
I’m curious about this and would love to explore it, but since I rarely use OpenStreetMap I couldn’t figure out what an OSM relation id is and how I retrieve one. Can anyone provide more explanation on this?
The OSM data model does not have a concept of areas, or polygons. A line feature ('way' in OSM parlance) that shares the same point ('node') for its start and end is usually considered to be an area. This works well for simple area features like, say, a building.
More complex area features, like ones with holes, large areas, or ones that share edges with other features, are commonly modeled using relations. A relation in OSM is an ordered list of nodes, ways and other relations, or any combination of those.
https://www.openstreetmap.org/relation/198770 is an example of a boundary relation consisting of several ways. The tagging type=boundary and admin_level=6 define the relation as an administrative boundary, and set its level in the administrative hierarchy.
You can find any administrative boundary relation by going to osm.org, entering its name into the search box, and clicking on the relevant result. The info box should say something like "Relation: Salt Lake City (198770)". The integer in brackets is the relation ID. Note that some places are only defined as points in OSM, they won't work in this tool, since it queries for data that lies fully inside the boundary.
There has to be a way to make this easier, but in the time I was prepared to spend on this, I couldn't come up with one.
I was digging through openstreet map and I only found 3 mappers in my area 50 miles out. I live in a pretty busy city so I was kind of surprised the numbers were so low
Only 10-20% of major landmarks were mapped in my city
I live in a relatively small town in northern Sweden and found hundreds of contributors. Sadly the tool clears the result list after yaskswitching on my phone and have to download the data again. Not sure how happy the server is about the usage...
It seems to be somewhat particular about relation IDs. I have it working for Palo Alto, with relation ID 1544955. If you want to try this for your city, I recommend zooming in the city on openstreetmap.org, clicking the "Query features" button on the right side of the map (it's the cursor with a question mark icon), and clicking within the boundaries of you city. On the left side, a list of features will appear. Scroll down to enclosing features, and click on the appropriate entry. A relation name and number will be displayed at the top, with the OSM data below.
I hope this stays within the Overpass API server's usage limits. Processing Palo Alto caused the page to download ~85 MB from overpass-api.de, which asks users to stay below 10k queries and 5 GB per day. The OSM wiki lists other servers, some of which allow heavier usage.[0]
The note says "It must be small-ish (admin_level 6 or higher)", which caught me out at first.
I can't use Copenhagen, which is too large a city, but I can use "Copenhagen Municipality" (2192363). This can be found with the pointer-? icon at the bottom of the set on the right, and looking for enclosing areas with a high enough admin_level.
The tool is interesting for me because I'm looking for a job in NZ/Australia/Canada. I've had more success contacting people rather than sending job applications - most job listings require me to already have a visa. I think that collaborating on open-source projects is a good way to make industry contacts, demonstrate my skills, and also benefit the community.