OpenCADIrrigation manual
How the app works, chapter by chapter. The README says what OpenCADIrrigation is; this manual is maintained in English, with a Portuguese translation in pt-BR/. Contributing, the editorial rule and the release checklist are in CONTRIBUTING.md.
- Five-minute start: open the app, the example gallery, the URL parameters
- Design workflow: from the area to the reports, step by step
- Interface: layout, menus, compact layout and keyboard shortcuts
- Drawing and editing: entities, snaps, selection, transformations, blocks, layers
- Hydraulic network: hydraulic items, connection rules, generators, automatic design
- Component catalogue: pipes, emitters, valves, pumps, prices and manufacturer packs
- Terrain: contours, spot heights, the terrain model, online elevation
- Calculation and sizing: parameters, calculation steps, design check and assistant, analyses
- Agronomy and irrigation scheduling: daily water balance, irrigation programme, runoff, fertigation by stage, field uniformity, user crops
- Power, water and machines: pump house electrics, solar pumping, water quality, two-wire, several pivots, travellers and furrows
- AI assistant: what the optional assistant does, what it sends and how it is controlled
- Reports, plotting and export: reports panel, PDF sheets, quote, exports
- Title block and technical documents: title block, datum, document packages, permit table, memorial, O&M plan, budget, life-cycle cost
- File formats: the project file and every import and export format
- Storage, privacy and network access: what stays in the browser, what goes out and to whom
- Languages and site: the 20 languages, the site, the offline start and the hosting
- Code architecture: the source tree and the design decisions
- Development and tests: commands, how to extend, what every test guarantees
- Known limitations and roadmap: what the app does not do yet
- References: standards, books and papers behind the engine
- Licence, third-party components and data: MIT licence, the components and the data sources
The technical study behind the engine is docs/TECHNICAL_STUDY.md; the engine API is docs/API.md.
Open the app