Water - Import metadata to start a new measurement network

This guide will explain how you can import measurement point metadata for new measurement points such as a well / tube into the portal.

Make sure you have your exported data ready in a supported format (csv). For example in Excel this can be done by File -> Save as xxx

IMPORTANT: Make sure you save the file with a ; delimiter.

Try to match the names of the columns to those used in the portal.
In the CSV it is recommended to use a # before the field you use as a key to check if there are existing objects you want to update. For example if you have an object in your portal with the description of PB01 you want to add a # before the description header in your CSV to map on descriptions. (#description).

Here is a mapping for the most used basic header fields for GroundwaterWells.

What	Field-name in CSV	Description
Well Name	well_description	This is the visible name of the well in our portal. For example: PB01
Tube Name	description	This is the visible name of the tube in our portal.
Well Head	well_properties_well_head	The height of the tube in reference to the location height reference such as NAP
	well_properties_well_head_timestamp	The time on which this value was measured, for example when the tube was placed or when the tube was schortend / lengthened. Needs to be in the format of: dd-mm-yyyy hh:mm:ss Like: 01-01-2020 00:00:00
Surface Level / Ground Level	well_covering_surface_level	The surface level or ground level is the level at which the ground is set. For example if a tube is placed in a field of grass the height in reference to the location height reference such as NAP is considered the surface level or ground level.
	well_covering_surface_level_timestamp	The time on which this value was measured. Needs to be in the format of: dd-mm-yyyy hh:mm:ss Like: 01-01-2020 00:00:00
Depth	well_properties_depth	The depth of the well.
	well_properties_depth_timestamp	The time on which this value was measured, for example when the tube was placed. Needs to be in the format of: dd-mm-yyyy hh:mm:ss Like: 01-01-2020 00:00:00
Sensor offset	schlumberger_diver_sensor_offset	The negative kabel length from the well head to the sensor as explained in: https://munisense.zendesk.com/hc/en-us/articles/360026736773-Installation-Manuals-for-water-sensors In short the cable length is measured from the bottom of the sensor to the well head. If the kable is 2.5 meters long you should put -2.5 in your csv
	schlumberger_diver_sensor_offset_timestamp	The time on which this value was measured, for example when new hardware was installed in the tube. Needs to be in the format of: dd-mm-yyyy hh:mm:ss Like: 01-01-2020 00:00:00
Rijksdriehoek X	loc_x_rd	You either use the Rijksdriehoek values if you are in the Netherlands to set your position. Or you use the latitude / longitude
Rijksdriehoek Y	loc_y_rd	-
Latitude	loc_lat_wgs84	-
Longitude	loc_lon_wgs84	-

Only use the headers you have data for. If you do not have data please remove the columns in your CSV file.

Here is an example file:
Import_munisense.csv

Now go to your portal and follow these steps:

1. Open the Import page in your portal (if you don't see this page please contact our support)
2. Click on New Import Job
3. Select the CSV file and set the correct settings.
   
   1. File: upload your CSV
   2. Domainobject Type: Should be set to GroundwaterWell
   3. Timezone of the Data: Your timezone like Europe/Amsterdam
   4. New Objects: If you are updating existing objects select "warning" otherwise allow.
   5. Existing objects: If you are updating existing objects select "Use / Replace" but be careful you will overwrite data! If you are creating new objects select Warning
   6. Result Conflicts:
      1. The option "Use Old" allows you to import new data but if overlap is detected the old existing data will be preferred and the new data will only be imported after the time-span of the old data
      2. The option "Use import" allows you to import new data but if overlap is detected the old existing data will be deleted and the new data will be imported (destructive action!)
      3. The option "warning" will give you a warning if overlap is detected with the old existing data
   7. Decimal Separator: Select the way your values are separated for decimal values.
4. When ready click on Upload
5. You will be redirected to the detail view, on this page it is also possible to upload additional files for when you for example have a single file per object
6. Now first click Validate Job to make sure your uploaded files are correct (please note that it can take some time for the validation process to finish). The page will refresh every 20 seconds.
7. Notice the bottom of the page for any warnings.
   
8. If needed correct these warnings with the Mappings option, use the PK checkbox to indicate that that field is used to identify an object.
   1. If you use the same column names as the portal uses (or you use the import file) this should already be set correctly
9. If needed click Validate Job again until all warnings are solved
10. If you have any other warning please pay them a closer look! They might indicate invalid values or other issues. Columns with warnings might be skipped in the import or can fail your import! If y ou are unsure or have any questions regarding the warnings present. Please contact our support!
11. If needed click Validate Job again until all warnings are solved
12. When everything looks OK click on Import Data
13. You can view the progress of your import by looking at Status in both the detail view as the list, you do not need to keep the import page open. When done the status will be set to Imported

Importing images

Images can be uploaded by uploading them to the import job and referencing the files names in the CSV file so they can be attached to the right measurement point. It is expected that the objects already exist and thus you are updating existing objects!

Please note that this will overwrite any images already present for the property that is being imported. It is even possible to attach multiple images to a measurement point in a single import job.

This works as follows:

1.  Use Add files to job to upload images that are to be attached to measurement points. It is also possible to upload all the images at once by uploading a zip-file that contains all of them.

2.  The CSV file will contain the names of the images split by a | character if there are multiple.

Image Mapping:

What	Field-name in CSV	Description
Description	description	The description of the well you want to add the images to. Make sure the # is added to force the portal to look for objects with the same description!
Cover images	well_covering_images	Pictures of the cover of the well and the surroundings. usefull for fieldworkers using the fieldwork tool. Multiple images should be included split with a | sign, as follows: filename1.jpg|filename2.jpg
Drilling Profile	well_covering_drilling_profile	An image of the drilling profile. Usually this depicts the different ground layers. Multiple images should be included split with a | sign, as follows: filename1.jpg|filename2.jpg
As build images	well_covering_as_built_images	Pictures of how the well is build / the tubes are situated on the inside. If multiple tubes are present it is suggested to number them in the image.  Multiple images should be included split with a | sign, as follows: filename1.jpg|filename2.jpg

3.  This ensures that the measurement point with description "Test" will have four as_built images attached to it after importing. This works exactly the same for cover_images, mounting_point_images or any other type. Any as_built images present before the import will be overwritten by this new import. They will not be added.