Home Trailcam Survey

Tennessee Deer Sporting & Deer Hunting Community Forum

Help Support TNDeer | Tennessee Deer:

grundsow

Well-Known Member
Joined
Apr 3, 2001
Messages
288
City & State/Province
Berks County, PA
In the spirit of the Hellickson trailcam survey article, I took the time to go thru every pic I had from Aug 1 - Oct 30. What do you think BSK? Anyone else have data to compare to?

Buck.......Doe.......Fawn
50.........26........37

Basically 2 buck for every doe

And 1.42 fawns per doe
 
Good questions.

Looking forward to estimating age structure of buck herd, just need to find some time.

Before the rut, I think I have 11 unique buck (much fewer than Hellickson I believe). Does this mean I have a very low deer density?

It�s funny, the data varied by month with September seeming most plausible. Remember this was not a baited survey, and wasn�t even intended to be counted in the first place. Going by memory here�

  • Aug the doe just seemed to be holed-up with fawns or something because I got few doe and even fewer fawns.
  • Sept I think had 11 unique buck and a near exact 1.0 buck for every doe, and something like 0.75 fawns per doe.
  • Oct I started to place a few cams over scrapes, and while I got both buck and doe at scrapes, once again the buck greatly outnumbered the doe. I believe this time it was due to neighboring buck on the cruise that skewed the buck count much higher (I still need to count unique buck for Oct).
Do these characteristics sound normal, and should Aug & Oct data be thrown out?

Should I be doing anything different with camera placement to improve accuracy?

How do you guys count all the deer when a group comes by on a trail? During daytime I capture them with a video clip, but I suspect my night pics may be missing some deer. Is this a problem?

What do you do with deer pics that can�t be confirmed as buck/doe/bb/fawn doe?
 
I try to make sure I have cameras covering as many types of set-ups as possible (or if only one or two cameras are being used, then move the cameras fequently). By using multiple set-up types, you run less risk of having the data heavily skewed in one direction. For example, feeding locations often get far more doe and fawn pics than what is actually in the herd. On the other hand, scrape pictures will be skewed towards bucks. Travel corridor pictures will be fairly evenly matched. Just make sure you're covering all these types of situations off and on all hunting season.

Honestly, I wouldn't worry about trying to calculate density numbers (deer per square mile). When photo-censusing properties under 1,000 acres, those numbers will be highly suspect due to shifting deer ranges throughout the seasons and the fact that deer have large ranges (are travelling on and off the property). But the numbers I would pay close attention to are the TRENDS in total unique bucks, sex ratio, fawn recruitment, and total deer censused (unique number of bucks + calculated number of does + calculated number of fawns). Those trends should be "real" (increasing or decreasing numbers mean exactly that).

And of most critical importance is to run the photo-census the same way every time. DON'T mix and match different densities of cameras or major changes in how you run the census. Even if the numbers aren't "accurate" the trends will be accurate.
 
And of most critical importance is to run the photo-census the same way every time.
I keep reading this, but what's the tolerance level on what�s acceptable?

In other words, must I develop a system where cam1 is always at location X during week Z? Or is there more wiggle room?

Couldn�t that type of a system be too constraining as maybe a tree blocks one of 2 major trails used in the survey. Or a situation where a trail leading to soybeans becomes grapes the next year? Or say, shifts in acorn abundance affect deer movement from year to year, etc.
 
As for keeping the data collection consistant, you don't need the cameras in the same locations on the same dates, just make sure you use a similar "mix" of locations at the same time of year each year. For instance, don't have them primarily on food plots during the rut one year, but have all of them on scrapes during the rut period the next year. That would produce very different data from year to year.

For my unbaited camera data, I primarily use a mix of food plot, trail, and bottleneck locations in September and early October. Once scrapes start showing up in October, I start switching some cameras to scrapes. During the rut month of November, I have half of the cameras on scrapes and half on food plots/trail/bottlenecks and keep them that way through mid-December, when I start switching all of them back to food plots/trails/bottlenecks until late January. I just make sure I use the same mix at the same time each year so that I don't skew the data TRENDS first established.

The way I collect my data, I have three primary data groups. I run a "baited" census in August (using salt licks as the bait). I keep the baited site data separate from the unbaited data, which is my second data set. The third data set is the first two combined.

As for data to look at, the month to month data is very interesting, but for management purposes I primarily look at annual changes in data. For unbaited data, here is some data graphs that look at total numbers of deer and sex/age of deer photographed over the full season:

PhotoPop1.jpg


PhotoPop2.jpg



When it comes to buck numbers and buck age structure, I look at this kind of data (and this data is baited and unbaited combined):

