[MUSIC] Hello again everyone, and welcome to the next milestone in our project based course. Now that you've made a plan and a proposal for what you want to learn about and analyze, it's time for you to plan out your analysis in more detail. Your proposal had a condensed version of your analysis, just so you could prove to yourself you had a viable analysis. But now it's time to think it through in detail. For most of you, this means you should take the time to put together a ModelBuilder model of at least some portion of your analysis. This gives you a canvas to think through and develop your algorithm with, but also a runable tool of its own to speed your data analysis and interpretation phase in the next milestone. Your model doesn't need to be complete and it doesn't even need to function fully. Instead, it should reflect time investment in determining exactly how to process your data to answer your questions. If ModelBuilder is only suitable for a portion of your analysis, that's fine, draft that portion. Or if it's suitable for your entire analysis, but incredibly complex, feel free to submit a portion of it. This step is designed for you to confirm that you have a viable way to proceed with your analysis, but not to be exhaustive. You'll do that in the next milestone when you analyze your data. We're building your project up in this way in order to prevent you from investing a ton of time, only to find out that your analysis had a critical and unresolvable error in it. By thinking through and laying out your analysis steps now, you'll validate your logic and ensure that you can complete your work. And if you use ModelBuilder, you'll save time in the next milestone. That brings me to the next piece, as you know not all workflows are completely suitable for ModelBuilder. Analyses like supervised image classification, requires significant human intervention to describe each class, even if a geoprocessing tool ultimately does the classification, that's fine. If you have a workflow that isn't suited to ModelBuilder, or ModelBuilder impedes your logical process for whatever reason, you can just submit another document that writes out in detail the steps and tools you expect to use in your analysis. Similar to the last milestone, you wouldn't necessarily develop a document for this step in a non-course project. But you would still want to plan your analysis to make sure you'll be able to proceed all the way through. As part of this milestone, I encourage you to spend some time looking at new geoprocessing tools you haven't used and at the ArcGIS desktop help. It might also be appropriate, in some cases, to look at tools in QGIS, Geospatial Modeling Environment, or other GIS systems. You're not limited to ArcGIS, but you do need a plan for the tools that will complete your analysis. And even though you don't need to run your data through your model, or make it functional just yet, this is a good time to put some test data through any new tools you find, in order to learn about how they work. This is the phase for exploration, but also confirmation of process. If you can't remember how to use ModelBuilder, the videos and resources in the rest of this milestone will help you. They are the videos that teach how to use it from previous courses. This is also a great time to reach out to your peers in the course with questions, suggestions for tools, and other workflow based questions. Lastly, I designed this milestone to take you only about a week, don't dwell too long on your model. The next phase is for the actual data analysis, and if your model needs testing, fixes, or enhancements, you'll do that then. For now, just get a reasonable plan for your workflow laid out. As with the last milestone, a document with more details is included in this lesson. Good luck and have fun.