This implements the upload of label objects.
This is meant to be a generic upload facility for any type of label, not to be confused with the labels used in the application. Its sole purpose is to allow users to contribute any type of label via the platform.
The labels are only stored on the storage server and need to be verified and checked and manually integrated.
This is a view of the updated upload modal:
The upload label can be toggle on or off.
The user can provide a file (zip, geojson, json, gpkg) needs to be one file so zipped shp is also fine, together with a desciption.
The database table is:
It's currently only for the dev environment.
The table has dataset_id and user_id as foreign keys, audited can be toggled manually if the file is reviewed and integrated if possible ??
While the data model allows data_access of public/viewonly/private only public/private are possible in the upload modal.
This implements the upload of label objects. This is meant to be a generic upload facility for any type of label, not to be confused with the labels used in the application. Its sole purpose is to allow users to contribute any type of label via the platform. The labels are only stored on the storage server and need to be verified and checked and manually integrated.
This is a view of the updated upload modal:
The upload label can be toggle on or off. The user can provide a file (zip, geojson, json, gpkg) needs to be one file so zipped shp is also fine, together with a desciption. The database table is:
It's currently only for the dev environment. The table has dataset_id and user_id as foreign keys, audited can be toggled manually if the file is reviewed and integrated if possible ?? While the data model allows data_access of public/viewonly/private only public/private are possible in the upload modal.