Closed GoogleCodeExporter closed 9 years ago
Ben
I am going to add more logging. I just reviewed the code and it should be
accounting
for available and unoccupied and available and occupied by the other sex. I do
not
think I made any changes to that part and we were overlapping before with males
and
females. So I am guessing it probably has something do with the way I am
calculating
the area, not the polygons I am calculating
bob
Original comment by ran...@mwwb.net
on 21 May 2009 at 5:28
Bob,
I would be very surprised if the polygon area calculation was the problem. When
I
calculated the area of the suitable-unoccupied polygon only, it perfectly
matched
the area in the home range log as available. My guess would be the issue arose
when
we made the change to the dissolve by multiple fields where we kept occupied
male
and occupied female instead of just using a clever trick to assign a single
field as
available. Hopefully the extra logging will help us sort this out.
Ben
Original comment by bpa...@purdue.edu
on 21 May 2009 at 5:56
Original comment by ran...@mwwb.net
on 1 Aug 2009 at 8:35
I think this was handled while down in Perdue the weekend of Aug 1/2
Original comment by ran...@mwwb.net
on 7 Aug 2009 at 3:48
I believe this was fixed by dissolving area based on suitability and
occupied-same-
sex.
Original comment by bpa...@purdue.edu
on 5 Oct 2009 at 7:20
Original issue reported on code.google.com by
bpa...@purdue.edu
on 21 May 2009 at 4:06Attachments: