Issues to resolve
Bare surface classes
Some bare surfaces do not fit into the current group of bare surface classes - how do we fix this? The ‘bare surfaces’ group of classes doesn’t fill the thematic space available – for example there is no bare rock category available below the alpine environment unless it’s a landslide or along a lake or river. We’re considering the merit if merging ‘Alpine Gravel and Rock’ with ‘River and Lakeshore Gravel and Rock’ into a new generic ‘Gravel and Rock’ class. What do you think? Collaborating agencies: Please leave your views as comments below, along with your name/organisation. |
Remove redundant boundaries?
Should boundaries between identical classes be removed? Our compilation to date has maintained an absolute respect for earlier mapping by not removing any existing boundaries, but inserting new boundaries along new or corrected land cover edges. As we do this, segments of former polygons have their attributes corrected so they often become described identically to their former neighbours. The old boundaries between neighbouring polygons therefore ceases to delineate any real difference between one side and the other so we’re contemplating a pre-release dissolve of these now-spurious boundaries to ‘clean up’ the database. What do you think? Collaborating agencies: Please leave your views as comments below, along with your name/organisation. |
Topo50 coastline
Should we replace the LCDB current coastline with the TOPO50 coastline? Collaborating agencies: Please leave your views as comments below, along with your name/organisation. |
Undersized polygons - remove?
There are many polygons smaller than the LCDB minimum
map unit size of 1 hectare. Should we remove these, and if so, at what threshold? Collaborating agencies: Please leave your views as comments below, along with your name/organisation. |
1-4 of 4