Excelerator returns results using the Loc-I full URI as the location identifier.
Ideally the Loc-I full URI would be used as the universal identifier, however, at the moment the reality is that datasets are coded with the local identifier (i.e. not the full URI). This means that users will have to manually edit the output to be able to join that data with other data (e.g. held in databases) or spatial layers (e.g. existing SHP/Geojson/etc).
This issue is to discuss the possibility of adding an extra columns for the local location identifier.
Excelerator returns results using the Loc-I full URI as the location identifier.
Ideally the Loc-I full URI would be used as the universal identifier, however, at the moment the reality is that datasets are coded with the local identifier (i.e. not the full URI). This means that users will have to manually edit the output to be able to join that data with other data (e.g. held in databases) or spatial layers (e.g. existing SHP/Geojson/etc).
This issue is to discuss the possibility of adding an extra columns for the local location identifier.