Hello,

I have a Collect Earth survey filled out using historical (e.g. 2016) imagery. Now I want to analyse more recent (e.g. 2018) imagery over the same samples sites (ie same grid), using obviously the same CE survey. Ideally, in Google Earth I would have a folder (saved in My Places) containing my 2016 filled-out survey (in green ticks, which I can click on to see how the 2016 CE survey/cards were filled out), and in Temporary Places the new empty CE survey (in red exclamation marks) ready for inspection with the new 2018 imagery. Obviously the two sampling grids are the same (must overlap).

I tried the following:

  1. In Google Earth, I opened the 2016 filled-out CE survey and saved (i.e. moved) the "Collect Earth Data" folder from "Temporary" to "My Places"
  2. In Collect, I have imported the XML file (generated by the filled-out 2016 survey) through the "Import Survey" function, changed the name of the survey, uploaded the same grid samples, and then exported a "new" CE survey (CEP file), thinking that this would create a new "empty" survey...
  3. In Collect Earth, I opened this file (through Tools > Proprieties > Projects > Load a new Project file) and loaded the new CEP project
  4. In Google Earth, the data is reloaded in the Temporary Places folder (overwriting existing data) but, despite showing the new name assigned in Collect, the survey is filled out and complete with green ticks.

A few questions for you:

  • Is this because my Collect Earth database (located in "...\AppData\Roaming\CollectEarth\collectEarthDatabase") is the same and project-independent?
  • How can I generate an empty CE survey from an existing one, without affecting the other project CE surveys I have saved in my database?
  • Is there a way to save (and visualise) an old filled-out CE survey on Google Earth, while working on and filling out another survey based on the same grid sites? So that I can look at how the 2016 survey was filled out and ensure consistency for my 2018 assessment?
  • When the 2018 assessment is complete, what is the best way to compare results from the 2016 and 2018 surveys? I know I could create summary charts and stats in Saiku of the CE survey indicators for each individual survey and then manually compare them, but I was wondering if there was a dedicated procedure to assess change by comparing the results between two differetn surveys.

Any quick suggestions / recommendation would be much appreciated. thanks a lot in advance, Simone

asked 27 Aug, 21:17

svaccari's gravatar image

svaccari
112
accept rate: 0%


Ciao Simone,

Answering the questions:

How can I generate an empty CE survey from an existing one, without affecting the other project CE surveys I have saved in my database?

Best way to do this is to import (in Collect Survey Designer) the survey you want to "copy" and then use the clone option. This way you will have both the original and the cloned version.

alt text

Is there a way to save (and visualize) an old filled-out CE survey on Google Earth, while working on and filling out another survey based on the same grid sites? So that I can look at how the 2016 survey was filled out and ensure consistency for my 2018 assessment?

Not really. For a case like that (where you just want to visualize the data already collected) the easiest solution is to export the data as CSV (Tools-Data Import/Export->Export data to CSV) and then drag and drop the CSV file to Google Earth! This will actually allow you to visualize all the data (maybe you can remove columns from the CSV that are not interesting for you as there can be many of them, aslo when you export choose the option to include labels so hat you can show those instead of the codes). Google Earth will ask you what are the latitude and longitude column (YCoordinate and XCoordinate) and if you want to apply a style. This way at least you can visualize the data easily.

When the 2018 assessment is complete, what is the best way to compare results from the 2016 and 2018 surveys? I know I could create summary charts and stats in Saiku of the CE survey indicators for each individual survey and then manually compare them, but I was wondering if there was a dedicated procedure to assess change by comparing the results between two different surveys

Sadly there is no silver bullet for this. If you had though of this from the beginning you would have included an extra attribute to the survey called "survey_year" (or similar). This "survey_year" attribute would also be marked as a "key attribute". This way you would end up with plots that have two key attributes. "id" and "survey_year". See example:

alt text

So now in your CSV files with the plot locations there will be for year 2016 these plots (for instance):

id,survey_year,YCoordinate,XCoordinate
1,2016,30,40
2,2016,30,41
3,2016,30,42

Then in 2018 when you repeat the assessment you chang ethe CSV files to reflect the new assessment year (so that they are stored as new rows in the database table)

id,survey_year,YCoordinate,XCoordinate
1,2018,30,40
2,2018,30,41
3,2018,30,42

When you finish, your database will have 6 plots for the survey. 3 for 2016 and 3 for 2018. Then you can use the "survey_year" attribute to split the data.

Truth being said, Saiku is not great to do the analysis when using this approach, so it would be better to use Excel or other. Saiku does not have a special function for matching by ID so it is a bit difficult for the goal of comparing specific changes inside a plot. If the aim is just to compare the aggregated data for 2016 and 2018 then it actually works quite well!

The main gain with this approach is that you have all the data in a single Database, and then it will be easier to reproduce every 2 years.

You can actually adapt your current survey to this approach:

  • Open the old survey CEP file in Collect Earth and import all the data from 2016.
  • In Collect Earth Survey Designer edit the old survey to add the "survey_year" attribute (but DO NOT set it as "key attribute" )
  • Export the survey as CEP and open it again in Collect Earth
  • Export the data from Collect Earth as CSV
  • Edit the resulting CSV and keep only the id field, add another column called survey_year and fill every cell with 2016
  • Go to Tools-Data Import/Export->Update current records using CSV and use this new CSV file that you just edited. After this the plots will have the value "2016" in the new attribute.
  • Now go back to Collect Survey Designer and change the "survey_year" attribute to make it "Key" attribute (in the left panel both id and survey_year have a key icon)
  • Edit the CSV files with the plot locations and add an extra column to the right of id (important that the order is right so first column is id and second is survey year). Generate a CSV file with plots with 2016 and another one with plots for 2018 (the IDs will be the same but you will have two records one for 201 and one for 2018)
  • Export the survey again as CEP file and open it in Collect Earth
  • Now in the Collect Earth Properties dialog you can open the CSV file for the year that you want to visualize (in case of the 2016 data) or to fill (in case of 2018 which you have no data for yet)

Let me know if you understood the process

permanent link

answered 28 Aug, 11:43

collectearth's gravatar image

collectearth ♦
64015
accept rate: 16%

edited 28 Aug, 15:49

Hi Simone,

I don't know if it will affect your assessment but note that there are inconsistent shifts between images in GoogleEarth, which could prevent you from comparing one plot to itself over time as it might not be exactly in the same place in 2016 and 2018.

Cheers,

Florence

permanent link

answered 31 Aug, 07:13

flandsberg's gravatar image

flandsberg
51113
accept rate: 0%

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×164

question asked: 27 Aug, 21:17

question was seen: 99 times

last updated: 31 Aug, 07:13