On Fri, 2017-09-22 at 13:16 +0100, Philip Barnes wrote:
> On Fri, 2017-09-22 at 11:28 +0100, James Harrison wrote:
> >
> > As an aside to this conversation, where are photos most useful for
> > OSM
> > contributions? Just built-up areas or road junctions etc? If we
> > were
> > designing a
I certainly prefer to take geo-referenced photos and upload them
through a script rather than use an app that deletes them. I at least
have a backup, and can refer back to find street or shop names that
mapillary has chosen to blur.
I have also discovered that mapillary has its own community,
I use the script "upload_exif.py" which is part of
https://github.com/openstreetcam/upload-scripts for OSC
for Mapillary, I just drop the files on their website (in your account
under uploads, there is an upload button). But they do have scripts as
well, probably
On Fri, Sep 22, 2017 at 09:26:53AM +0200, Marc Gemis wrote:
>
> I use a DSLR to take pictures, then georeference them, and then upload
> them via a Jython script to OpenStreetCam. I use the Mapilary website
> to upload them there as well. They have scripts to upload pictures as
> well.
I also do
While we would probably all love to be able to our hands on some
Hollywood magic (I just have s many photos that are just a tiny bit
too blurry to decipher :-)) I suspect Marc was referring to reverting
back to the original non-blurred images, removing blurs added for
privacy reasons,
Simon
Then I would go with Wikipedia, you can more or less chose any open
license you want for the pictures.
Those pictures will show up next to Mapillary and OSC photo's on
http://projets.pavie.info/pic4carto/index.html
As to what is interesting:
we map:
* landuse
* POIs (shops, hotels, ...)
*
On 21/09/17 22:33, Simon Poole wrote:
>
>
> while I don't have any first hand knowledge specifically about the
> UK, but continental Europe has a largish number of companies that do
> that kind of photographic asset management professionally (and which
> seem to have an at least half working
from my Samsung Galaxy smartphone.
Original message From: Simon Poole <si...@poole.ch> Date:
21/09/2017 22:33 (GMT+00:00) To: talk-gb@openstreetmap.org Subject: Re:
[Talk-GB] OpenStreetCam or Mapillary?
Not commenting directly on the pros and cons, but t
When you attach the smartphone to the front window of your car or on
the bar of a bicycle, there is not much aiming involved. The apps keep
on taking pictures. The pictures that are taken do not contain blurred
sections, only the ones you can access via the website. On Mapillary,
you can indicate
The relevant background/motives as I understand them...
Both currently aren't too limited on funds & I licensing might allow all
photos/data to be taken for OSM if they did close down.
Mapillary is a startup for the street-level photo viewing technology.
Seemingly other things now like 3D models
(Second try, the first one went only to Neil)
Slightly off-topic, but answering Neil's questions:
I use a DSLR to take pictures, then georeference them, and then upload
them via a Jython script to OpenStreetCam. I use the Mapilary website
to upload them there as well. They have scripts to upload
I've tried Mapillary -- not tried OpenStreetCam yet.
Comments mostly relate to the Mapillary Android app:
* Mapillary App drove me nuts until I worked out how to take photos
individually when walking, rather than as a continuous sequence -
more car oriented?
* Seems to be moderately
Not commenting directly on the pros and cons, but through their
cooperation with Here using mapillary for this would make the material
directly available to a competitor too. Now you can consider this a good
thing or bad, but in any case it needs to be considered.
Slightly OT;
while I don't have
Hi everyone
I use Mapillary, becuase they are rather more forgiving of ancient hardware
(a Galaxy S2).
I'm OK with the Mapillary licence situation, but there are differing photo
use licences between the two and TfWM may have views on that.
Paul
On Thursday, 21 September 2017 19:09:32 BST,
14 matches
Mail list logo
