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
This occurs when the viewport is updated after the task is complete, usually by a subsequent geometry task. Returning the the previous task, the viewport of the previous map is restored, which doesn't necessarily have the collected geometry in focus.
Instead, if the task already has data, we should set the initial viewport to the bounds of the geometry, perhaps one zoom level up (Z-1).
gino-m
changed the title
[Draw area task] Draw area UI in invalid state after restoring draft
[Data collection] Photo and drawn area lost after restoring draft
Nov 19, 2024
gino-m
changed the title
[Data collection] Photo and drawn area lost after restoring draft
[Data collection] Photo and draw area lost after restoring draft
Nov 20, 2024
I'm unable to repro this locally. @gino-m Can we sync once for this issue?
gino-m
changed the title
[Data collection] Photo and draw area lost after restoring draft
[Geometry data collection tasks] Geometry sometimes not visible on current map when returning to task
Nov 22, 2024
@shobhitagarwal1612 Updated this bug title, description, and priority based on our discussion. PTAL?
gino-m
changed the title
[Geometry data collection tasks] Geometry sometimes not visible on current map when returning to task
[Geometry data collection tasks] Geometry sometimes not visible on map when returning to task
Nov 22, 2024
This occurs when the viewport is updated after the task is complete, usually by a subsequent geometry task. Returning the the previous task, the viewport of the previous map is restored, which doesn't necessarily have the collected geometry in focus.
Instead, if the task already has data, we should set the initial viewport to the bounds of the geometry, perhaps one zoom level up (Z-1).
Screen_recording_20241119_100010.webm
@kenstershiro @lecrabe @jabramowitz5 @anandwana001 FYI
The text was updated successfully, but these errors were encountered: