# data[].attributes.body
Use this flowchart to help guide you: https://ele.exeter.ac.uk/mod/resource/view.php?id=3641446

# data[].attributes.body
Do we need to include installing packages, loading the libraries, and loading the data into our R Markdown?

Also on the assessment brief I see that it says for the R Markdown there is a word count of 1000 words, is this for the actually code of the markdown or the headers and code labels?

Thank you.

# data[].attributes.body
The QGIS point data provided for each individual only displays the deployment ID and date. If we wanted to look at temperature by month for example, and display that on our QGIS map, is there a way of including the temperature in the point data, and would you suggest how to do this? Or would you recommend any online data archives with/to create shapefiles/rasters to display the temperature on our maps?

Thank you.

# data[].attributes.body
If we choose to do a QR code for the bibliography, should we also submit a copy in a word doc in case it doesn't work? Also, do we reference the sources of map data such as GEBCO?

Thanks :)

# data[].attributes.body
I understand we need to include an R Markdown for analysing the depth data, if we have used a method (such as the one provided in the spatial practical Exercise 12) to import SST data to then display on our maps in QGIS, should we create a separate R Markdown document for this separate Figure on our poster?

# data[].attributes.body
I am interested in using more tracking data in for my work but I what I am interested in requires depth data that cannot be figured out from the paper alone and I can't seem to find much other relevant tracking data. Is there any way that more data from the (turtle) paper could be made available or would I need to focus on something else? Thank you

# data[].attributes.body
Is there anywhere we can get historical shipping data for free? I would really like to add boat traffic from the last year but most of the sources I have found require a paid subscription. Thanks

# data[].attributes.body
when I upload a polygon map the CRS is for different to my downloaded plots so it doesn’t align properly, it’s not letting my change this in QGIS?

# data[].attributes.body
Would it be appropriate/acceptable to just state in the header/code description that for example the process Steps 1-8 would be repeated for each file in the R Markdown, or do we have to repeat the same code for each file (since there are 3 sets of tracking data which we will be processing the same way). If we are stating that it will be the same code for the other files, how and where would you suggest to insert this into our Markdown document?

Many thanks.

# data[].attributes.body
when displaying different data analyses in our poster for the dive data, should we combine all 3 datasets given to show one large trend (i.e. the three separate turtle datasets), or can we pick and choose datasets to support our findings

# data[].attributes.body
In the markdown, do we include things that didn't work or only the process to make graphs that we used? Some things I started, had problems with and so moved on to other ideas.

Also, should we silence the code for making our graphs or will you want to see that?

Thanks

# data[].attributes.body
are you aware of anywhere i can access marine plastic data that could be used?

# data[].attributes.body
I'm trying to use ERDDAP to bring environmental variables into my poster but it keeps crashing my RStudio. Are there any other suggestions to download environmental variables?

# data[].attributes.body
Do we need to use all the data provided in the .tab files, e.g. time, depth, temperature, and date variables?

Could we just look at specific relationships between two of these variables? or maybe just look at a smaller range of the data e.g. a specific range of dates?

Thank you,

# data[].attributes.body
the chlorophyll data mentioned in exercise 12 of the spatial exercise seems to be gone, are there any oher places i can get this from? Thanks

# data[].attributes.body
How specific should we be in our annotations in our markdown, for example should we explain the functions in each line of code and what they do?

Also since the plot creation using ggplot is a long continuous piece of code, do we just describe each function/lines of code before the large code chunk?

Thanks you.

# data[].attributes.body
I have used AI lots for coding and GIS - is it possible to just give a statement like 'AI was used extensively for coding to give freedom to develop and troubleshoot code etc' rather than providing all the prompts as this would be incredibly long?

# data[].attributes.body
the assessment brief specified to 'find something in the data we haven't seen before' - if we interpret a novel trend and find reasoning behind it, does it matter if it could be wrong? will we be marked down? Or is it the process behind the interpretation that we will be marked on. I.e. animals on this day did x... this could be due to y...

this particularly refers to the future direction section, finding something that hasn't been looked into before for instance

# data[].attributes.body
For posters, do they need to have a dedicated section for "discussion" / linking results to literature?

Could "discussion/literature" be intermingled with the plot/results section it relates to?

# data[].attributes.body
Are we assuming that our data has already been prepared, so we don't need to clean it, if not, for light geo data, what observation scores should we include/not include, is there instructions available on how to clean light geolocation in particular

# data[].attributes.body
Is the temperature data we have been given regarding the temperature of the water in the specific location the animal was present, or the sea surface temperature directly above the location of the animal