fuck diversity. A man and a woman are different from each other. You can’t change the nature

This makes no sense and what makes you state your opinion in such an offensive way? We’re different from each other and it’s called diversity. We want basic rules in place to keep our interactions civil, precisely because there are comments like yours making people fell not welcome.

Edits aren’t required to serve on the OpenStreetMap US board. In fact some of the most valuable board members in OpenStreetMap US’ past haven’t edited much. The board isn’t about editing OpenStreetMap, it’s about supporting and growing OpenStreetMap in the US. It’s about our ability to put on awesome conferences, to run solid communications, to raise money, to keep our books in order, and to facilitate local events.

As someone who’s served for 3 years on the board and does quite a bit of editing, I welcome anyone to the board who’s passionate about OpenStreetMap and is ready to put in real time. Great skills in organizing, communications, networking, fund raising and a passion for the project don’t always go with mad mapping kills :)

Everyone is welcome. I’m personally thoroughly impressed with each person who I’ve been on the board with this past year and each new candidate running this year.

As jonwit pointed out, there’s a townhall recording from last night to learn more about the candidates.

Cheers!

@SK53 - y, this needs to be translated, working on it.

Note that we’ve been in touch with the Japanese community from the get go on this project, with Taichi Furuhashi being extremely helpful - there’s a Facebook coordination page and continued communication in Japanese: https://github.com/mapbox/mapping/issues/120#issuecomment-140966601

While the Mapbox drawn building outlines are a big improvement over those available from CCSF, they are not particularly well aligned to Bing. In general, I often need to move entire blocks 10 to 15 feet in order align them to the image reference we are generally expected to use.

Andrew - note that Bing imagery is not the authoritative image reference for OpenStreetMap as it can be off in bad cases by meters. In the San Francisco tracing effort we have used existing GPS data and the LIDAR derived SF public domain building dataset as location reference.

http://wiki.openstreetmap.org/wiki/Good_practice#Align_Aerial_Imagery_before_Tracing

I love this. The building dataset for SF in OSM is one of the best out there, it would be great to add building heights right into it.

You cannot forbid me to vectorize map data from your map.

The terms don’t seem they’re globally forbidding vectorizing the map, although it would be good to define what specific latitude/longitude coordinates are meant in the ToS.

If your users place the markers based on an OpenStreetMap-based map, these positions are covered by the share-alike of Open Database License.

This is not the case. Placing markers on top of an OSM based map doesn’t per se make the marker locations subject to ODbL share alike. Only if you used those markers in a way that winds up extracting a Substantial subset of OpenStreetMap the marker data would be subject to ODbL share alike.

http://opendatacommons.org/licenses/odbl/1.0/

Nice find.

I added a rudimentary city node until the original one is recovered http://www.openstreetmap.org/changeset/31950230

Please report such issues to the data working group (data@osmfoundation.org). I just notified them of the issue.

Hit send too early, continuing:

We’ll also have to balance driving editors with the goal of knowing what’s wrong on the map. We only have a seconds of a user’s time to learn what’s going on, so we’re keeping this experience laser focused.

Since we flipped the form around and offer a fast submission first we’ve increased the number of reports we’re seeing at least by 10 x. I’m seeing we lost the piwik link on the edit button so I can’t report on users we drive (getting this one back in now).

Everybody’s OpenStreetMap relevant knowledge going through map-feedback winds up on the map: either as a direct edit by the Mapbox team, as a note or by a direct edit by the user.

Let there be no doubt that we want to grow a strong OSM community, and map-feedback has been one of our approaches to help do that.

Adding to this: a previous iteration of the map feedback page was flipped around: the first action was “contribute to OpenStreetMap”, the second action was “let us know what’s wrong”. This didn’t work as well as we wanted to. Only a minuscule amount of visitors wound up going to OpenStreetMap (we don’t know whether they actually edited).

We’ll continue to measure the impact of this page and iterate on it. Overall, driving editors to OpenStreetMap is the best thing for the project - we all agree on that.

Alex from Mapbox data team here - thank you for the detailed write up! We typically verify incoming feedback against a second source - the bulk of it can be checked against Satellite imagery (“missing path” type of info) or like here with a municipal web site’s information. Information we can’t verify we place as notes.

I’ll touch base with my colleague Andgol first thing tomorrow and get back to you with more details of what happened here.

Part of this could be done by strengthening the connections between volunteer mapping communities and commercial data teams.

Love btw how we can have conversations directly on the changeset now thanks to changeset comments. Together with notes this functionality really helps us interact with community outside of our team right now.

Danke für die Zusammenfassung!

Daher ist es an der Zeit, dass die OSM-Community im deutschsprachigen Raum sich veranstaltungstechnisch selbstständig macht und eine eigene Veranstaltung auf die Beine stellt.

Fänd ich gut. State of the Map Berlin 2016? :) https://blog.openstreetmap.org/2015/03/10/call-for-venues-for-sotm-2016/

In my experience you’ll find three types of place=hamlet nodes in the US. This is including some of what has already been said on this thread:

1. place=hamlet that should be a place=suburb
2. place=hamlet that should be a place=neighborhood
3. place=hamlet for a trailer park
4. place=hamlet for a housing project like Brooklyn’s Bay View Houses
5. The real place=hamlet

I suggest the following fixing strategy for all hamlets in populated areas:

• Review against satellite imagery
• If clearly a trailer park or a housing project, draw closed way around it, tag landuse=residential name=*
• Else if built up urban area change place=hamlet tag to place=neighborhood
• Else don’t change.

This is the rule I’ve been personally following. How does this sound?

I think it would be best if OSM carto would not to render objects anymore which are tagged with tiger:reviewed=no.

Interesting idea…

One example I found just by zooming into Eric’s Arnold rendering: here in WV there’s a highway=residential which has moderate traffic flows and should really be a tertiary.

And y, we should be able to detect these types of issues w/ HPMS/ARNOLD.

@RichardF - yup, thought about it… but: what we have of ARNOLD right now is pretty much what HPMS (attributes) is using of ARNOLD (geometry) - which isn’t much. OSM or TIGER coverage is much much bigger than HPMS, and ARNOLD itself is not available for download, I think. Let me check on the latter, actually.

Richard - thanks for posting.

Over here in the Mapbox team we’ve been mostly focused on fixing alignment problems via the micro tasking manager to-fix (background).

We’re using updated TIGER data as a guide for editing, one weakness of the original TIGER data is the lack of classification granularity in the lower level road network - exactly the reason why we have this mess in OSM now. Just talked to Eric Fischer over here and we want to look into whether by surfacing the existing road classification in TIGER comparison layers better we can at least focus retagging efforts better by knowing where TIGER does / doesn’t provide useful classification information.

I like the framework you’re suggesting for retagging.

Some other useful tools for fixing TIGER:

• Martijn van Exel’s TIGER vs OSM battle grid - alignment focused https://oegeo.wordpress.com/2013/11/07/the-tiger-versus-openstreetmap-battle-grid-improved/
• Eric Fischer’s iD/JOSM tracing layer for TIGER - highlights alignment and shows road labels, you can use this with or without the battlegrid https://www.mapbox.com/blog/openstreetmap-tiger/

When did you ship Eric off to North Korea? ;)

Haha, yeah, bad photoshopping :)

This is awesome.

I’d love to be able to put a bounty on notes I’d like to see addressed. Paying small bounties like this could be interesting to incentivize on the ground surveys where work can’t be done remotely.

Eric Fischer does all the magic! https://www.mapbox.com/blog/osm-community-visualized/