Thanks Andrew
I capture at 2fps with a BlackVue (via 30fps mp4). That was
unfortunately a hard choice to do with the cost of the Internet
connection. 5fps would have been nicer. Road name signs are then
problematic not only from the framerate perspective, but that
compression artefacts glug the image up somewhat. I have some more tests
to do that might help that.
It should be relatively simple to code up for road surface type and
width. I wonder if a tool will ever appear that allows autoregen on a
per road segment basis? It would also have to know what do do about
single lane sealed roads with large gravel shoulders. (common in many
rural areas) When the sealed section goes it suddenly becomes dual lane
gravel!
I am considering doing entire towns if they are 10 streets or less. I
have to do it in both directions if sign data is needed though. I am
also happy to do a more intense capture of a small area (say 5 or 10fps)
on request.
On 7/5/19 11:34 pm, Andrew Harvey wrote:
The higher resolution images and more frequent capture when at highway
speeds are very helpful for making sure street name signs get captured
and are readable, often I see reports from downstream users about a
street name being wrong in OSM, so having this in Mapillary helps
provide some ground truth so we can update this in OSM.
Just having the street level imagery is very useful for validating
edits and mapping road features like surface, speed limits,
restrictions, turn lanes, lane counts, etc.
That said, having recent imagery is useful, so re-capturing existing
areas every few months is helpful.
Only uploading every 3 months when you have a good connection is okay,
I'll do the same, sometimes uploading imagery that's older than a few
months since I'll hold it for upload until I have access to a faster
upload connection.
_______________________________________________
Talk-au mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/talk-au
