I receive many requests for modelling courses. At a time when I could not organise another course, I began sharing a series on the foundations a newcomer needs. My first point was that modelling is neither one software package nor a single skill. It is a way to understand complex systems, used in medicine, engineering, management and finance as well as several distinct environmental disciplines.
Choose a path with both your background and the market in mind
Before collecting software names, decide which environmental process you want to work with. Air, water, soil and noise applications have different scientific foundations, inputs and questions. Starting close to your education or existing work gives you something you can understand and evaluate.
Practical demand matters too. A project or employment market may lead you towards a discipline you had not initially chosen. I recommend balancing your existing foundation with the work you need to deliver, rather than assuming that every discipline can be mastered through a short course on an interface.
Water modelling is a broad field of its own
Environmental work creates many water-related questions: flooding and hydrology, hydraulics and drainage, water quality and groundwater. These subjects interact, but they are not one identical workflow under different names.
Someone with a civil engineering or hydrological background may find an accessible starting point in water and flood applications. The next question must still be specific: are we studying runoff, flow in a channel or pollutant transport? That changes the required variables, evidence, model construction and evaluation.
Air and noise applications follow different project questions
Air dispersion appears in assessments of industrial projects, power stations, factories, generators and stacks. It requires understanding emissions, source conditions, meteorology, terrain and receptors before interpreting the calculated concentrations or other outputs.
Noise modelling appears in construction, roads, industrial facilities, generators and outdoor air-conditioning units, among other settings. Source characteristics, propagation and relevant receptors have to be understood in acoustic terms. Those differences are why I do not treat “learning modelling” as finding one package that will serve every discipline.
Ask the questions that come before software selection
Instead of beginning only with “Which program should I learn?”, I ask what I need to understand, why the calculation is being made, what data it requires and what the client or reviewer expects to receive. These answers define the study before the interface is opened.
Following software steps can produce values and maps without giving the user the ability to defend the method or explain a changed result. Trying buttons alone is not a complete learning approach. Theory and data knowledge make experimentation useful and help separate an execution problem from a weak study assumption.
The learning sequence I recommend
Start with the discipline and process, then the scientific basis of the model, then the necessary data, units and sources. Learn the appropriate software after those foundations. Each interface choice can then be connected to something understandable, rather than memorised as a sequence of clicks.
Next, work through clear case studies, preferably grounded in real situations whose inputs and purpose are known. Finally, practise the report: method selection, processing, assumptions, results and limitations. Guidance on model evaluation links suitability to the application purpose and the evidence used to evaluate it. [1]
Five groups that help explain a model
I introduce external drivers, state variables, mathematical relationships, system parameters and physical or reference constants as a teaching framework. They help explain what is being supplied, what is being calculated and how the calculation connects them.
In dispersion work, concentration at a receptor might be the variable, wind an external influence and stack height a source parameter. The model formulation connects them to the output. Recognising those roles is more useful than treating a model as a black box that accepts files and generates a map.
Develop depth without trying to master everything at once
Begin with one relevant discipline and build it carefully. Someone coordinating impact assessments also benefits from understanding the fundamentals of air, water and noise even without specialising in all three. That knowledge supports scoping, discussions with specialists and review of their work.
The series I began was intended to share methods, tools, datasets and applications and create room for discussion. I still measure progress less by the number of programs a person can open than by their ability to explain why a study was built in a particular way and what its results mean.
References & original writing
Adapted and expanded from the author’s LinkedIn writing. Technical references are listed below.
