8.4 Permit Tools
Level of expertise required for this Chapter: Intermediate; specifically for LUPMIS @ TCPD
Note: Chapters 8.4 - 8.6 describe databases, which are directly linked to the GIS and form part of the entire LUPMIS. They store data about permits, census, and tax revenue generation in future.
Note: Features described below are not part of standard Map Maker. They have been developed at LUPMP in Ghana to handle parcels at Local Plan level (Planning Permit, Building Permit, drawing of parcels). For external technical inquiries, feel free to contact us ( email).
Land use planning is primarily the formulation of plans at different levels (scales and detail), i.e. the collection and compilation of data, preparation of the 'best options' for future land uses and selection of the optimal land use in a political process with involvement of all parties in a legal setting.
The process of issuing permits for the implementation of land use plans is a well-defined 'business' process, not like the ‘creative’ formulation of plans. Permits form part of the land administration, where land sector agencies have their individual mandates and information systems (only to mention: LIS, UMLIS).
In LUPMIS, a Permit Database has been developed to support the administration and issuance of permits by TCPD:
- Planning Permits allow the applicant to develop the land (parcel) according to the Structure Plan and Local Plan. These plans define land use zones, which legally allow, prohibit or restrict specified land uses. The Planning Permit gives the right to use land accordingly, for example to build a residence, a warehouse, a hotel.
- Building Permits allow the applicant to build a structure ('building') with well-defined dimensions, functions, access. The primary purposes are the structural integrity and health, engineering and sanitation aspects. It has to be based on the Planning Permit (which again is based on the Structure Plan and Local Plan), but includes more detailed features, to be approved by engineers and architects.
The Permit Database serves three functions:
A) It works as a database (DBMS) to enter, store and retrieve permit data (particularly, Planning Permits). This includes, for example:
Date of application
Object of request
Name of applicant
Data can be selected and printed in different formats.
B) It works as a quality control (QC) tool for GIS data, particularly for Local Plan maps. This includes checks for:
Redundancy of UPN
C) In combination of DBMS and GIS data, it works as a production tool to print permits.
- - - - -
In technical terms, it is built on a robust, transparent technology, which – as the highest goal of sustainability and technology transfer – can be easily installed and taught both on a user and future developers level.
- - - -
Following assumptions are made for the Permit Database:
a) One person can apply on more than one parcel (for example, owner of multiple parcels)
b) One or two persons can apply for a parcel. One permit will be issued, no matter if one or two persons applied, i.e. one applicant and possibly one co-applicant. It will be a joint-application, if there are two applicants.
c) One Planning Permit can be requested and granted for more than one parcel (for example, estate development permit)
d) Only one Planning Permit can be applied for a parcel, not multiple Planning Permits
e) All parcels should follow the UPN system.
f) The LUPMIS - Permit Database is an inventory system, not a legal official instrument (at this stage).
g) The only legal documents are hardcopy permits, issued by TCPD, signed and stamped by an authorized person.
h) Scanning of legal hardcopy documents (either of the past or current) is not yet supported by the LUPMIS-Permit Database, but will be implemented at a later stage.
i) The process of issuing of Planning Permits, as granted by TCPD, does not confirm proof of ownership on the applicant.
- - - - -
The Permit Database consists of four main data tables ('A-tables') containing information about: