1. An Overview of the Social Tenure Domain Model (STDM) and the Planned Piloting in Amhara National Regional State (ANRS), Ethiopia
Workshop on Cadastral Index Mapping and Computerization for Speedy and Pro-poor Rural Land Administration in Ethiopia: Experience, Challenges and Prospects, May 2009
By Solomon A. Haile (GLTN/UN-HABITAT and Christian Lemmen (ITC/Dutch Cadastre)

2. Outline STDM Overview What is STDM? Why STDM?
STDM development process and status
Why piloting STDM in ANRS, Ethiopia?
Few words on STDM piloting in ANRS
Quick displays of the STDM interface
Conclusion

3. To introduce STDM to partners in ANRS/Ethiopia
Objective
To introduce STDM to partners in ANRS/Ethiopia
To facilitate smooth piloting and customization

4. STDM Overview What is STDM?
a multi-partner (GLTN, UN-HABITAT, ITC, FIG, WB) land information management software development initiative to support pro-poor land administration in an integrated framework
Why STDM? The need to provide pro-poor tools
Propriety LIMS solutions and coventional surveying hasn’t served the poor in informal, customary, small holder agric., etc areas where parcels are ‘untidy’, land rights are ‘messy’ with overlapping claims and tenures
To get around prohibitive costs
STDM is being developed with public resources by non-profit entities and based on open source methodology (no acquisition costs, no license fees, no upgrade fees, etc)

5. STDM Overview: what is STDM?
It is unconventional : all kinds of spatial units /property units; all kinds of rights and all types right holders
Parcel
Apartment
Building
Customary area
Groups of areas
Etc << can be extended >>
Quality labels
One Point - inside polygon
One point - street axes
Set of Lines
Polygon (low accuracy)
Polygon (high accuracy)
3D Volume
Etc << can be extended >>

6. Why pilot test STDN in ANRS?
STDM is a part of the support package that CIM partners are availing for consideration in ANRS/ Ethiopia
Conditions: STDM becomes a robust tool and gets local partners buy-in.
Agains this backdrop, the test can help
assess if current and forthcoming functionalities correspond to LIMS needs of users
determine the degree of customization required with regard to context (rural land administration /small holder agric), local language support
get a sense of users capabilities of partners’ staff at different levels in managing and using the software
get a sense of compatibility / complementarity with existing IT infrastructure, software

7. STDM development process and status
Informal ‘needs assessment’ through individual research
Why hasn’t parcel–based convetional LA taken off in SSA and much of the developing world?
why has implemeting land policies become a daunting challenge?
Documentation and communication LIMS experience acquired through normative advisory activities and working with professionals and communities of practice in the developing world
Building consensus and partnership around unmet needs in informal settlemts, customary and subsistence farming areas
Commissioning software development contract with ITC and having backsopping of partners like FIG

8. STDM development process and status
Conceptual design and internal review (ITC, GLTN/UN-HABITAT)
Functional design and internal review (ITC, GLTN/UN-HABITAT)
Technical design and internal review (ITC, GLTN/UN-HABITAT)
Prototype release, in-house testing and validation (ITC)
External peer-review of design outputs (FIG-led, but involving well known professionals)
Forthcoming
External (Field) testing (Ethiopia in small holder agric context; Namibia in informal settlement context; customary???
Peer-review of the prototype

9. An overview of the piloting
Installation of the software in client server mode (the server side tools include additional open source software like PostgreSQL, PostGIS, Tomcat; STDM also uses ILWIS platform for raster data management)
Data preparation, input, integration and management
Exiting alphnumeric data from ISLA
Newly acquired spatial data from the ongoing CIM
Training
Land administration on principles, processes and practices
Database management in STDM environment
end users training on STDM management and functionlities
Testing – both users as well as developers

10. Examples of STDM functionalities
Generate images for field work
Generate forms for field work
Scan images
Vectorise raster data
Record overlapping claims (for future possible adjudication)
Record and manage overlapping tenure
Link spatial and admin data
Aggregate parcels (e.g., into holdings)
Record history
Process – not modelled
Record, store and manage all types of source documents
Record info on data collectors, process managers

11. A leaf from the technical design

12. STDM Main Window

13. STDM: Navigation pane
Information Management section: define parameters to connect to the selected database, to define access rules, the working directory, Reference maps and data collectors.
Data Acquisition section:Input data in the database

14. Preferences tab: define the working directory and the connection to the database

15. Reference Maps tab: to define the geographic area and the imagery that belongs to it.

16. Natural Person Attributes
Person ID: official country ID of the person (i.e. burgerservicenummer/sofinummer in The Netherlands or Social Security Number SSN is the U.S.A. or Cédula de Ciudadanía in Colombia or Carteira de identidade in Brasil). (M)
Gender: natural person gender: male or female. (M)
First Name: natural person first name. (M)
Last Name: natural person family name. (M)
Street: street name or number
Postal code: postal code
City: name of city or region. (M)
Photograph: person’s photograph
Fingerprint: the scan of the person’s finger print
Signature: scan of the person’s signature.
Date Of Birth: natural person date of birth
Validity: date the record is input in the database. (M)
Until: date the record is not valid anymore.
(M) = Mandatory

17. Natural Person tab: create, search and edit data of natural persons

18. Non Natural Person tab: Create, search and edit data of non natural persons

19. Spatial Unit Attributes
Spatial Unit ID: identification number of the spatial unit. (M)
Field ID: identification number of the spatial unit given on the field. (M)
City: city or region where the spatial unit is located. (M)
Tax Amount: estimation of the tax that the spatial unit has to pay according to regulations of the country.
Value: estimation of spatial unit value
Calculated Area: approximate area of the spatial unit.
Spatial Unit Type: type of spatial unit to be selected from a number of options (point, line-based, text, sketch, building, ..). (M)
Type of Use: type of use of the spatial unit to be selected from a number of options (agricultural, living, ..)
Data Source: address path where the data source for the spatial unit is stored. To be selected from a browsing window. (M)
Photograph: scan or digital photograph of the spatial unit’s.
Validity: Date the record is input in the database. (M)
Until: date the record is not valid anymore

20. Source Document tab: create, edit and find source documents.

21. Spatial Unit tab: Create, edit and search spatial units
Base imagery
Supporting document

22. Spatial Unit: Georeferencing

23. Spatial Unit: Georeferencing (2) adding tie points

24. Spatial Unit: Digitizing

25. Conclusion
There is a LIMS gap that STDM is going to bridge in unconventional fashion and targetiing needs in hitherto unserved areas and unreached LA scope
Has a potential to integrate formal, informal, and customary land systems
Major software vendors has shown interest to collaborate on its further devlopment and seems to have endorsed the thinking behind STDM’s development.
Let us give it a try and see what WE CAN ACHIEVE!