OpenStreetMap logo OpenStreetMap

mvexel's Diary

Recent diary entries

Opening Hours

Posted by mvexel on 17 July 2014 in English. Last updated on 25 July 2014.

Mapping opening hours correctly can be a pain; the format for the opening_hours key can be hard to remember. I didn’t use to do it much for that reason. Until I recently discovered that there’s a JOSM plugin for that! It works really well, let me show you how I added hours of a local restaurant in seconds.

First, of course, make sure you have the plugin installed:

install

Then, select the thing you want to add opening hours for:

See full entry

I have been following Mapillary with a good deal of interest, because they provide an open ‘street view’ platform that is explicitly aimed at improving OpenStreetMap.

Here’s an example of a Mapillary image and map context:

example

I have created an account and did some test shooting from my car, using the iPhone app Mapillary provides. This is OK, but I want better quality images. So I am looking at an action camera I can mount in my car and on my bike.

After doing some research, I narrowed the field down to two contenders: the Garmin VIRB / VIRB Elite and the GoPro Hero 3.

See full entry

Complex Intersections, or Why We Should Get Rid Of exit_to

Posted by mvexel on 3 July 2014 in English. Last updated on 5 April 2017.

Here in the U.S., we have been using the convention of tagging exit information on the highway=junction node using the poorly documented exit_to tag. The rest of the world has been using destination=, and now that I start to think about this problem more, I can see why.

Let’s take this example of the junction of I-70 and the Baltimore beltway I-695.

Example situation

(Have you used Mapillary? It’s pretty awesome and unlike Google Streetview, OpenStreetMap explicitly does have permission to map from the images. It’s pretty easy and fun to contribute your own, too.)

How to tag this so that navigation and other software could make sense of it?

Currently, the only relevant tags on the junction node are ref:left=91B and ref:right=91A indicating the exit / junction numbers. There is nothing on the `_link’ ways to indicate destination.

See full entry

New MapRoulette Challenge: Crossing Ways

Posted by mvexel on 30 June 2014 in English. Last updated on 1 July 2014.

We created a new MapRoulette challenge over at Telenav: Crossing Ways. As always with the Telenav-generated challenges, this one is US only, because we currently only process OpenStreetMap data for the United States. We are working on extending support for other regions.

TL;DR –> On to MapRoulette!!

The Crossing Ways challenge is pretty straightforward and should make for an easy challenge for novice mappers looking for something to fix. It detects ways that cross, but neither way is tagged as a bridge or tunnel. Here is an example:

Example from MapRoulette

If you open this up in iD or JOSM, you will be able to tell the required resolution from the aerial imagery:

See full entry

Brave Mappers of Wherever You Are

Posted by mvexel on 23 April 2014 in English.

From time to time someone will ask me: ‘How do I find out who my fellow local mappers are?’

That can be a surprisingly hard question to answer. You can go to your user page and see a few people who have indicated their ‘home location’ to be near yours. OSM user page map That does not work so well for a variety of reasons:

  1. Not all people set their home locations. My guess is most people don’t.
  2. People don’t update their home locations when they move.
  3. The home location is not necessarily where that person is mapping.

See full entry

Over at Telenav we have been busy comparing the GPS traces of drivers using our navigation apps against OSM data. This is fun work and sometimes leads to really useful results. One of our recent studies involved comparing what we think are one-way streets to the corresponding OSM ways. The process is quite simple: count how many traces following a given street go in one direction, and how many go in the other. If the number for one direction is close to zero, the street is probably one-way. The outcome depends on the confidence level you apply, but it turns out that there are more than 100 thousand OSM ways that probably should be marked with a oneway tag, but aren’t.

One. Hundred. Thousand.

I don’t know about you, but I think that would make for a really great MapRoulette challenge. So that’s what I did, and here it is.

But how do you know if a street should be one-way without having eyes on the ground? It turns out the aerial imagery provides helpful hints. Let me show you what I look at to verify the one-way-ness of a street using just JOSM and the Bing layer.

Let’s look at this case here:

See full entry

Those first few MapRoulette challenges did not keep you busy very long: most tasks in the Zorro / Tangled / Wrong One Ways challenges were fixed within the first few days. Dang! We were not prepared for that and had to take MapRoulette down for a little while because there was nothing to do…

But now we’re back! This time with Ways Needing Smoothing. We detect ways that have suspiciously sharp angles and ask you to smoothen them out. Here’s a great example:

example

Opening this task up in JOSM reveals that there’s more to fix than just the one sharp angle that was detected:

See full entry

New MapRoulette about to be launched!

Posted by mvexel on 11 March 2014 in English.

We are about to launch the new version of MapRoulette! Finally! The most obvious changes are that you now sign in using your OSM account - so you can track your and other mappers’ progress, and multiple challenges being available to choose from! We will launch the day after tomorrow with four new challenges to start with: the familiar Zorro Ways, ways with overlapping parts, wrong one way ways (if you know a better name, let me know..) and tangled ways. More to come!

Behind the scenes much more has changed. There is now an API for challenge providers to post their own challenges (let me know if you want access), challenges can have an area associated with them so you will be able to choose a challenge that is local to you, and they also have difficulty levels. The entire application has also been rebuilt from the ground up to be more stable, scalable, and allow more flexibility for different types of challenges in the future. If you want to see how MapRoulette is built, check out MapRoulette on Github.

So, on March 12, head on over to maproulette.org and start fixing!

Location: Santa Clara, Santa Clara County, California, United States

We are trying out something new here in Salt Lake City, Utah: Saturday Mapternoons. The next one is tomorrow, and I am looking forward to it. Saturday Mapternoons are a mix of mapping, catching up with fellow local OpenStreetMappers and geeking out over all things geo. If you’re in the area, join us!

Check out all upcoming OpenStreetMap Utah events on our meetup page.

(This was originally posted on my blog. I want to start posting here more instead. This is a start.)

If you follow the blog at openstreetmap.us, you will have heard about the Battle Grid. It is a map that shows you where recent TIGER data is different from OpenStreetMap data. Because TIGER has improved a lot over the years, and has kept up reasonably well with new road construction, a big difference between TIGER and OSM tells us that OSM likely needs some love. Here is how the battle grid looked until today:

Cells with a lot of difference between TIGER and OSM are brighter, and as a simple way of prioritizing the cleanup and update work, I colored the cells that are within a Census CDP orange, and the rest green.

As of today the Battle Grid will look like this, instead:

See full entry

Location: Salt Lake City, Salt Lake County, Utah, United States

Welcome Working Group

Posted by mvexel on 20 December 2012 in English.

I was just looking at my user map to see what’s going on with OpenStreetMap users who are in my area. It turns out many of them have zero edits. They signed up for OSM, even put in the additional, optional effort of setting their home location, but never edited. Why?

That is the Big Question we want to try and answer in the Welcome Working Group. That, and trying to come up with solutions for the ‘retention problem’. Simply said, provide a warmer welcome to new users. Our focus will not be on editors. Rather, we want to look into documentation, welcome messages, incentives to map.. You could say: the social and educational dimensions of welcoming newcomers to the community.

Do you think you have something to contribute to this process? Helping (re-)write documentation? Research new user behavior? Another angle you would like to explore? All it takes is constructive ideas and some time to act on them. We meet on #osm-strategic every Thursday at 1900 UTC.

Location: East Central, Salt Lake City, Salt Lake County, Utah, 84102, United States

Back in Amsterdam

Posted by mvexel on 18 January 2012 in English.

I'm back in Amsterdam for a bit. I haven't really have time to do any mapping yet but I'm happy to see that the area where I'm currently staying is now littered with POIs - bars, restaurants, shops, all the goodness that the Leidseplein area is well known for. Even the recently started Starbucks Invasion into the Netherlands is already reflected. Most places have URL and/or phone number data associated with them. It looks like we have user stroet43 to thank for most of the recent improvements in this area. Great work! I don't think I've met him or her. Maybe at the upcoming New Year's Drinks in Utrecht? I don't see a link to it anywhere on the OSM wiki, but they're in Utrecht this Sunday. Inquire on talk-nl if you want to know more I guess. See you there?

Location: Centrum, Amsterdam, North Holland, Netherlands

Remapping

Posted by mvexel on 12 January 2012 in English.

I got on the remapping train. It looks like Salt Lake is pretty severely affected because of a small number of decliners. I approached one of them, and he is not changing his mind. Approaching the other few soon. In the mean time, I'm focusing on the main road network. There's even a few miles of interstate that will need to be remapped. A lot of work, and not the most fun job. On the other hand, I get to (re)visit some places that could use some improvement.

Location: Winder Meadows, Millcreek, Salt Lake County, Utah, 84117, United States