Understanding length- versus area-based budgeting for activities
RIOS asks for costs of landscape activities which can be input as an amount per unit length or as an amount per unit area. I'm dealing with activities (bunds, terracing, trenching, etc) which have different costs based on the slope (since steeper slopes require more closely spaced structures). I often know the cost of building these structures for a unit length.
My question is, when RIOS deals with a unit length, how does it (later) convert this to a cost per area (the output shows values in cost per hectare). Does it assume that a length-based activities can only traverse a pixel once?
Thanks for any enlightenment!
Post edited by jelliso on