Mapillary Now Able to Recognize and Label Objects in the Wild
blog.mapillary.com
Mapillary Now Able to Recognize and Label Objects in the Wild
1–7 of 7 posts
Re: Mapillary Now Able to Recognize and Label Objects in the Wild
#2They apply CNNs to label pixels. The result could be used to improve other computer vision tasks. Applied to maps they think it would be good to measure vegetation density or the availability and sidewalks.
Hmm... okay.? I dunno what I expected.
Re: Mapillary Now Able to Recognize and Label Objects in the Wild
#3>Here is a short list of areas where semantic segmentation is available: Graz, Paris, San Francisco, Hong Kong, Dar es Salaam, and Mexico City.
If the method is general, why only these areas?
Re: Mapillary Now Able to Recognize and Label Objects in the Wild
#4They apply CNNs to label pixels. The result could be used to improve other computer vision tasks. Applied to maps they think it would be good to measure vegetation density or the availability and sidewalks. Hmm... okay.? I dunno what I expected.
[deleted]
Re: Mapillary Now Able to Recognize and Label Objects in the Wild
#5>Here is a short list of areas where semantic segmentation is available: Graz, Paris, San Francisco, Hong Kong, Dar es Salaam, and Mexico City. If the method is general, why only these areas?
I'm guessing limited computing power while refining the algorithms.
Re: Mapillary Now Able to Recognize and Label Objects in the Wild
#6>Here is a short list of areas where semantic segmentation is available: Graz, Paris, San Francisco, Hong Kong, Dar es Salaam, and Mexico City. If the method is general, why only these areas?
It's because we need to upgrade and optimize some of the backend storage layout in order to cope with the data produced.
(I'm part of the Mapillary team)
Re: Mapillary Now Able to Recognize and Label Objects in the Wild
#7>Here is a short list of areas where semantic segmentation is available: Graz, Paris, San Francisco, Hong Kong, Dar es Salaam, and Mexico City. If the method is general, why only these areas?
It's because we need to upgrade and optimize some of the backend storage layout in order to cope with the data produced. (I'm part of the Mapillary team)
Thanks for elucidating - makes sense.