This is a core issue that requires changes outside of any farm app. Let me give some context:
Land does not often change hands. It is often owned by a different party than the operator (and particularly the operator of ERPNext), most often a relative, but also rental relationships. The trouble with land in ERPNext is that it is a fixed asset that cannot be depreciated, per every accounting course I’ve ever taken. You can, however, add to its basis with things like drainage tile. I honestly think that handling land ownership is very low on the list of priorities for an ERPNext implementation. My solution has been to ignore it and work with the something closer to the mental map I have as a farmer - I think of things in ‘fields’ which is a problem RE nomenclature. In ERPNext (and well, HTML and programming generally) field means something different, so I’ve opted for the unambiguous “acreage”, which seems a little archaic to me in conversation but is fine in a mental map.
@sheerland installed a beta version and seems to think what I’ve got will also work for him in the context of his rice and sugarcane farms in the Philippines.