Loop3D/map2loop-2-legacy

The metafile is janky and should be abstracted away from users for the Loop remote sources

Closed this issue · 1 comments

The metafile is janky and should be abstracted away from users for the Loop remote sources

Solved by commit ec121c9. Project objects now accept a loopdata_state param that indicates loop remote sources are to be used and which loop service to get it from WA, QLD etc.