You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Panoramic images are cool! They render in the viewer with yellowish arrows and you can drag the viewer around 360 degrees:
But we don't handle them correctly. I discovered that when we call the Mapillary API, we get the same key multiple times with different camera angles:
>feature.properties.key"vdjJHj_NLRqcYa08vElpZQ">feature.properties.ca187.626653150049//... some time later...>feature.properties.key"vdjJHj_NLRqcYa08vElpZQ">feature.properties.ca203.359039340867
We are expecting this key to be normal unique key, so d3 will only show one of them as a normal marker. We should instead detect this condition in the loaded callback, set a flag that it is a panoramic image, and style the panoramic markers differently, not using ca (camera angle).
The text was updated successfully, but these errors were encountered:
Panoramic images are cool! They render in the viewer with yellowish arrows and you can drag the viewer around 360 degrees:
But we don't handle them correctly. I discovered that when we call the Mapillary API, we get the same key multiple times with different camera angles:
We are expecting this
key
to be normal unique key, so d3 will only show one of them as a normal marker. We should instead detect this condition in the loaded callback, set a flag that it is a panoramic image, and style the panoramic markers differently, not usingca
(camera angle).The text was updated successfully, but these errors were encountered: