Mapillary plugin

[hjart]

Hi

The guys over at Mapillary.com recently has created an enhancement to iD which lets mappers traverse their image sequences from within iD. As an experienced and dedicated JOSM user though I would much prefer being able to do this from within JOSM. I love Mapillary and at this point has about a dozen sequences totalling ~1000 images in there and regularly check other sequences/images for useful info, so I would very much appreciate if anyone finds some time to create a useful Mapillary plugin for JOSM.

Apparently the Mapillary guys currently doesn't have the extra resources for this (see the end of ​https://github.com/mapillary/mapillary_issues/issues/148), which is why I'm asking here.

Mapillary has some documentation for their API at ​http://www.mapillary.com/developer.html (snipped from Ticket #10919)

Thank you

[jaakkoh]

Not that I could contribute any code to this but just wanted to chime in that a JOSM plugin would be absolutely fantastic.

I've been doing a stack of photo mapping over time and used OSMTracker until Mapillary arrived this spring and would just want to note that what exists already with showing the photos in JOSM (locally, though) is pretty much what I'd love to see with Mapillary photos too.

Also, as a related note, I can already view Mapillary photos locally by simply dragging and dropping (local) photos to JOSM. This produces a very nice experience for the part of the photos that are dropped in as JOSM shows even a nice directional "beak" (that's what it looks like more than an arrow) to the direction of what is the compass reading in the photo.
I'm not sure where the functionality that I currently see in JOSM comes from as I have a few photo related plugins activated -- but it's great.

If there only was a way to pull information dynamically from Mapillary's API into JOSM and see all the photos that everyone has uploaded for a given area. That would be just great. I'd by a case of beers to anyone who'd do that. And/or would happily chip in at least $20 to a Kickstarter/what_not crowdfunding project for this.

[richlv]

couldn't find a way to watch/subscribe, leaving this comment in hope to get notifications

[Don-vip]

Ticket #10919 has been marked as a duplicate of this ticket.

[AndrewSnow]

Wanted to add my desire to see this happen. I've contributed 30K images to Mapillary and made 650K changes to OSM, mostly in JOSM. Having direct access to Mapillary images synced to the area I'm working on in JOSM will speed up the editing and vastly improve the level of detail in the map.

[abienvenu]

In addition, Mapillary in JOSM would make mapping activities more enjoyable!

[Polyglot]

I think I'd like to attempt it. The first question that comes to mind is: build further on the photo mapping plug in or fork it creating a new plugin?

Jo

[Aun Johnsen <lists@…>]

Looking forward to it, without looking at it I would guess building out the photo mapping plug in would be most reasonable, you probably have most of what you need in that plugin. Making a new plugin probably would result in a lot of double code.

[holgermappt]

I also thought about this. One option would be to use most of the infrastructure of the current photo layer (GeoImageLayer, JOSM core functionality) including image display. It would need to learn to load photos from an URL and to cache them locally (which would be cool anyway). The plugin then talks to the Mapillary API and adds the URLs to the photo layer. But on the other hand a more dynamic layer like the notes layer might be better for a constant update of the available photos. It's not just photos, there are also the tracks.

Edit: I think it definitely should be a new plugin. With the traffic signs, the possible option to display them and to give feedback about falsely recognized signs, and possibly other details and options (image upload?) this will not have that much in common with the current geo image layer. Which doesn't mean that both can not share common code.

I can volunteer to do some smaller tasks or review the plugin. But I don't have enough time to write or co-author it.

[gyllen]

Polyglot, gyllen from Mapillary here. Shoot me an email at gyllen at mappilary dot com and I will give you access to new API.

[peter@…]

Guys,
we are happy to help from the Mapillary side, as mentioned above we currently have no bandwidth for the job itself - help is greatly appreciated. Contact me at @peterneubauer if you need anything.

[anonymous]

Replying to gyllen:

Polyglot, gyllen from Mapillary here. Shoot me an email at gyllen at mappilary dot com and I will give you access to new API.

Address is gyllen at mapillary dot com

[AlexandreMBM]

Already is there code being versioned?

[malenki]

Since there is now a Mapillary plugin shouldn't this ticket be solved?

[stoecker]

As we already see more detailed bug reports (which are fixed fast as I must say!) I think: Yes.