Irrigation traditions, roots of modern irrigation knowledge Online publication date: Sun, 13-Jul-2003
by M.W. Ertsen
International Journal of Technology, Policy and Management (IJTPM), Vol. 2, No. 4, 2002
Abstract: The paper illustrates how different irrigation artefacts can be understood as outcomes of underlying, historically grown, colonial technological regimes, and how these regimes still determine modern irrigation practice. The discussion centres around water discharge measurement structures in British India and the Netherlands East Indies. Adjustability is the key difference between the two areas. In general, the British structures were not continuously adjustable, as they were designed for constant flow. Most British designs were based on famine relief, spreading water thinly over a vast area to supplement rainfall. Operation should be simple. The British needed a discharge structure, delivering a fixed flow without the need for regular adjustment. The Dutch needed an adjustable discharge measurement structure. The mutual presence of sugar cane and peasant crops (mostly rice) in the same irrigated area is a primary cause, as areas of sugar cane and rice fluctuated over the seasons and years. Despite the different circumstances in independent India and Indonesia, colonial irrigation design rules (regimes) still do structure to a considerable extent irrigation activities of engineers and irrigators.
Online publication date: Sun, 13-Jul-2003
If you are not a subscriber and you just want to read the full contents of this article, buy online access here.Complimentary Subscribers, Editors or Members of the Editorial Board of the International Journal of Technology, Policy and Management (IJTPM):
Login with your Inderscience username and password:
Want to subscribe?
A subscription gives you complete access to all articles in the current issue, as well as to all articles in the previous three years (where applicable). See our Orders page to subscribe.
If you still need assistance, please email firstname.lastname@example.org