OpenStreetMap

lxbarth has commented on the following diary entries

Post When Comment
How we apply map feedback 20 days ago

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.

How we apply map feedback 20 days ago

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.

Social Engineering the Mapbox Data Team 29 days ago

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.

Rückblick auf die FOSSGIS 2015 in Münster und Ausblick auf die Zukunft der FOSSGIS about 2 months ago

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/

Hamlets in US cities about 2 months ago

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?

Fixing the rural US 3 months ago

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

Interesting idea...

Fixing the rural US 3 months ago

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.

Fixing the rural US 3 months ago

@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.

Fixing the rural US 3 months ago

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:

Japan, why are you so beautiful? 3 months ago

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

Haha, yeah, bad photoshopping :)

Now Live: Notes Posted By Scout Users 5 months ago

This is awesome.

Website for asking to improve just one area in OpenStreetMap (or paying for improvement) 5 months ago

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.

Why I'm running for OpenStreetMap US again 6 months ago

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

The trouble with the ODbL - summarized 6 months ago

Imagico:

Of the points listed above at least 2, 4, 5 and 6 are not specific to the ODBL (meaning they would apply for many other licenses likewise). Before you say PD would not have these issues remember that true PD does not exist in most jurisdictions.

2, 4, 5 are clearly issues of the ODbL. 6 is an exacerbating factor when having a high maintenance license. True, could be an issue for other (open) licenses too.

1 and 3 are issues of EU database law and not specific to the ODBL either. Short of giving away all data without limitations there is no solution for this. It seems to me the authors of the paper you cite are not really familiar with the legal basis of data and database rights in Europe.

This is a rather technical argument. Sure, some of the issues in the ODbL go back to the European Database directive.

You probably should point the National Park Service to NASA which apparently has no such issues.

NASA is placing OSM labels on top of their imagery which is a very straight forward use case even under the ODbL. NPS would like to maintain some of their data as part of OSM, which makes share alike a show stopper.

The case of Yale University seems to be based on the misconception that any license can force you to give away other data and force you to violate other obligations. The only thing the ODBL can do is forbid you to use OSM data under certain circumstances, it has no power to change your other legal or contractual obligations.

Exactly the point of the paper. The ODbL is so complex that we're losing people based on misconceptions. If you were a lawyer and magically gave away free, concise and fast legal advice every time such questions crop up, the penalty we're paying for the complexity of such a license would be smaller.

Generally citing people who do not use OSM data because of certain fears without analyzing if those fears are well-founded seems inappropriate and misleading. The key words in all your case examples are 'could', 'might', 'concerned', 'worried' etc. and the text makes no attempt to analyze the validity of these concerns.

See above. It doesn't matter whether the concerns are actually valid. It matters whether people have them and they do. Every week I hear of legal departments saying no to OpenStreetMap because of its license.

Frankly i am somewhat appalled by the fact that you do not acknowledge the LWG efforts with the community guidelines to shed light on unclear and difficult to understand aspects of the ODBL. If you really want to help data users to use OSM data and resolve their concerns you should support these efforts by helping to communicate them to potential data users.

I'm very grateful for the LWG's work and I agree with you which is why I am hoping to get to a clarification on geocoding https://lists.openstreetmap.org/pipermail/legal-talk/2014-October/008003.html

====

giggls:

There is a saying in german whichg goes "wes Brot ich ess, des Lied ich sing" :)

We talked about this on Twitter https://twitter.com/lxbarth/status/527121888024465408 . I don't want anyone to dismiss the points of the paper based on who I work for. Please go get in touch with every one of the captured case studies and make yourself a picture.

====

Cquest:

This paper definitely does not provides a comprehensive overview of issues. It provides only on side of the issues, reinforcing only one point of view.

It does not cover hundreds of use of OSM data where the ODbL license is not an issue at all.

The ODbL just doesn't have any issues except where it has issues ;-)

====

Open/free free projects rely on people contrubuting to them, which is one of the main goals of requiring attribution, share-alike etc. The US government does not need that.

This implies that share alike has a benefit for contributors which no-one has been able to explain to me.

====

mcld:

I know these guidelines are not part of the licence, but as guidelines officially endorsed by OSMF, I would expect most jurisdictions to consider them as normative.

Fair. The paper itself uses more nuanced language, namely that the definition of what's Substantial by the OSMF guidelines is far off from what's case law so far.

Importing 1 million New York City buildings and addresses 8 months ago

Is the part of convert.py dealing with T-intersections available somewhere as a standalone program? It would be useful in many other situations!

It's not. Feel free to lift it :)

Importing 1 million New York City buildings and addresses 9 months ago

Now that we've got it imported, when will NYC be releasing new data, and how will we handle updating it?

@pnorman - we're still focused on clean up tasks, but with the next significant building or address import we should run a diff against OSM data and see whether there are worthwhile updates to go after. How exactly that's handled best I think depends a lot on the quality and the quantity of the specific changes.

San Francisco building footprint data completed 10 months ago

Did you use any (semi)automatic tools for extracting the buildings?

All done by hand.

How have you doing the map animation? It's really cool

Take a look here: https://github.com/Rub21/osm_visualization

Connecting Communities With Improved OpenStreetMap Credits on Mapbox Maps 12 months ago

Phase one of the changes I described above are rolled out now with Mapbox.js 1.6.3. What's missing now is updating our infrastructure to link attribution differently and switching maps directly viewed on Mapbox.com over to the new Mapbox.js. https://www.mapbox.com/blog/mapboxjs-v163/

Connecting Communities With Improved OpenStreetMap Credits on Mapbox Maps 12 months ago

Rasher - let me reach out.

Attributing OpenStreetMap 12 months ago

Thanks for comments everyone. I've posted updates here: http://www.openstreetmap.org/user/lxbarth/diary/21847

Re: "improve this map" in German - good point, take a look at this code sample, it's easy to change the language in the attribution: http://bl.ocks.org/lxbarth/9490377

I will ping the Zeit Online team.