Open AndyFoy opened 11 years ago
It is unknown if any LERCs would like these features to be developed at this stage. Please indicate if you would like this change request developed.
We have data for Rivers in line format. This is closely related to the polygon data and will use the same incid where stretches of River are mapped partly as polygons and partly as lines. "Incids cannot contain more than one feature" seems to be a problem.
There is certainly the hope to map hedgerows and perhaps ditches which are not in MasterMap. These would be done as lines.
We would hope to use point data as well. We have done but having point data within the MapInfo layer caused problems with some processing so I took this out.
We would certainly like the ability to use point and line data in the future (although not sure exactly when) - our existing hedgerow data comes to mind plus chalk river data that is available for download.
Similarly point and line functionality would be useful - rivers are a bit of a pain as they are mapped as polygons above a certain channel width i think, so the lower reaches will be in the polygon layer anyway, but not the headwaters.
Description
Currently the tool is designed to work with GIS layers containing polygon features. However, IHS and MasterMap are both designed to work with polygons, lines or points. Hence in future users may have point or line GIS layers that they would wish to view/maintain using the tool.
Note: CR31 and CR33 are prerequisites of this change request.
Proposed Solution
Enhance the tool to enable it to work with point, line or polygon GIS layers, amending the functionality and user interface as required, e.g.:
i. Logical split and merge functions are valid for both point and line features. ii. Physical split and merge functions are valid for line features but not for point features. iii. Area values & calculations are not required for point or line features. iv. Perimeter values & calculations are required for line features but not for point features. v. History logging to be performed for both point and line features for all valid update types (attribute updates, splits, merges). vi. Ensure the relevant records from the lut_ihs_habitat lookup table are used accordingly (i.e. which ihs_habitat records relate to points, lines or polygons). vii. Ensure the relevant site_id column is used from the lut_site_id table. viii. Incids cannot contain more than one type of feature.
ArcGIS will obviously require point, line and polygon features to be within different feature classes so the tool will need to identify which type of feature class is in use.
MapInfo can allow point, line and polygon features to be within the same feature classes so the tool will need to identify which type of feature are being processed.