Import from excel structure
Import Parcels from Excel
This functionality allows importing register of parcels in database if there is possibility to get these data from institution which register parcels, in excel file. It is situated in Agricultural holding > Parcels by clicking on button Import/export 
and selecting Import Parcels from Excel.
Farming opens following windows:
| Read XLS |
Import parcel that are not in database or that already exist but we will change them. This means that we import parcels from excel that we have prepare |
| Save XLS Template |
Export a properly structured Excel file for Parcels so that it can be filled by user and then imported back |
| Export Fields to XLS |
Export parcels from database to excel |
EXAMPLE:
1. step: Import parcel in empty database
If we want to import our parcels to the database, first we have to go via Save XLS Template and Farming will prepare empty excel file only with names of the columns.
2. step: Fill the excel file
After Farming created empty excel file, enter data regarding parcels.
| acField (FieldID) |
Enter the identification number of the Field. This data is obligatory. |
| acFieldName (Field Name) |
Enter the name of the Field. This data is not obligatory. |
| acFieldDeatailID (Field versionID) |
Enter details of the Field. If we skip this data Farming will automatically create Field Detail ID from Field ID. This data is not obligatory. |
| acFieldDetailName (Field version name) |
Enter Field version name. If we skip this data Farming will automatically create Field Detail ID from Field Name. If we don't have Field Name, this field should stay empty. This data is not obligatory.
|
| acActive (Active) |
Here we have to option F- False and T -True, regarding selected Field is active or not active. This is obligatory. |
| adValidFrom (ValidFrom) |
Enter the validity from Date. This is obligatory. |
| adValidTo(ValidTo) |
Enter the validity to date.Thi is obligatory in case if ewe import Field that is not valid any more.
|
| acCountry (Country) |
Enter the name of the country where the Field is situated. |
| acMunicipCode (Municio.Code) |
Some countries needs also municipality data. In this enter this data too. Before import, this field of the municipality code should be already in database. |
| anLatitude (Latitude) and anLongitude (Longitude) |
If we have data about Latitude and Longitude we can enter them. They are not obligatory |
| anKM(Distance km) |
This is the distance in km (kilometers) from agricultural Holding to the Field. Data is not obligatory. |
| acStatus (Status) |
We have five Status options:
C - Common use ( if we have field in use with other farmers)
L - Leased from ( we have field in lease)
O - Owned ( we are the owner of the field)
R - Leased to ( we give Filed in rent)
S - Sold ( the Filed is sold)
This data is not obligatory.
|
| anSetOfUse (Usage) |
This is an attribute which describes what is general use of the parcel. Set of Use is from country to country different. First, it should be checked if we there exists set of use (Land Use) in the database. After that proper set of use for the parcel should be checked within code books for Land use are in Administration Panel| Settings|Farming|Agronomy|Parcel Use. |
| anArea (Area (ha)) |
Enter the area of the field. |
| anAreaNet (AreaNet(ha)) |
At the moment this information is important only for SI (Slovenia). Enter the area of the Field which is covered with hail net. Other localizations can skip this field. |
| anAreaIrriagte (Irrigated(ha)) |
Enter the area of the Field which is irrigated. |
| anInclOver20 (are, inc.>20% (ha)) |
Enter the area of the Field which has more than 20% slope. |
| anAreaWaterWide (Water prot. (ha)) |
Certain areas of the Field can be important and for such there is special care of the legislative. Enter area of such area on the Field. |
| anAreaWaterNarrow (strict water port. (ha)) |
Enter the area that is in strict water protection. |
| anAreaNatura2000 (natura2000 (ha)) |
Enter the area which is within Natura 2000 program. |
| acIrrigateBesp (sprinkling) |
F- False (no sprinkling irrigation) or T - True (has sprinkling irrigation), or leave empty in this case program considered this as F-False |
| acIrrigateDrop (drop irrigation) |
F- False (no drop irrigation) or T - True (has drop irrigation) or we leave empty in this case program considered this as F-False |
| acIrrigateMicroBesp (Mickro-sprinkling) |
F- False (no micro-sprinkling) or T - True (has micro-sprinkling) or we leave empty in this case program considered this as F-False |
| acGrass (Grass cover) |
F- False (no grass cover) or T - True (has grass cover) or we leave empty in this case program considered this as F-False |
| acTerrace (Terrace) |
F- False (no terrace) and T - True (has terrace) or we leave empty in this case program considered this as F-False |
| anAreaNotMownPasture(Ummowedpasture(ha)) |
Enter area of unmoved pastures. This is now only in SI localization. This is for KOPOP action. If we use action that we need to leave unmoved pasture. |
| acWineOrigin(Wineorgin) |
Enter wine Origin. Previously such Wine origins should be already added in the database. |
| acBlock (Block) |
Enter the number of the block. Fields can be divided in blocks This data is not obligatory. |
| IsEcologically Important |
F- False (not important) and T - True (important) or we leave empty, or leave empty in this case program considered this as F-False. This is now only in SI loc. |
| anFarmingProdType (farming production type) |
Choose one of three possible options. Enter the number:
1. for Conventional Framing
2. for Redirected to Organic Farming
3. for Organic Farming
|
| acFruitType Use (single/Double purpose use 1,2) |
Choose one of two options:
1. Single purpose
2. Double purpose
|
3. Step: import parcel in database
After excel file is filled with parcels and all necessary information regarding parcels, go back and choose button Read XLS.
When clicked on the button Farming opens window as follows and user should navigate to the excel file with fields.
After Excel file is loaded modal UI (window) looks somewhat like this:
Every row represents field which will be uploaded to database.
4. Step: checking and correcting data
4.1 Checking data
First, all Fields should be selected:
Checking data starts when button 
. is pressed.
If everything is ok, no Note or Error shows. By pressing button 
these fields and data will be saved in database.
If we get any Error or Note, than we need to fix them. By Note and Error we have three options. Two of them are on right click and one is in column Action in dropdown. How to use them you can see in following content.
4.1.1 Copy value for selected cell from existing data
In case "Field already exist in database" and the values are different between data in database and data in excel we can fix each cell separately.
How we now that data are different?
The cells that have differences between data in database and data in excel are colored in blue.
Now, go one selected cells and by right mouse click choose Copy value for selected cell from existing data.
In this case the data from Table Existing Field Values will be copied to Fields for import. Just for selected cell. This option is only, if we agree with the fact that data that in database are ok and we just want to unify them. In case that we don't want to unify data, we will see below in point 4.1.3 and 4.1.4. what to do.
4.1.2 Copy missing values for selected rows from existing data
In this case the data from Table Existing Field Values will be copied to Fields for import. In this case all blue colored cells will be updated (whole row will be updated). This option is appropriate only if we agree with the fact that data in database is ok and we just want to unify them. In case that we don't want to unify data we will see below in point 4.1.3 and 4.1.4.
4.1.3 Override existing Field version
This options is in column Action in dropdown.
If we have field that is already in database and we have some chances that we want to change on Field, in this case we choose option from dropdown Override existing Field version.
In this example Valid to on Field_2006 will be changed from 30.6.2016 to 15.6.2016.
Before Override:
After import, were we choose option override:
4.1.4 Insert new Field version
If we want to insert new version of Field the column Filed version ID must be different from stored one in database and Valid from and valid to must be also different. If we have the same date, Farming will return error Overlapping of field.
Before inserting:
After import, when we insert new version:
