8.5 Permit Tools
Level of expertise required for this Chapter: Intermediate; specifically for LUPMIS @ TCPD
The Permit Database serves three functions:
Date of application
Object of request
Name of applicant
C) It works as a quality control (QC) tool for GIS data, particularly for Local Plan maps. This includes checks for:
Redundancy of UPN
- - - - -
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 more persons can apply for a parcel. One permit will be issued, no matter if one or more persons applied, i.e. one applicant and possibly one co-applicant.
c) An applicant can be supported by an agent.
d) One Planning Permit can be requested and granted for more than one parcel (for example, estate development permit).
e) Only one Planning Permit can be applied for a parcel, not multiple Planning Permits.
f) All parcels should follow the UPN system.
g) The LUPMIS - Permit Database is an inventory system, not a legal official instrument (at this stage).
h) The only legal documents are hardcopy permits, issued by TCPD, signed and stamped by an authorized person. These can be printed from LUPMIS (Permit Tools > Development Permit > Permit (document)).
i) Scanning of legal hardcopy documents (either of the past or current) is supported by the LUPMIS-Permit Database.
j) 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: