mvexel has commented on the following diary entries

Post When Comment
How do you map while on the go? about 2 months ago

SimonPoole - do you think Pushpin OSM is a bad, destructive tool?

Mapping turn lanes in OpensStreetMap about 2 months ago

From the perspective of a large scale data user (Telenav) - in the end we will just do whatever it takes to get the best coverage for our users. If this means supporting two competing conventions for a while, we will do that.

That said, we will always try to get wider support for a single tagging convention that ensures ease of use and consistency for mappers, but also covers more complex situations that simplified tagging schemes just cannot.

A good example is the exit_to versus destination discussion we had in the US last year, where I actively promoted switching to the much more flexible destination based tagging scheme for tagging motorway / freeway exit signposts.

If it means creating new JOSM plugins, or other tools, we will consider that. Message me if you have anything specific in mind that you think we may be able to help with.

Mapping turn lanes in OpensStreetMap 2 months ago

The one case that I can't see would be supported well by the simpler scheme is the complex intersection of the type Aury88 drew. This is where you would need a clearly defined relation between origin lane and destination way or even lane. From an application perspective, I would rather support one scheme that covers all possible cases. From a mapper's perspective, I am all for keeping it simple however. Sometimes these two sides of me don't come to an agreement.

Mapping turn lanes in OpensStreetMap 2 months ago

My observations:

1) Whatever is used significantly more should be the de facto standard. The turn:lanes schema wins here (turn:lanes on TagInfo versus turnlanes:turns on TagInfo)

2) Whatever is easier to map and maintain should be preferred, again, turn:lanes wins - BUT the fact that the relations proposal has JOSM plugin support makes it really attractive, so there is not a clear winner here.

3) From a routing engine perspective, the relations approach would be much preferred because it defines a clear from --> to relation, removing ambiguity on complex intersections.

I favor the relations approach, mainly because I deal with the routing engine dimension every day.

New ScoutSigns release - now with Mapillary power! 3 months ago

I received a few comments about the source code not being published - I just wanted you all to know that we are working on getting this out into the open. Thanks for your patience!

A look at Scout Signs 3 months ago

malenki - this is something that we plan to address in a future release. As always 'armchair' mappers should be careful with any information that is not based on own survey, just like with Bing imagery etc. So it's not really plugin specific - otherwise I would consider adding a notice.

In the mean time, we added Mapillary support in the latest release - let me know what you think.

community building 4 months ago

A great idea! Thanks for sharing!

Mysterious: Invisible ways in JOSM 7 months ago

I was wrong - there were nodes missing from our file, which explains the missing way display. Still, there is something not quite right about the way JOSM handles these 'incomplete' files. I would say either accept them but display a warning that there are missing nodes (there is such a warning in the console output, but not in the UI), or enforce full referential integrity for JXML files.

I also pointed to this entry on the josm-dev mailing list and there are some thoughtful responses there.

Mysterious: Invisible ways in JOSM 7 months ago

Thanks for looking bdhurkett - All existing nodes are actually in the change XML file, so all information needed to reproduce the way are present. And as I mentioned the way is actually there - if you click in the right place, it is selected. We even made sure to order the elements so that there are no forward references in case the contents are read using a SAX-like parser. I did check the map paint / rendering settings, I am using the defaults which I believe should render the indicated ways visibly.

A look at Scout Signs 9 months ago

Martijn here from Telenav. I am not developing the plugin but working closely with Bea who does!

First off thanks for taking the time to beta test. Because it is still beta, we hadn't gotten around to creating a proper wiki page yet, but I have at least created a stub now. Feel free to use the talk tab there to provide feedback and suggestions as well. There should also be a link to this page in the JOSM description shortly.

I really like the suggestion for (optionally) hiding the signs where maxspeed is already present on the way - or perhaps only when OSM and the sign agree. We will look into this after we get the initial version out.

The CV algorithm processing the signs into speed limits is definitely not fail-safe - there is no such thing, unfortunately :) We did not see a lot of mistakes so far, but it's definitely possible. (This is one of the reasons it's a JOSM plugin and not some sort of automagical data processing / importing machine).

The offset from the actual sign position is perhaps confusing initially but expected if you reckon that the camera position is recorded at the time the picture is taken, and not the sign position (which is unknown). I don't think it's a huge deal, but if it turns out to be an issue we can look at ways to mitigate.

As Skippern mentions, a collaboration with Mapillary would make sense, and we have that in the works, so expect to see that sometime soon.

Feel free to drop me a line (or ask on IRC) if you have any other questions or feedback. Excited for this plugin to go live!

Potlatch 2: quickly move from task to task 10 months ago

This is an excellent improvement Richard! I am guessing it could be used with any Overpass Turbo GeoJSON export as well?

I am currently working on direct GeoJSON support for MapRoulette (as required by the Magical MapRoulette Machine) so I am hoping that geoJSON can grow to be some sort of microtask format standard for OSM.

6000 EUR for OpenStreetMap 10 months ago

I have been using to shop and automatically have Amazon donate a fraction of the price of my purchases to the Humanitarian OpenStreetMap team. I don't know if this is Amazon US specific, but it seems to be a similar setup. I believe the donation is 0.5% of each purchase.

Now Live: Notes Posted By Scout Users 10 months ago

Thanks kerosin! Well, to be honest, at first we are seeing some 'unfixable' things come through our filters, but we expected that to happen, and are monitoring the notes closely.

Scout GPS Navigation (formerly Skobbler) is not affected by this change yet. We are working on this! I will post diary entries whenever I have Scout-related news to report.

Now Live: Notes Posted By Scout Users 10 months ago

SanderD: Currently it can be up to 4 weeks, but we're working to refresh more often. TomH: I will see that that gets fixed.

The Magic MapRoulette Machine 10 months ago

Yes, you could change the query to include a bigger bounding box or loosen other query parameters without creating a brand new challenge.

CheckAutopista Update 12 months ago

This is an amazing tool!! I can't believe I didn't know about it.

After using it for a few minutes I am just amazed by how well it works and how well designed it is.

A couple of questions I have:

  • I see you are displaying exit_to tags in green, is that suggesting that exit_to is a good way to tag motorway exits? In the U.S., we have been discussing moving to destination= and I am personally not a fan of exit_to.
  • Is there a way to get a permalink with a specific freeway pre-loaded?


New MapRoulette challenge: TIGER Mismatched Ways 12 months ago

Takuto - Whoa, yes the first batch is done already! I didn't expect it to happen this quickly. Let me get some more up (there's lots more) - will post here when they are ready.

First thoughts 12 months ago

Let me chime in with a warm welcome to you! Lots of great advice already here. Let me see what I can add. It is easy to get overwhelmed by the sheer amount of work to be done, so there is a lot to be said for starting small and bringing the areas you know best up to date first.

There are some tools out there that may be helpful, like the Battle Grid which points out areas where OSM is in poor shape compared to more recent (better quality) TIGER data. Also MapRoulette which gives you random tasks to help fix up the map around the US and beyond.

Also, you are invited to join a Virtual Mappy Hour sometime soon! Virtual Mappy Hours are online events where we talk about OpenStreetMap, answer questions, and welcome newcomers. You can join through Google+ Hangouts. We hold them every other week on Monday. Look at the OpenStreetMap US Google+ page for announcements. I hope to see you there sometime!

Finally, there is also a mailing list specifically for the U.S. OSM community. A great place to introduce yourself, ask questions, make suggestions, etc.

New MapRoulette challenge: TIGER Mismatched Ways 12 months ago

Pieren: I usually just delete these ways that don't seem to exist. Before I do so, I look up and down the main road to see if the road should be moved rather than deleted. But especially the short 'doodles' sticking out form the main road that have no names, I mostly just delete.

MapRoulette Challenges 'Ways Needing Smoothing' and 'Crossing Ways' Completed about 1 year ago

Be A Mapper, thanks! I hope for more good challenges in the future.

Simon, thanks. Yes, there would be a noticeable improvement in routing quality for those particular locations where TIGER misalignment is really bad. Scout is pretty forgiving when it comes to determining which road you are on - as are most GPS based navigation systems - but where it gets really confusing, like this for example:

confusing will get wrong guidance and 'rerouting...' prompts consistently. In those places, GPS based routing applications will immediately benefit from targeted improvements. I have a similar challenge lined up that identifies OSM ways that are significantly misaligned from more recent (2014) TIGER data, which should help resolve some of the remaining TIGER mess.

Can you believe we are still cleaning this up, 5 years after the import?