Currently we have two big classes, arbitrary geometry and tile_map_service_grid. This leads to many if else clauses in the rest of the code to determine which type of project gets different treatment. It would be cleaner to separate that logic entirely into new classes.
These new classes mirror the usage in the app-client, names are not final:
old -> tile_map_service_grid
Change Detection
Overlay (Completeness)
Tile Classification (Build Area)
old -> arbitrary_geometry
Footprint
new Digitization
-> !! This also requires a refactoring of the respective tutorials
Currently we have two big classes, arbitrary geometry and tile_map_service_grid. This leads to many if else clauses in the rest of the code to determine which type of project gets different treatment. It would be cleaner to separate that logic entirely into new classes.
These new classes mirror the usage in the app-client, names are not final: old -> tile_map_service_grid
old -> arbitrary_geometry
-> !! This also requires a refactoring of the respective tutorials