OK done with some thoughts. Data entry went fairly smoothly. I have some confusion about the rainfall values and the wind direction.
Actual important stuff:
- I tweaked the formatting so that lines alternate between white and grey - same as the weather data tables. That made it much easier for me to track the lines as I entered the date.
Nice. I look at spreadsheets everyday so it's not something that crosses my mind.
- At first the wind direction looked that it was entered as where the arrow in the data table pointed. For example -> was entered as East. Later I was not so sure. Need to clarify that. I believe the game expresses wind as "wind from the <direction>" and that is what we should do in the table. So, the previous data - was it entered as the arrows pointed or as wind from? Do you agree that we should capture it as wind from? I may need to adjust my entries for today depending on your answers and if we are entering wind from directions we should change the title - the column title was the other reason I entered as I did.
Not something I thought about. I always just assumed the arrows were the direction of the wind and therefore if it's pointing to the south east it means the wind is coming from the north west which you enter into the spreadsheet. If we've got it back to front consistently or the game uses something weird in this respect I can simply write a formula that will reverse the directions. I just hope I haven't fallen asleep for one of the days and entered something incorrectly.
- Rain fall ??? I entered the mm for the hour. For me those were all under 1mm mostly 0.1 or 0.2 but I see that none of the previous entries were done that way. I am not sure what those previous numbers were.
I gave up quickly worrying about the 0.1's etc. I just round it up to 1mm and refer back to main forecast icon to see if there is notable preciperttion or not for that hour. (Raindrop from the cloud icon). Remember these values are only for that hour, not for the whole day that most rainfall guages measure. The game simply doesn't have that level of fidelity when it comes to working out weather conditions, and I'm not about to worry about every 1/10th of preciperation to work out if the ground is muddy or wet.
- Three columns for the date - I'll convert that to an actual date value and switch the time format to 24 clock that should make data entry easier.
Please don't. It's set up like that for a reason. I'll be able to combine all these regions into one sheet at the end of this and creat a pivot table (like some of my other CM excel works) to make it easer for the reader to use without going through 1000 of rows of data.
Please do it's why I asked.
My idea of extreme cold is anything under 5 degree's celsius and I agree that 29 degrees isn't exactly warm where I'm from. I couldn't find a table anywhere detailing how BF interprets these fields but my understanding is that they assume it's a fixed temperature. For example when you make a scenario 'Cool' it will always assumed to be 12 degrees celsius or equivilent. Unsure if time of day or month plays a role in this. If my theory is correct then it's a simply case of changing the the values assigned on the reference sheet (using the fixed BF/CMx2 values as a mid-point) and everything else updates automatically. Just get the numbers right.
I've been meaning to test this but just brain dead after work at the moment and CM has been far from mind. Will make a concerted effort ASAP.
- I really like your work on ground conditions - very cool stuff.
This is going to be an excellent reference for people. Great idea.
Still need to tweak and view all the combinations as time goes on to see if it's 'accurate' but getting this one right is probably the most important given vehicles and bogging risk.
[/QUOTE]