Tuesday, December 11, 2018
Friday, December 7, 2018
Blog Post 6
After a very stressful week with very confusing and hard to work with data, I finally have some substantial progress made on what will go on my final poster.
Kernel density finally worked after many issues on my computer led to Dr. M having to do it on her computer for me (thank you!!!).
I now have three kernel density rasters showing the density of peregrine falcon sightings in 2017 (based on birder citizen- science program "Ebird" data) for winter only, summer only, and year round data. I then overlaid the USGS maps of the winter, summer, and year round ranges to see if the sighting locations lined up with the expected range. I have been messing around with the colors to try and find the best way of portraying the overlap (or lack thereof) between the two layers. I might consider doing a raster analysis now that we have done chapter 11 to identify the areas where the two areas do actually overlap, and what percentage of the range that actually adds up to. There's lots more to do but I feel ore on track now!
Kernel density finally worked after many issues on my computer led to Dr. M having to do it on her computer for me (thank you!!!).
I now have three kernel density rasters showing the density of peregrine falcon sightings in 2017 (based on birder citizen- science program "Ebird" data) for winter only, summer only, and year round data. I then overlaid the USGS maps of the winter, summer, and year round ranges to see if the sighting locations lined up with the expected range. I have been messing around with the colors to try and find the best way of portraying the overlap (or lack thereof) between the two layers. I might consider doing a raster analysis now that we have done chapter 11 to identify the areas where the two areas do actually overlap, and what percentage of the range that actually adds up to. There's lots more to do but I feel ore on track now!
Saturday, December 1, 2018
Blog Post 5
This week I have been working on getting my data from ebird (that finally arrived) into ArcMap. I have run into several problems in this process. First it was taking far too long to get the map to draw and the program kept crashing. Then I went through the excel sheet and selected only 2017 sightings/ observations and that worked much more quickly. I have been able to link the excel sheet by adding X,Y data, but there are always a few points misplotted. The points pretty much make up the shape of the US, including Alaska and Hawaii, but there are always a few points that look like they would be across the Atlantic somewhere in Europe, which I know is incorrect because this is only US data. So I don't know if this is an issue within ArcMap drawing the points, or if this is an issue within the ebird data that is incorrect, and I am not sure if I should take it out becuase I don't know how it will affect my overall data.
The next problem I keep running into is that I cannot export my data from the temporary event that is created when you link XY data into a feature class that way I can manipulate and work with the data later in my mapping. I did some googling, and I found that some of the error messages I got when I tried to export the data may be because the values in the table may not be accepted. So I went through the excel sheet and changed all of the values in the field titles to 10 characters no spaces or special characters, and I got rid of any fields I don't need in the table. I also changed everything to text format, except latitude and longitude, which would not draw when in text format. Even after all this, I still cannot export the data into a feature class, and I cannot figure out anything else I am doing wrong. I get errors saying the table could not be found, and that the data can't be exported. If anyone has any ideas about someting I may be missing, please let me know.
My nect step when I (hopefully) get the data to export is to create a density map using kernel density in ArcMap, which is something I am going to have to do a bit of research into how to do.
The next problem I keep running into is that I cannot export my data from the temporary event that is created when you link XY data into a feature class that way I can manipulate and work with the data later in my mapping. I did some googling, and I found that some of the error messages I got when I tried to export the data may be because the values in the table may not be accepted. So I went through the excel sheet and changed all of the values in the field titles to 10 characters no spaces or special characters, and I got rid of any fields I don't need in the table. I also changed everything to text format, except latitude and longitude, which would not draw when in text format. Even after all this, I still cannot export the data into a feature class, and I cannot figure out anything else I am doing wrong. I get errors saying the table could not be found, and that the data can't be exported. If anyone has any ideas about someting I may be missing, please let me know.
My nect step when I (hopefully) get the data to export is to create a density map using kernel density in ArcMap, which is something I am going to have to do a bit of research into how to do.
Subscribe to:
Comments (Atom)