01:25 I can accept rounding to the nearest hundredth but estimation seems fraught with problems. I saw a method of doing this not too long ago that basically made rounding errors all but cancel out. In your example, you have rounding errors of +.004, -.003, and -.002 for a total of -.001. That doesn't seem unreasonable. Yeah, this specific case, but still... (I'm from an engineering background and the practice in a lot of areas is that you never try to estimate beyond the precision of the gradations of your instrument because you can never do so accurately. Even mathematical interpolation is often frowned upon.)
A concept which could be better explained is to what decimal place you “publish” values. Most plan sets and most published datum report to 2 decimal places. If you will accept rounding, then why not estimate to the thousandths during the course of your work, your notes, your data (or if you don’t like the word estimate, lets call it: take a reading to a higher degree of accuracy- because no matter how you slice it a reading to the thousandths will be tighter than a numerical value rounded at every reading) but then when you publish, publish to 2 decimal places. Then you will have taken tighter readings throughout and your final rounding (which you already believe in) will be satiated upon publishing. I also only publish to 2 decimal places because what subsequent trade will even have the equipment to perform worth tighter than the hundredths place or two decimal places. Just so you know, I’m not being sarcastic with you, this is my actual practice. Perform work to the thousandths, keep the figures extremely tight throughout- and then publish to 2 decimal places. As an engineer, dont you sometimes use coordinates or other values to the highest reported decimal place in CAD or in a CSV file, even though the methods of recording likely don’t warrant that thousandth? Because the instrument, CAD and CSV exports estimated that 3rd or even 4th decimal place. Why not take advantage of it when your eyeball is capable of the same?
This app is called GoodNotes, its on the IPad. You can create or download templates for any type of note taking, and I love the laser pointer oand drawing features for presentations. It’s been a game changer for me.
I like the way you describe how to properly layout the book, steps in the math, checks. Great video! Keep 'em coming!
Thank you!
This video helped me solve a practice problem during my NCEES FS exam review. Very cool.
That's awesome feedback, glad to help!
Greatly appreciate this video. Been watching a lot of surveying videos recently. This is by far the best explanation of survey notation! Thank you!
Brandon, long time no see. We're all ready for a new video!
New content is up! Sorry for the break, just a little traveling, but I'm back and ready to go!
Pegging a Level, new video coming in hot!
Fantástico, thank you!!!!!!
where can I find the good notes template you used for the field notes? I could use it for practice 👍
I actually made this one, but I’d be happy to send it to you. Shoot me your email address?
i can see that 1 million like happening soon on your outro keep believingingini
@@nejendary Thank you!
01:25 I can accept rounding to the nearest hundredth but estimation seems fraught with problems. I saw a method of doing this not too long ago that basically made rounding errors all but cancel out. In your example, you have rounding errors of +.004, -.003, and -.002 for a total of -.001. That doesn't seem unreasonable. Yeah, this specific case, but still...
(I'm from an engineering background and the practice in a lot of areas is that you never try to estimate beyond the precision of the gradations of your instrument because you can never do so accurately. Even mathematical interpolation is often frowned upon.)
A concept which could be better explained is to what decimal place you “publish” values. Most plan sets and most published datum report to 2 decimal places. If you will accept rounding, then why not estimate to the thousandths during the course of your work, your notes, your data (or if you don’t like the word estimate, lets call it: take a reading to a higher degree of accuracy- because no matter how you slice it a reading to the thousandths will be tighter than a numerical value rounded at every reading) but then when you publish, publish to 2 decimal places. Then you will have taken tighter readings throughout and your final rounding (which you already believe in) will be satiated upon publishing. I also only publish to 2 decimal places because what subsequent trade will even have the equipment to perform worth tighter than the hundredths place or two decimal places. Just so you know, I’m not being sarcastic with you, this is my actual practice. Perform work to the thousandths, keep the figures extremely tight throughout- and then publish to 2 decimal places. As an engineer, dont you sometimes use coordinates or other values to the highest reported decimal place in CAD or in a CSV file, even though the methods of recording likely don’t warrant that thousandth? Because the instrument, CAD and CSV exports estimated that 3rd or even 4th decimal place. Why not take advantage of it when your eyeball is capable of the same?
@@leansurvey8212 Das fair... Work out farther than you are to report then submit within project parameters. 👍
@@bwhog 👊
Awesome ❤
@@itssecret01 thank you!
Hey Dude, what name of this app?
This app is called GoodNotes, its on the IPad. You can create or download templates for any type of note taking, and I love the laser pointer oand drawing features for presentations. It’s been a game changer for me.
Send me some more tutorial I'm new
What topic are you looking for?