Closed gyllen closed 10 years ago
+1
+1 Also, let us (Mapillary) know if you need anything tweaked on our end.
+1
+1
+1
+1
No need to +1 here: everyone sees the value. The most expedient way to integrate this would be to implement & PR it.
Awesome, @tmcw do you have any pointers and ideas of how you want the integration?
You would write the integration with the api as a new service, and probably use the gpx layer as an example of writing a new layer/domelement that can integrate with the existing map
Cool, I would also like to show the Mapillary images on a click. Would you prefer that as a popup or what do you prefer there?
Depends on the UX you create - small thumbnails that expand in a panel might work. popups/modals are probably not the best pattern, since they'd likely interfere with the editing that such images should enable.
So I have been messing around a little with the code. And as I see it there is 2 ways I can solve this.
@tmcw Do you have any thoughts on this?
@tmcv Have you had the time to give this any thought?
Option 2 sounds better to me - it's somewhat similar to what we already do with GPX tracks as reference, and would mean that the UI for toggling mapillary could be located alongside other layers on the right. This would also be similar to a general image+exif viewer if we ever get a PR/time for that.
Should this depend on a generic way to open geotagged photos? Much of the user-facing elements should be the same, and I doubt if we can deploy if we're integrating mapping from photos only when users upload them to a third party service, so the generic way ends up being a pre-requisite for this anyways.
Should this depend on a generic way to open geotagged photos?
I don't think so, unless someone is volunteering to actually build that. Luckily in this case there are people ( @gyllen ) who are somewhat up for implementing this, and their wants may coincide with their skills and time. Unfortunately on the other ticket, we had the wants, but noone with the skills or time.
Hi there, there is some initial work, https://github.com/mapillary/id which we need a bit of feedback on. It looks like
Small screencast here: https://docs.google.com/a/mapillary.com/file/d/0B0YWa-MXQt98VlFaS25BMDVhTkk/edit
So, feel free to try it out and give feedback on
WDYT? This is not PR-ready, but hopefully will be soon!
/peter
Hi @peterneubauer, this is looking promising. Thanks for putting in the time to work on it.
I think that rendering the sequences as an interactive layer like on mapillary.com is definitely the way to go. The hover feedback and marker with direction indicator are important affordances. I suggest putting the mapillary layer checkbox in the same group as "Local GPX File" in the background settings panel, and having it toggle both this layer and the image display.
I'm not sold on the current UI for the image as it covers a lot of the map with unused whitespace. I would try out two different ways of displaying the image:
As to "how", you'll want to follow along the lines of iD.GpxLayer
and dive in to rendering SVG elements with d3.
Mmh, have the Mapillary sequences rendering now. However, how should I go about to select the nearest photo? Make a new Mode? Right now, only core OSM features are selectable, so this would be an interactive element that is non-OSM. Advise?
@peterneubauer It wouldn't be a mode, because modes are mutually exclusive, and you want to be able to have the photo available in any mode. "Currently selected photo" would need to be a bit of state that's held outside of any mode, like in the mapillary layer or UI code.
Can you recreate your repository as a proper fork of this one so that you can see diffs of your changes versus iD master?
Looks really bad right now but I got a 30% of the left sidebar for the image, and a mapillary sequence json layer (in red), need probably another layer to place the image marker with direction onto the working area, @jfirebaugh ?
Fork is at https://github.com/mapillary/iD, @jfirebaugh
Have now got a marker on the map, see http://mapillary.github.io/iD/#background=Bing&map=20.12/-77.02209/38.90114, now I think I need feedback on the interaction with it and of course the styling, since it follows mouse clicks. Code at https://github.com/mapillary/id @jfirebaugh . Thanks!
Make it possible to view Mapillary (http://www.mapillary.com) images in the editor to derive data (see http://www.mapillary.com/osm.html).
There are two components of Mapillary that you can use for the integration.
http://api.mapillary.com/v1/im/close?lat=38.89356&lon=-77.033634&distance=100&minca=145&maxca=200&limit=3
lat, lon are floats describing the point distance (optional) is a radius in meters from the search point minca and maxca (optional) are the boundaries in degrees of compass angle limit (optional) is the number of images returned (there is a hard cap on 10 at the moment)
The response is:
To access an image use the key returned in the following urls