BuckAge.jpg


BuckAgeStructure.jpg
 
The type of "time-scale" data I analyze is when individual bucks first show up on camera, and how long they are photographed using the property. This is part of my research on seasonal shifting buck ranges and how that relates to individual properties.

When photo-censusing an individual property I find it EXTREMELY common that individual bucks come and go from the property at different and fairly predictable times of the late summer/fall/early winter. The following graph depicts these shifts. In the graph, each horizontal line is a unique buck, stacked bottom to top by the first to last unique buck identified, respectively. The date the line starts is the date the buck was first photographed and the end of the line is the date the bucks was last photographed. Green lines are yearling bucks and red lines are bucks 2 1/2 or older. Each "diamond" along a line is the date that buck was photographed.

BuckInventory.jpg



Two important things to learn from this type of data is that it is VERY common for "new" bucks to appear on a property at several times during the season that were not on the property in late summer and are not one the property at the end of the season. This means that those bucks would NOT have been picked up in a pre-season OR post-season baited census. The only way to know these bucks used the property during hunting season is to run season-long camera surveys. In fact, approximately 50% of the bucks we kill on my own property each year are NOT resident bucks, but bucks that shift onto the property during the rut.

Secondly, many more bucks use a property than hunters imagine, especially considering seasonal range-shifting and rut range-expansions/shifts. Now these bucks aren't "resident" bucks, but they are still manageable, harvestable bucks. In fact, on properties of a suare mile or less, it is very common to pick up more than double the number of new, unique bucks over the course of an entire season than were captured/censused in a pre-season baited census.
 
BSK,

I LOVE that last graph... basically you've summed up the entire season's pics in one graph. There's so much info both in trends as well as individual bucks there.

Did you come up with that graph yourself or adapt it from others you've seen?

IMO, that should be the standard photo census graph for whitetails!
 
I made that one up myself. I was just looking for a "graphic" way to depict what I needed to see, and that's what I came up with.
 
if i am reading your graph correctly, it is not uncommon for a new buck to show up that ends up staying on the property and becoming a "resident", correct? i would think better habitat, feed, or less pressure could cause this?
 
deerlawyer said:
if i am reading your graph correctly, it is not uncommon for a new buck to show up that ends up staying on the property and becoming a "resident", correct? i would think better habitat, feed, or less pressure could cause this?

When I first started working on this research, no "terms" existed for what I was seeing in the data, so I had to use something and came up with the terms "seasonal range-shifting" and "rut-season range-expanders/shifters." Although it was impossible to know what was really going on, all of my camera data from different locations kept displaying the same patterns from year to year, in that it appeared that bucks were displaying shifts in their ranges seasonally.

Below is a similar graph of just the older bucks (2 1/2 years old or older). I eliminated yearlings because they have some unique behaviors that confuse the issue (Yearling Buck Dispersal). This graph was produced for an article and so I removed all of the "diamond" data points for each date photographed to keep from confusing issues. I only displayed the first and last date a buck was photographed (or known to exist) on the property:

BuckPhotoInventory.jpg


Classically, I was finding two primary times that older bucks would suddenly appear or disappear from a ongoing photo-census of a property. The first occurs right at antler velvet shedding time. Some summer resident bucks would suddenly disappear from a property just at antler velvet shedding time, not to be seen again until the following summer. At the same time, "new" bucks would suddenly appear on the monitored property right at antler velvet shedding time. Many of these new" bucks would then stay for the entire fall hunting season. On occasion, I would see the same bucks appearing from year to year at this time. Again, from all appearances, it seemed as if these bucks would only use a given property during the fall months, and they would do so each year. I call the bucks that leave a property at antler velvet shedding time or appear on a property at that time "seasonal range-shifters," as they appear to change their normal ranges right at the same change of season each year. More recently, these seasonal changes in range have been confirmed as "normal" in GPS-collar studies of older bucks conducted at Remington Farms in Maryland. Sometimes bucks have completely different ranges from summer to fall, but most often they simply shift only part of their range. A percentage of their range remains unchanged, by they start using areas in fall they did not use at all in summer. For smaller properties, a particular buck may not cross the property at all in summer (his summer range is near or adjacent to the property, but he doesn't cross the property line hence won't be picked up in a summer census). Come fall he abandons part of his summer range and starts using a different area that is on the monitored property, hence suddenly appears in the census.

On every monitored property I have data for, some bucks shift away from the property at the end of the summer. Sometimes the property loses as much as 50% of their summer resident bucks, but 20-30% is more common. However, those bucks are usually replaced by bucks shifting into the property in fall, producing a "zero net change" in total bucks using the property from summer to fall. On the other hand, some properties lose fewer bucks after summer, yet still gain new bucks in fall, producing a net gain in total bucks from summer to fall.

The second major and consistent period where "new" bucks show up on camera censuses is around the rut. It has been known for a long time that bucks dramatically increase the size of their ranges around the rut, as they seek out estrus does. This "rut-season range-expansion" can bring a buck whose normal range is close to a monitored property (but doesn't cross the property line during most of the year) onto the property only during the rut as the buck expands the size of his range. These rut-season range-expanding bucks are generally only photographed for the peak of the rut on a given property (2-4 weeks). They expand their range onto the property just prior to the peak of the rut, use the property occasionally during peak breeding, and then disappear from the property as soon as peak breeding is over. Again, like seasonal shifts, I would often see the same buck appear on a property only during the peak of the rut from year to year. I assumed range expansions were the only reason for these bucks' appearances and disappearances, but some new GPS-collar research out of Auburn is finding something very interesting. With their GPS-collared older bucks, they are finding that some of these bucks have completely different ranges than normal during the rut. In essence, they actually completely leave their normal range and move to a different location for the rut, only to return back to their original range after the rut. So now I've expanded my definition of these bucks from rut-season range expanders to rut-season range expanders/shifters because some of the new bucks that appear only during the rut may actually be shifting their range onto monitored properties only during the breeding period instead of just expanding their range from an adjacent area.

Now "why" bucks make these seasonal and rut-season range shifts is unknown and will probably stay that way. It's impossible to get inside a buck�s head and figure out his decision making process. However, the most likely reason is access to needed/desired habitat. A particular type of habitat is needed/desired at only certain times of the year, hence is only used during particular seasons of the year.

The practical application of all this is twofold. First, bucks shift around during the year, hence the standard late-summer baited photo census will not pick up many bucks that will be using the monitored property during the hunting season. In addition, some of the summer censused bucks won't be using the property during the hunting season. That's why so many hunters report killing bucks during the hunting season that they didn't get pictures of on their census. This has caused many hunters to question the value of photo-censusing. They kill bucks they didn't get on their summer census thus assume the census was bad. Yet the reality is that buck they killed in fall that wasn't in the summer census literally wasn't on the property in the summer. He only uses the property in the fall. In addition, hunters that never see bucks during hunting season that were summer photo-censused think hunting pressure drove the buck totally nocturnal. That may be part of the problem, but some bucks that use a property all summer long and are picked up on summer photo censuses and/or are seen feeding in fields on the property literally are not on the property come fall hunting season. They may have shifted their range off the property come hunting season, and this would have occurred hunting pressure or no hunting pressure.

Second, many more bucks than just the summer resident photo-censused bucks can use an individual property over the course of an entire hunting season. Due to seasonal and rut-season range shifts/expansions, a single property may end up having three times the number of bucks as what was found in the summer census use the property at some point during hunting season and be "harvestable" bucks. For example, a property that identifies 10 unique bucks in summer may end up photo-censusing 30 different bucks using the property at some point over the course of an entire hunting season.

Too often I hear hunters/managers trying to calculate how many bucks they have to manage/hunt. The conversation always starts, "Let's see, I have half of a square mile, and the deer density is 30 deer per square mile--giving my 15 deer, and if 1/3 of those deer are bucks I've now got 5 bucks to work with...." Yet those type of calculations are a HUGE mistake. Not only is the hunter/manager forgetting that deer cross square-mile boundaries, they aren't accounting for seasonal range-shifts and rut-range expansions/shifts. As an example, the deer density in my area runs around 35 deer per square mile, and I have 3/4 of a square mile to work with. Theoretically that means I only have 26 deer to manage. Yet from the August 1st to January 31st I may photo census over 150 unique individual deer using my property at some point. Now at no time are all those deer on the property at the same time. In fact, the number using the property at any given point in time remains about the same. But over the course of 6 months, 150+ deer cross the property, making them "manageable" deer (they are using the resources of the property). That's why a single well-managed property can positively influence a large number of deer from the entire surrounding area. Now not all deer we census over 6 months are harvestable. Some were only on the property in summer and left the property before the hunting season opened. But still, the point is, many more deer�and especially bucks�cross a property and are manageable, harvestable animals than �deer densities� suggest. Deer, and especially bucks, move around quite a bit from season to season.
 
grundsow said:
That last graph tells a lot!

Was that made in Excel? Could you make that available for download so we can enter our own data?

It's an extremely convoluted conversion from Excel to PowerPoint. Not easy to accomplish at all.
 

Latest posts

Back
Top