DDS OF LANDS DEPARTMENT -

DDS OF LANDS DEPARTMENT SUPPLEMENTARY FEASIBILITY STUDY REPORT DAM REFERENCE

Ref. No. : T120 June, 2004 i Version : 1.0

Amendment History

Change Number

Revision Description

Pages Affected

Revision Number

Date


Ref. No. : T120 June, 2004 ii Version : 1.0

TABLE OF CONTENTS

3. APPENDIX.......................................................................................................................... 3.1-1

3.1 DAM REFERENCES................................................................................................... 3.1-1 3.1.1 Existing and Revised Workflow of Building CSU ............................................... 3.1-1

3.1.1.1 Existing workflow ............................................................................................ 3.1-1 3.1.1.2 Problems encountered....................................................................................... 3.1-4 3.1.1.3 Revised Workflow ............................................................................................ 3.1-5

3.1.1.3.1 Design and Construction Stage................................................................. 3.1-13 3.1.1.3.2 Post-Construction Stage............................................................................ 3.1-13 3.1.1.3.3 Demolition Stage (demolished layers DBLDG and DPOD) .................... 3.1-15

3.1.2 Existing and Revised Workflow of Lot CSU...................................................... 3.1-16 3.1.2.1 Existing Workflow.......................................................................................... 3.1-16 3.1.2.2 Problems encountered..................................................................................... 3.1-18 3.1.2.3 Revised Workflow .......................................................................................... 3.1-18

3.1.2.3.1 Creation/Re-grant ..................................................................................... 3.1-23 3.1.2.3.2 Land Transaction Registration.................................................................. 3.1-24 3.1.2.3.3 Subdivision ............................................................................................... 3.1-24 3.1.2.3.4 Surrender/Resumption .............................................................................. 3.1-25

3.1.3 Existing and Revised Workflow of Road Centreline CSU................................. 3.1-26 3.1.3.1 Existing Workflow.......................................................................................... 3.1-26 3.1.3.2 Problems encountered..................................................................................... 3.1-26 3.1.3.3 Revised Workflow .......................................................................................... 3.1-27

3.1.3.3.1 Construction of a New Road..................................................................... 3.1-29 3.1.3.3.2 Re-alignment, Extension of an Existing Road, or Change in Road

Information ............................................................................................... 3.1-30 3.1.3.3.3 Closing of an Existing Road Centreline CSU........................................... 3.1-31

3.1.4 Current and Recommended File Formats ........................................................... 3.1-32 3.1.4.1 Current File Formats....................................................................................... 3.1-32 3.1.4.2 Recommended File Formats ........................................................................... 3.1-33

3.1.5 Dissemination Option suggested in DAM.......................................................... 3.1-34 3.1.5.1 Recommended Data Dissemination Option.................................................... 3.1-34

3.1.6 Existing PLW data exchange process identified in DAM .................................. 3.1-36


Ref. No. : T120 June, 2004 3.1-1 Version : 1.0

3. APPENDIX

3.1 DAM REFERENCES

3.1.1 Existing and Revised Workflow of Building CSU

3.1.1.1 Existing workflow The existing workflow that describes the process of data exchange before CSU implementation is illustrated in the figures below. Examples of data exchanged in the five stages include:

(a) Planning Stage – master layout plan, development plan and planning application

(Figure 3.1.1.1-1); (b) Design Stage – building plan (Figure 3.1.1.1-2); (c) Construction Stage – approval of building plan, issue of Occupation Permits

(Figure 3.1.1.1-3);

(d) Post-Construction Stage – alteration notice (Figure 3.1.1.1-4); and

(e) Demolition Stage – application for demolition consent (Figure 3.1.1.1-5).

Figure 3.1.1.1-1 Existing Workflow in Planning Stage



Figure 3.1.1.1-2 Existing Workflow in Design and Construction Stage

Figure 3.1.1.1-3 Existing Workflow in Post Construction Stage (I)



Figure 3.1.1.1-4 Existing Workflow in Post-Construction Stage (II)



Figure 3.1.1.1-5 Existing Workflow in Demolition Stage

3.1.1.2 Problems encountered One key issue in the Building CSU was the alignment of the different Building definitions, currently adopted by PDs to meet their own business needs: (a) LandsD defines buildings as permanent building or structure of a size larger than

10m2 according to Basic Mapping Specification. (b) RVD defines buildings as ratable boundaries.

(c) BD defines buildings as attached structures sharing the same Means of Escape

(MOE).

(d) C&SD defines building as an independent structure, permanent or temporary, covered by a roof and enclosed by external walls extending from the foundation to the roof. It includes structures less than 10m2.

(e) PlanD’s definition of building aligns with that of LandsD’s.

(f) LR defines building as residential or commercial dwelling(s) belonging to one or

more owner committee. With the joint effort from all members of the Building sub-working group, the following key issues were resolved and the aligned requirement would be incorporated in the Building CSU specification.



(a) Physical meaning of buildings in Building CSU – In the context of Building CSU,

building will mean the tower and podium (podium is a containment with facilities for a designated purpose above ground). It will exclude underground structures (e.g. underground basement, underground oil tank) at the moment and the need for its inclusion in Building CSU would be further reviewed upon the completion of the Situation Analysis Review.

(b) Scope of Building CSU – It will include towers and podiums of all private buildings

and non-private buildings to the latest specification of B1000 which will be revised to include small size buildings and the surveying rule for closing the podium lines to form a polygon.

(c) Delineation rules for polygons of Building CSU – BD would soon implement a GIS

for BD’s business need. The existing rules in LandsD’s B1000 specification would be revised such that the revised rules would maintain a one to one mapping between BD’s and LandsD’s polygons for new private buildings (on implementation of Building CSU). Although BD would like the plan view of the polygons to follow the approved plan, PDs opined that the plan view to the survey specification of the existing B1000 specification would meet their business needs.

(d) Definitions of common attributes – Definition of synonyms terms were clarified

and agreed among PDs (e.g. building height etc.) Also existing workflow is revised to streamline the following processes: (a) Most PDs would require the podium information to be presented in spatial polygons.

However, since only podium line information is currently available from LandsD, these PDs would have to close the podium lines to form the polygons by themselves. Instead of repeating the exercise by each PD, the effort would be coordinated in the revised workflow and a mechanism would be designed for the updating of the Building CSU information throughout the life cycle of the Building CSU.

(b) The current workflow in the exchange of building information could only allow the

building information to be made available at a very late stage, e.g. after issuing Occupation Permits. Due to business need, individual PDs would have to approach developers/architects or relevant departments for the building information in the early stage of the building development. Instead of repeating the exercise by each PD, the effort would be coordinated in the revised workflow and a mechanism would be designed for the updating of the Building CSU information throughout the life cycle of the Building CSU.

3.1.1.3 Revised Workflow

The proposed workflow process will cover the data exchange in the following three stages: (a) Design and Construction Stage; (b) Post-Construction Stage; and



(c) Demolition Stage. The proposed workflow is illustrated by the chart below:



Figure 3.1.1.3-1 Future Workflow of Building CSU – Design and Construction Stage



Figure 3.1.1.3-2 Future Workflow of Building CSU - Post Construction Stage (1)



Figure 3.1.1.3-3 Future Workflow of Building CSU – Post-Construction Stage (2)



Figure 3.1.1.3-6 Future Workflow of Building CSU – Demolition Stage



3.1.1.3.1 Design and Construction Stage (a) In the early stage of the development, developers/PDs would exchange data e.g.

master layout plan etc for development pre-design. LandsD would base on the limited information and provide a tentative layout of the building polygons in the proposed layer. The polygons would be put on the appropriate proposed layers at the early stage of the development and are for indicative purposes only. There is no precise survey of the building layout. Data Users should note that not every building under design/construction can be registered in the CSU dataset due to limited information accessible by LandsD.

(b) BD is the statutory authority to approve building plans from private developments

whereas ArchSD is the architect/structural engineer of the client department. In the design stage, design plans of private developments are submitted to BD for review and approval.

(c) For government buildings (Category 4), once the plans are approved for

construction, ArchSD will submit their plans to LandsD, who is the Data Owner of the building polygons. LandsD would then assign CSU ID(s) and create the concerned Building Geographical Info record(s), which is of Proposed status, and Building Polygon record(s) to represent the building(s) contained in the plans (CSU01).

(d) For private buildings (Category 1), due to concern on copyrights of the building

plans, for the moment it may not be feasible for BD to pass the approved building plans to LandsD for mapping purpose before completion of the building development. After all, the sub-working group recognizes sharing approved building plans prior to issue of concerned OPs as room for future improvement in data exchange process. The issue may be resolved outside the DAM project scope, and the ongoing CSU maintenance committee may review the progress after initial implementation of DAM.

(e) Upon application for a provisional house number submitted by the developer, the

Building CSU will be assigned with a provisional house number by RVD. RVD will create Building Address record(s) under the concerned Building Geographical Info record (CSU02).

3.1.1.3.2 Post-Construction Stage

(a) When building construction of a private development (Category 1 buildings) is

completed/stage completed, BD will receive Occupation Permit (OP) application from developers. On approval of the application, BD will create the building polygons (on implementation of BD’s GIS) based on the approved building plans. Number of building polygons will be determined according to the latest revised B1000 specification, but BD will use their own rules to determine the shape of the building polygons. BD will contribute the OP and other structural information to CSU to form the concerned Building Structural Info, Building OP Info and Building Lot No in OP records (CSU03).

(b) Also, when the development comes to a stage when the building layout is



confirmed or when the physical building base/structure is seen on ground, the geometry that indicates the location of the building and number of polygons representing the development would be updated by LandsD. LandsD would perform an onsite survey of the work completed for all categories of buildings. LandsD will create a building polygon, or update the concerned proposed building polygon, based on the onsite survey to the latest B1000 specification. The CSU ID assigned during the Design and Construction Stage will be carried over to the Post-Construction Stage as far as possible (say, as long as the original label point is still within the active building polygon), or LandsD will assign a new CSU ID to the Building CSU when necessary. These polygons will be contributed to form the Building Polygon record for the CSU, the CSU status will be changed to Active, and surveyed address will be attached as Building Address record (CSU04).

(c) There is no strict chronological order between (a) and (b) (i.e. LDB04-6 and

BDB03-6). The former may occur before the latter for some buildings, but vice versa for some other buildings. For buildings with BD’s polygon created before the LandsD’s one, BD will pass their building polygons for LandsD’s reference in preparing the CSU polygon.

(d) After both Building Geographical Info record (with concerned Building Polygon)

and Building Structural Info record have been defined by LandsD and BD respectively, BD will do the mapping between the CSU polygon (Building Polygon record) and their departmental building polygon. BD can periodically check whether there are any BD polygons not yet linked with any CSU polygons (e.g. every time after collecting new changes from the CSU dataset) to complete the linking process. The linkage results form the Geo-Struct Mapping record(s) for the concerned CSU (CSU05).

(e) LandsD and BD will work together to maintain a 1-1 mapping between the two

records as far as possible. Designated personnel will be assigned from both departments to resolve the conflicts, if any, through channels like periodic meetings. According to discussion results, the concerned Building Geographical Info record (with the related Building Polygon) and/or Building Structural Info record may be merged/split during the resolution process and the corresponding Geo-Struct Mapping record(s) will be re-defined (CSU06). Those Building Structural Info records representing building structures not within the Building CSU scope (e.g. an underground building structure), hence without corresponding Building Geographical Info record, will be removed.

(f) On the other hand, as long as the CSU is changed to Active status, RVD can attach

confirmed address to the Building CSU, which will form the Building Address record(s).

(g) For Category 2, 3 & 5 buildings, after they are marked as Active, the corresponding

Data Owner (LandsD for Category 2 & 5, PlanD for Category 3) can then identify building category information and attach additional attributes to the CSU to form the concerned Building Structural Info record (CSU08, CSU09 & CSU11).

(h) For government buildings (Category 4), ArchSD will pass the as-built drawings to

LandsD after completion of building construction for LandsD’s reference in



delineating the active building polygon (ADB03). ArchSD can provide the category, completion year/month, number of storeys and approximate building top level information to the CSU together with the as-built drawings. For those buildings already registered in the CSU dataset (i.e. Building Geographical Info and Building Polygon records already created) in the Design and Construction Stage, ArchSD should quote the concerned CSU ID(s) also. The concerned Building Structural Info records can then be formed using the textual attributes provided by ArchSD (CSU10).

(i) Addition and alteration (A&A) works on private buildings (Category 1) may

require a new OP. If this occurs, BD will use the new OP information to form new Building OP Info record under the concerned Building Structural Info record. Since the linkage between BD and CSU polygons has already been built up in earlier stage (i.e. the concerned Geo-Struct Mapping records), the concerned CSU will be linked with the new OP eventually.

3.1.1.3.3 Demolition Stage (demolished layers DBLDG and DPOD)

(a) It is a statutory requirement that the demolition of a private building (Category 1)

should be approved by BD. On completion of the demolition, BD then receives a notification from the private developer. BD updates their database to include the demolition completion date, and forwards the information to LandsD (CSU13).

(b) For government buildings (Category 4), ArchSD will also record the completion of

demolition work and forwards the information to LandsD (CSU13).

(c) LandsD will update the Building CSU with the demolition completion date provided by BD or ArchSD. For those buildings which do not have the demolition completion dates supplied by ArchSD and BD, LandsD will field-verify the demolition, such as a field survey on site. Upon completion of the field survey, the CSU status will be changed to Demolished (CSU14).



3.1.2 Existing and Revised Workflow of Lot CSU

3.1.2.1 Existing Workflow

The existing workflow that describes the process of data exchange is illustrated in the following figures. There are three main stages discussed in the workflow: (a) Creation/ Re-grant Stage (Figure 3.1.2.1-1) (b) Subdivision Stage (Figure 3.1.2.1-2)

(c) Surrender/ Resumption Stage (Figure 3.1.2.1-3)

Figure 3.1.2.1-1 Existing Workflow of Lot in Creation and Re-grant Stage



Figure 3.1.2.1-2 Existing Workflow of Lot in Subdivision Stage

Figure 3.1.2.1-3 Existing Workflow of Lot in Surrender/Resumption Stage



3.1.2.2 Problems encountered One key issue encountered in establishing the Lot CSU is the definition of the lot description. Currently, BD, LandsD, RVD and LR have their own conventions for identifying the lots. BD, RVD and LR have predefined fields to store the lot type, lot number, sections, subsections and extensions in a structured manner, whereas LandsD uses a comma delimited format to handle virtually unlimited number of sections/subsections, R.P. and extensions. To better facilitate data exchanged between PDs, the Lot CSU sub-working group considers it as a potential improvement to maintain a 1:1 mapping between the conventions used by the two major stakeholders, namely LandsD and LR - by building a one-one mapping table between LandsD’s representation of Lot No. (as published in the C1000 library) and LR’s representation (PRN as in IRIS and the structural format currently used in LRS). Only those under the Lot CSU scope will be processed, hence obsolete Lot No. will not be matched. It is recommended to store the above-mentioned formats of Lot ID of LandsD and LR in the CSU dataset for easy reference by various Data Users in different systems: (a) LandsD’s structural format as being used in the L1000R/C1000 library - lot type

and lot number are stored in predefined fields, and virtually unlimited number of sections/subsections, R.P. and extensions are delimited by a comma and stored in one single field.

(b) LR’s structural format as being used in the Land Registration System (LRS) and to

be used as part of address identifier in the Integrated Registration Information System (IRIS) - lot type, lot number, not more than 4 sections plus 3 subsections, extensions and an indicator of peculiar lots are stored in predefined fields.

(c) LR’s Property Reference Number (PRN) to be adopted in IRIS - an 8-character

unique identifier of lot registers. (d) The full English lot description.

3.1.2.3 Revised Workflow

The proposed workflow process will cover the data exchange in the following four stages: (a) Creation/Re-grant; (b) Land Transaction Registration;

(c) Subdivision; and

(d) Surrender/Resumption

The proposed workflow is illustrated by the charts below:



Figure 3.1.2.3-1 Future Workflow of Lot CSU – Creation/Regrant (1)



Figure 3.1.2.3-2 Future Workflow of Lot CSU – Creation/Regrant (2) and Land Transaction Registration



Figure 3.1.2.3-3 Future Workflow of Lot CSU – Subdivision



Figure 3.1.2.3-4 Future Workflow of Lot CSU – Surrender/Resumption



3.1.2.3.1 Creation/Re-grant (a) LandsD creates the Lot record in L1000R for preparation of the land boundary plan

during processing land grant/sales/exchange/allocation etc. Lot ID in existing format (as mentioned in 3.1.2.2 (a) above) is captured into L1000R and to be printed on the lot boundary plan also. (LD03-04)

(b) The new lot information is not yet released to other departments through the C1000

library as the proposed lot information is still classified as restricted information until completion of executing the land grant/sales/exchange/allocation.

(c) LandsD requests for registration of a new lot at LR. (LD05)

(d) When registering this new lot into Lot Register, LR captures the Lot ID in all these

formats into Integrated Registration Information System (IRIS): (LR02)

(i) Property Reference Number (PRN) (system assigned);

(ii) The Lot ID in existing LRS structural format (i.e. the future IRIS address identifier format) as mentioned in 3.1.2.2 (b) above;

(iii) The Lot ID in LandsD’s L1000R/C1000 format as mentioned in 3.1.2.2 (a), which can be found from the lot boundary plan printout; and

(iv) The full lot description as printed on the land grant/sales/exchange/allocation document.

(e) LR contributes the new Lot Register information as well as the concerned land transaction of Memorial Day Book (MDB) record to CSU. Regarding the Lot Register information, Lot ID in all the four formats captured into IRIS (PRN, structural format as in LRS, C1000-format and full lot description) are included. Regarding MDB records, only those related to lot registers are included, while those related to sub-division registers (SDR) are outside the scope of the Lot CSU. (LR03)

(f) The data from LR are published in the Lot CSU dataset even before availability of

the concerned lot boundary so that other PDs notice the creation of a new lot in an earlier stage. (CSU01)

(g) Meanwhile, LandsD is informed by LR about completion of registering the new lot

through memo, on which the PRN of newly registered lot is shown for reference. It is recommended that this memo, which is addressed to LAO of LandsD, is also copied to SMO of LandsD to streamline the process. LandsD then updates L1000R, hence C1000 also, to move the lot record to the active layer and contribute the data to the CSU. The lot boundaries contributed by LandsD are identified by the Lot ID in C1000-format. (LD06)

(h) The lot boundary and land transaction information in the CSU dataset contributed

by LandsD and LR respectively are now linked up automatically through the C1000-format Lot ID. The link between the Land Info record and the Lot Register



record for the new lot is available in the Lot Register record contributed by LR in step (e) above. Upon importing these data into the CSU dataset, the Data Agent will also copy the link (i.e. the paired-up C1000 Lot ID and PRN) from the Lot Register record to the PRN data item of the associated Land Info record. (CSU02)

3.1.2.3.2 Land Transaction Registration

(a) After registering a new transaction on a Lot Register (but not an SDR), LR

contributes the information to CSU, which quotes the PRN of the concerned Lot Register. (LR06)

(b) The new land transaction information is linked up with the concerned Lot CSU

automatically through the PRN-format Lot ID. (CSU03)

3.1.2.3.3 Subdivision (a) LR processes registration of carving-out plan submitted by the lot owner. IRIS is

updated to create new Lot Register records for the sub-divided lots, and the original Lot Register is appended with closure remarks in IRIS. LR is also recommended to maintain relational links between the parent Lot Register and the subdivided Lot Registers in IRIS. (LR08)

(b) LR contributes the new Lot Registers information, as well as the carving-out land

transaction information (MDB record) to the CSU. The links between the parent lot and the subdivided lot, which are identified by PRNs, are contributed to the CSU also. Regarding the new Lot Registers information, Lot IDs are provided in PRN, structural format as in LRS and full lot description formats. (LR09) That is, LR will contribute the following data to the CSU dataset: (please refer to the Logical Data Model for System Interface document for detailed descriptions of these records such as field data type, field length and field description)

(i) Lot Register record, one for each subdivided lot - all data items except C1000 Lot ID

(ii) Memorial record regarding the registration of subdivision - all data items

(iii) Lot Register Memorial record(s) to link up the concerned Lot Register and Memorial records - all data items

(iv) Subdivision History records to link up the parent lot and all subdivided lots - all data items

(c) New CSUs for the sub-divided lots are created but without C1000-format Lot ID yet. (CSU04)

(d) Authorized land surveyor (ALS), who is appointed by the concerned lot owner,

submits the registered sub-division plan to LandsD for checking. (LD07)

(e) If checking is passed, LandsD will update C1000 to replace the original lot by



subdivided lots. In addition to the C1000-format, LandsD also enters the corresponding PRNs into their system. LandsD can search for the PRNs of the new subdivided lots through the parent lot from the linkage information provided by LR described in (b). (LD08)

(f) LandsD contributes the new lot boundaries to CSU, which are identified by Lot IDs

in both C1000-format and PRN-format. That is, LandsD will contribute the following data to the CSU dataset: (please refer to the Logical Data Model for System Interface document for detailed descriptions of these records such as field data type, field length and field description)

(i) Update the Status data item of the Land Info record for the parent lot

(ii) Add a new Land Info record for each subdivided lot (all data items filled in)

(iii) Add a new Lot Polygon/Overlap Lot Polygon record for each subdivided lot (all data items filled in)

(iv) Delete the Lot Polygon/Overlap Lot Polygon record of the original parent lot

(g) The new lot boundaries in the CSU dataset are linked up with the Lot Register and land transaction information from LR automatically through the PRN-format Lot ID. The link between the Land Info record and the Lot Register record for each subdivided lot is available in the Land Info record contributed by LandsD in step (f) above. Upon importing these data into the CSU dataset, the Data Agent will also copy the link (i.e. the paired-up C1000 Lot ID and PRN) from the Land Info record to the C1000 Lot ID data item of the associated Lot Register record. On the other hand, the original Lot CSU for the parent lot is marked as inactive. (CSU05)

3.1.2.3.4 Surrender/Resumption

(a) As in the existing environment, after execution of lot surrender/re-enter/resumption,

LR deactivates the concerned Lot Register in IRIS. (LR11) (b) LandsD removes the lot boundary of the concerned Lot from the C1000 Library and

mark the lot record as inactive. These changes, i.e. removal of lot boundary and change in status, are then contributed to CSU. (LD12)

(c) The concerned Lot CSU Status is changed to Inactive in the CSU dataset and its

boundary polygon is removed from the active layer (i.e. the concerned Lot Polygon/Overlap Lot Polygon record is removed). (CSU07)



3.1.3 Existing and Revised Workflow of Road Centreline CSU 3.1.3.1 Existing Workflow

The existing workflow that describes the process of data exchange of Road Centreline information is illustrated in the figure below. Detailed descriptions of individual processes are documented in Draft DAM1.

Figure 3.1.3.1-1 Existing Workflow in the exchange of Road Centreline Entity data

3.1.3.2 Problems encountered

There are limitations from the current single road centreline system which do not fully satisfy other departments’ needs, e.g. does not support route planning due to the absence of turntable, road direction information etc. Although TD is now developing a more sophisticated road network, with multiple road centreline and associated turntable under its Transport Information System (TIS), they will not be made available within the DAM timeframe. Thus, it is recommended to adopt LandsD’s single road centreline as the Road Centreline CSU, and when required, a new CSU can be created to accommodate the future TD’s multiple road centreline, which is more suitable for route planning purpose. In the context of the Road Centreline CSU and since there is need for LandsD to continue the maintenance of the existing single road centerline for other non PDs, it was agreed by the sub-working group that any change required for the CSU should be kept to a minimum,



so that effect to the non PDs would be reduced. Also effort put in the system revamping for CSU purpose would be better within the affordability of the LandsD. Hence, only minimal change to the workflow of Road Centreline is proposed. This includes: (a) Works departments and LandsD should collaborate in the gazette preparation

process and ensure no portion of any street would be left without a gazetted street name.

(b) LandsD would assign a Sub-ID for each road segment in addition to the Street Code

to ensure the uniqueness of the CSU ID.

3.1.3.3 Revised Workflow The proposed workflow is illustrated by the chart below:



Figure 3.1.3.3-1 Future Workflow of Road Centreline CSU



The workflow presented in Figure 3.1.3.3-1 describes the life cycle of the Road Centreline CSU. There are a number of events which will initiate a new or changed road centreline CSU record, including: (a) Construction of a new road; (b) Re-alignment, extension of an existing road, or change in road information; and

(c) Closing of an existing road.

The term “existing” used in this context implies the road already exists as a Road Centreline CSU. Updating of the Road Centreline CSU records will only be required if there are alterations to the attribute and spatial information of a road.

3.1.3.3.1 Construction of a New Road Planning Stage Road developers (HyD, TD, Land owners, etc.) carry out road projects planning before constructing a new road (ID: RD01). Design Stage The road construction design is carried out according to the road projects plan (ID: RD02). The Works departments (and their consultants) who are responsible for the design of new roads, will provide the design drawings in the agreed digital format(s) to LandsD as soon as the design is finalized. LandsD will then update the Proposed Road Layer in the Basic Mapping System accordingly (ID: LD01). (Note: the digital format is yet to be agreed, but the issue would be forwarded to CSWP Committee for follow up). Where the street requires a new name, a request for naming of the new road, with both English and Chinese names, proposed by government departments, district councils, rural committees or land property owners, is submitted to the street naming authority, LandsD (ID: LD02). The procedures and guidelines on the Naming and Gazetting of Street Names in Urban and NT are outlined in SMO Instruction Technical No. 2/2000, and are briefly described below: (a) The status of the street to be named would first be searched; (b) After identifying the appropriate government department or property owner

responsible for the subsequent erection of street name plates, LandsD will proceed with the street naming process;

(c) A draft gazette plan showing the location of the road concerned will be arranged by

LandsD, seeking comments from other government departments.

(d) With due consideration given to the comments received, a final decision will be made, and LandsD will notify the requestor of the decision and process the gazetting of the street name (ID: LD03).

(e) The government departments and LandsD should collaborate in the gazette



preparation process and ensure no portion of any street would be left without a gazetted street name.

Construction Stage After completing the new road construction, the road developer(s) will create a temporary road centreline in their data inventory (ID: RD03). LandsD will carry out a survey on the newly constructed road and update the Road layer in the BMS (ID: LD05). The Road Centreline CSU for the newly constructed road will be created with a CSU ID, and assigned with the textual attributes (ID: LD06 & LD04). GIS Map Update LandsD will update the Street layer and dispatch the Road Centrelines CSU to other PDs (ID: LD08). HyD, PlanD and other departments will update their departmental systems.

3.1.3.3.2 Re-alignment, Extension of an Existing Road, or Change in Road Information Planning Stage If an un-named street is designated with a new name, an existing street name has to be changed, or where a road, after removal, no longer exists due to road works or redevelopment, the corresponding new name will be created or deleted by way of a gazette notice (ID: LD02 & LD03). LandsD will modify and update the CSU record accordingly: (a) In the case when a new street name is assigned to an existing street (gazetted or

ungazetted) or to an un-named street, the corresponding English Name and Chinese Name in the Road Name entity will be updated.

(b) When the street is an ungazetted or un-named street, a new Street Code will need to

be assigned to the existing record in the Road Name entity, with corresponding amendments made to the Street Code in the Road Segment Layer and the Road Intersection Entity.

(c) Where a complete road (and associated road segments if applicable) no longer

exist(s) after permanent removal, due to road works or redevelopment, its record in the Road Name Entity will be deleted, including the corresponding records in the Road Intersection Entity, the corresponding arc feature(s) and relevant node(s) in the respective Road Segment and Road Intersection layers will be removed and updated accordingly.

GIS Map Update Where alterations are made to a road, LandsD will carry out a survey on the modified road and update the road data in BMS (ID: LD05). The Road Centreline CSU will be updated according to the survey data of the modified road (ID: LD06): (a) Road alterations include the following:

(i) an extension to an existing road;



(ii) shortening of an existing road; and

(iii) a street re-alignment;

(b) As a result from the road alternation, the geometry of the corresponding arc feature(s) and the node feature(s) in the Road Segment and Road Intersection layers have to be updated accordingly. The relevant textual attributes of the node feature(s), i.e., [Geo.Ref.Number] in the Road Intersection Layer and the Road Intersection Entity have to be updated as follow:

(i) In case if the street no longer intersects at the original road junctions, then the respective records in the Road Intersection Entity will be deleted.

(ii) In case if the street is now connected to other existing street(s), then new record(s) in the Road Intersection Entity will need to be created accordingly.

LandsD will update the Street layer and dispatch the Road Centreline CSU to other PDs (ID: LD07 & LD08). Concerned PDs and other road developer(s) will update their road data inventory on receipt of updated road centreline CSU from LandsD.

3.1.3.3.3 Closing of an Existing Road Centreline CSU When a road is removed due to road realignment and redevelopment, the CSU is then deleted.



3.1.4 Current and Recommended File Formats

3.1.4.1 Current File Formats In the existing environment, various software platforms and file formats were deployed in different departments and their divisions. The inventory of PDs’ core software platforms are summarized below: PD System Software Version Supported Versions of E00

and DGN ArchSD CAD AutoCAD 2000 N/A

C&SD Digital Mapping System Arc/Info 8.1 E00 (exported from Arc/Info Coverage version 7)

CED Slope Information System MicroStation J DGN v7.0

Geological Modelling System

ArcGIS 8.x E00 (exported from Arc/Info Coverage version 7)

Computerised Slope Register and Location Plan System

MicroStation J DGN v7.0

Geographics DGN v7.0

ArcView 3.2a E00 (exported from Arc/Info Coverage version 7)

DSD AM/FM Framme 04.00.06.07 DGN v7.0

EMSD Pilot GIS ArcView 3.2a E00 (exported from Arc/Info Coverage version.6 & 7)

HyD Road Data Maintenance System

Arc/Info and ArcSDE

8.1.2 E00 (exported from Arc/Info Coverage version 7 & 8)

Utility Management System (UMS)

MapInfo 4.1 E00 (exported from Arc/Info Coverage version 7)

LandsD Computerised Land Information System (CLIS)

AutoCAD 2000I N/A

MicroStation J DGN v7

Arc/Info 6.x E00 (exported from Arc/Info Coverage version 6)

SMRIS Arc/Info 8.x E00 (exported from Arc/Info Coverage version 7)

PlanD Town Planning Information System

Arc/Info 7.1.2 E00 (exported from Arc/Info Coverage version 7)

ArcMap 8.1 E00 (exported from Arc/Info Coverage version 7)

RVD Property Master System (PMS) and Interim Valuation System (IVS)

Arc/Info and

ArcSDE

8.2 E00 (exported from Arc/Info Coverage version 7)



PD System Software Version Supported Versions of E00 and DGN

WSD Digital Mapping System Arc/Info 8 E00 (exported from Arc/Info Coverage version 7)

SDE 3.2 E00 (exported from Arc/Info Coverage version 7)

ArcView 3.2a 3.2A E00 (exported from Arc/Info Coverage version 7)

Table 3.1.4.1-1 Supported Versions of E00 (Arc/Info Coverage) and DGN by PDs’ current CAD and GIS Systems

3.1.4.2 Recommended File Formats

To mitigate data conversion effort when data are exchanged across departments, a file format standard was recommended in the DAM project. In the context of CSU, future data exchange processes between PDs will be confined to the file formats standard. In the broader context of PLW data exchange, the recommended file formats standard will be promoted for use within HKSARG.

Specifications of the recommended file formats standard are summarized as below: (a) E00 (Exported from Arc/Info Coverage Version 7.0); (b) DGN v7 (3D1) with attributes storing in separated files;

(c) Other specifications:

(i) Linking DGN Drawing with attribute file: DGN Drawing should be linked with the attribute files (i.e. dBase IV file) using MSLINK. MicroStation use the field MSLINK to link up a graphic element with a row in the attribute file. Hence, the attribute file must contain a numerical field called MSLINK.

(ii) Character Set: As specified in IF, English Characters should be encoded in ASCII or EBCDIC (for mainframe to mainframe data exchange). Chinese Characters (e.g. annotation, attribute) should be encoded in Big 5 or ISO 10646-character set encoded in UTF-8. For further details, please refer to the Character sets and Encoding under Domain 3: Information Access and Interchange of Interoperability Framework (IF) version 1.0.

(iii) Coordinate System: Coordinates of geospatial data should be in the Hong Kong 1980 Grid.

1 It is understood that LandsD provides basemap in DGN with settings for three-dimensional (3D) drawings. The setting (i.e. 3D) is for elevation (i.e. z-value) of contour lines. On the other hand, as specified in CSWP, 3D DGN should be used for CAD Drawings exchange amongst Works Departments. In viewing that both the LandsD and Works Departments exchange DGN using the settings for 3D, 3D DGN is recommended in the File Formats Standard.



3.1.5 Dissemination Option suggested in DAM

3.1.5.1 Implementations Option

Given the latest status reported in the Draft DAM 1 paper, there are five CSUs and the respective Data Agents are:

CSU Data Agent Slope CED Building Lot Road Centerline

LandsD

TPU/SB PlanD Table 2 CSU and Data Agent

Data Agent of each CSU needs to provide data dissemination facilities to an agreed level of service such that data owners and data users are allowed to store/retrieve the CSU data following the mechanisms and procedures for maintenance of the CSU. There could be different implementation options for this data dissemination purpose.

3.1.5.2 Recommended Data Dissemination Option

D a ta U s e r

O ptio n A - C entral H u b (o n-line data dissem inatio n)

C e n tra l H u b

C S U D a t a b a s e

W e b -b a se D C T

U p lo a d

R e tr ie v e

C & S D

D a taO w n e r

R V D

B D

L a n d s D

B uil din g-S tr e e t N a m e …

O n -li n e D a ta S u b m is sio n

B uil din g-O P n um b e r …


B uil din g-S ur v e y e d B l d g N a m e …


B uil din g-O P n um b e r-S tr e e t N a m e …

O n -li n e D a ta R e tr ie v a l R V D

B uil din g-O P n um b e r …

O n -li n e D a ta R e tr ie v a l

P la nD B uil din g-O P n um b e r-S tr e e t N a m e …

O n -li n e D a ta R e tr ie v a l

G N E T

G N E T

Figure 3.1.5.2-1 - Recommended architecture of data dissemination system for CSUs in DAM In the DAM project, four options2 for the architecture of data dissemination system have been evaluated. Given the implementation schedule of DAM 1 and LandsD’s DDS, Option A was the recommended option and it was suggested to be implemented in stages: (a) Stage 1 – develop the central database, data upload facilities, data import

programmes, data conversion tools and facilities to allow data download by Data

2 Details of the evaluated options are in Draft DAM 1 paper.



Users for DAM 1 purpose (Web-based user interface may be considered for data upload and download facilities).

(b) Remaining stages – set up a hub to provide query and analytical functions (not a

mandatory requirement for DAM 1, but these functions could improve level of services), which are subject to detailed user requirements collected upon system implementation.



3.1.6 Existing PLW data exchange process identified in DAM project

Process ID

Data User /

Subject PD

Data Provider

Data Exchanged Related DAM

Strategy3

Related CSU

Format Freq. Size

(Mega Bytes)

Freq.

(Per Yr)

Tech. Effort

(Manday/

process)

Prof. Effort

(Manday/

process)

Annual Tech. Effort

(Manday /Yr)

Annual Prof. Effort

(Manday /Yr)

Total Annual Efforts

(HKD/Yr)

ArchSD10 ArchSD LandsD Land status DAM1 Lot Hardcopy O-M-5 4.8 60 0 0 0 0 0 ArchSD11 ArchSD CED Slope data DAM1 Slope Soft copy - - 0 0 0 0 0 0

BD01 BD CED Slope Information DAM1 Slope Hard copy - - 0 0 0 0 0 0 BD02 BD RVD Building Address DAM1 Building Soft copy O-Y-1 - 0 0 0 0 0 0 BD07 BD LandsD Land Status and

Cadastral Information DAM1 Lot Softcopy Several per

day - 1000 0 0 0 0 0

BD08 BD LandsD Lot outline or polygon DAM1 Lot Hardcopy O-Y-6 - 6 0.67 0 4 0 6,748 C&SD01-

A C&SD LandsD Base Map DAM1 Building Arc/Info O-Q-1 5,000 4 28.9 0 115.5 0 194,849

C&SD03-A

C&SD LandsD Cadastral map include land lot polygons

DAM1 Lot Arc/Info O-Q-1 640 4 1.875 0 7.5 0 12,653

C&SD04-A

C&SD PlanD TPU / SB boundaries DAM1 TPU Arc/Info O-Y-1 31 1 0.75 0 0.75 0 1,265

C&SD05-A

C&SD BD OP documents DAM1 Building Hard copy O-Y-80 - 80 0.45 0 36 0 60,732

C&SD08-A

C&SD BD BD MD DAM1 Building Hard copy O-M-1 - 12 3 0 36 0 60,732

CED18 CED LandsD Land Lot layout plans DAM1 Lot Hard copy - - 0 0 0 0 0 0 HyD11 HyD LandsD Lot boundaries DAM1 Lot Arc/Info O-H-1 4000 2 3 0.2 6 0.4 12,240 HyD13 HyD LandsD SMRIS data DAM1 Slope Arc/Info O-H-1 224 2 2 0.2 4 0.4 8,866

LandsD06 LandsD BD BD Monthly Building Digest

DAM1 Building Hard copy - - 0 0 0 0 0 0

LandsD07 LandsD BD OP DAM1 Building Hard copy O-Y-100 - 100 0.05 0 5 0 8,435 LR01 LR RVD Monthly Return of DAM1 Building Hard copy O-M-1 NA 12 9 0 108 0 182,196

3 DAM1: Common Spatial Units (CSU), DAM2: Standardization of symbology for graphic entities, DAM3: Standards on the file formats for exchanging data



Process ID

Data User /

Subject PD

Data Provider


Strategy3

Related CSU

Format Freq. Size

(Mega Bytes)

Freq.

(Per Yr)

Tech. Effort

(Manday/

process)

Prof. Effort

(Manday/

process)

Annual Tech. Effort

(Manday /Yr)

Annual Prof. Effort

(Manday /Yr)


(HKD/Yr)

Building Numbers Allocated/ Cancelled

LR02 LR BD Statutory Orders and Occupation Permit,

etc.

DAM1 Building Hard copy O-Y-26,643 NA 26643

0.016 0 426.288 0 719,148

LR03 LR LandsD Land grant document DAM1 Lot Hard copy O-Y-420 NA 420 0.176 0 73.92 0 124,703 LR04 LR LandsD Resumption Notices,

Consent etc. DAM1 Lot Hard copy O-Y-1,859 NA 1859 0.016 0 29.744 0 50,178

PlanD01 PlanD C&SD Register of Living Quarters

DAM1 TPU Textual O-Y-1 39 1 23 0 23 0 38,801

PlanD04 PlanD BD OP information in BD MD

DAM1 Building Microsoft Excel

O-M-1 0.2 12 2 0 24 0 40,488

PlanD05 PlanD BD Committed sites for development in BD

MD

DAM1 Building Microsoft Excel

O-M-1 Included in Plan D04

12 3 0 36 0 60,732

PlanD06 PlanD LR Land owner records DAM1 Lot Formatted text file

A-Y-1 306 1 80 0 80 0 134,960

PlanD07 PlanD LandsD Information on land sales

DAM1 Lot Arc/Info O-Y-1 0.1 1 6 0 6 0 10,122

RVD02-A RVD BD OPs, certificates and consents

DAM1 Building Hard copy O-W-5 - 260 0.15 0.0375 39 9.75 117,410

RVD06-A RVD PlanD TPU boundaries Plan DAM1 TPU Hard copy O-M-5 - 60 2.25 0.75 135 45 465,975 RVD09 RVD LandsD Land grant document DAM1 Lot Hard copy O-W-5 - 260 0.2 0.05 52 13 156,546 WSD02 WSD C&SD Demographic data DAM1 TPU Hard copy A-Y-5 500 5 6 1.5 30 7.5 90,315 WSD03 WSD LandsD GIRS data DAM1 Road

Centreline Formatted

text file O-H-1 200 2 1 0.1 2 0.2 4,433

WSD10 WSD PlanD TPU / SB boundaries DAM1 TPU Arc/Info O-Y-1 60 1 1 0.1 1 0.1 2,216 ArchSD01

-A ArchSD LandsD Base map DAM2 Building DGN O-Y-1 300 1 1 0 2 0 3,374

DSD02-A DSD Various As-built drawings DAM2 Building DGN, Hard O-Y-90 5 90 1 0.125 90 11.25 211,388



Process ID

Data User /

Subject PD

Data Provider


Strategy3

Related CSU

Format Freq. Size

(Mega Bytes)

Freq.

(Per Yr)

Tech. Effort

(Manday/

process)

Prof. Effort

(Manday/

process)

Annual Tech. Effort

(Manday /Yr)

Annual Prof. Effort

(Manday /Yr)


(HKD/Yr)

Works Depts.

copy

EMSD01-A

EMSD CED Project layout DAM2 Other DGN O-Y-30 0.5 30 1 0 30 0 50,610

HyD04-A HyD LandsD Base map (DGN) DAM2 Road Centreline

DGN O-Q-1 3000 4 3 0.5 12 2 30,832

HyD06-A HyD All Works Departme

nts

As-built drawings DAM2 Road Centreline

DGN, Hard copy

O-Y-140 14 140 0.125 0.05 17.5 7 66,581

LandsD01-A

LandsD CED Slope boundary DAM2 Slope DGN O-M-1 0.18 12 0.5 0.5 6 6 41,886

LandsD02-A

LandsD All Works Departme

nts

As-built drawings DAM2 Other DWG, hard copy

O-Y-30 3.5 30 0.7 0 21 0 35,427

PlanD08-A

PlanD LandsD BMS and CIS data DAM2 Other Arc/Info O-Q-1 - 4 0 0 0 0 0

WSD01-A WSD LandsD Base map DAM2 Building Arc/Info A-Y-5 1500 4 1 0.05 4 0.2 7,807 WSD04-A WSD All Works

Departments

As-built drawings DAM2 Building DGN, DWG, Hard

copy

A-Y-25 6 25 1.5 0.05 37.5 1.25 69,880

BLD-01 LandsD LandsD Outgoing Spatial Building data

DAM3 Building E00 O-M-1 - 12 2.75 0.083 33 1 60,965


DAM3 Building DWG O-M-1 - 12 2.83 0.08 34 1 62,652


DAM3 Building DXF O-M-1 - 12 2.83 0.08 34 1 62,652


DAM3 Building DGN O-M-1 - 12 4.08 0.08 49 1 87,957

BLD-05 LR LR Outgoing Textual Building data

DAM3 Building ASCII O-Y-1 - 1 0 0 0 0 0

BLD-06 LR LR Outgoing Textual DAM3 Building ASCII O-D-1 - 365 0 0 0 0 0



Process ID

Data User /

Subject PD

Data Provider


Strategy3

Related CSU

Format Freq. Size

(Mega Bytes)

Freq.

(Per Yr)

Tech. Effort

(Manday/

process)

Prof. Effort

(Manday/

process)

Annual Tech. Effort

(Manday /Yr)

Annual Prof. Effort

(Manday /Yr)


(HKD/Yr)

Building data BLD-13 RVD RVD (To

BD, LandsD, PlanD,

HD)

Outgoing Spatial Building data

DAM3 Building ASCII A-Y-1 - 1 27 0 27 0 45,549

BLD-14 PlanD LandsD Incoming Spatial Building data

DAM3 Building Arc/Info Library

7.2.1

O-Q-1 - 4 1 0 4 0 6,748

BLD-22 PlanD LandsD Incoming Textual Building data

DAM3 Building Arc/Info Library

7.2.1

O-Y-1 - 1 0 0 0 0 0

BLD-15 C&SD LandsD Incoming Spatial Building data

DAM3 Building Arc/Info Coverage

Pre7.0

O-Q-1 - 4 9.625 0 38.5 0 64,950

BLD-16 HyD LandsD Incoming Spatial Building data


Pre7.0

O-Q-1 - 4 1 0.2 4 0.8 10,983

BLD-17 HyD LandsD Incoming Spatial Building data


Pre7.0

O-Y-2 - 2 1 0.2 2 0.4 5,492

BLD-25 HyD LandsD Incoming Textual Building data

DAM3 Building Info 7.0 O-Y-2 - 2 1 0 2 0 3,374

BLD-18 LandsD All Works Departme

nts

Incoming Spatial Building data

DAM3 Building DGN A-Y-1 - 1 120.8 5.4 120.8 5.4 232,377

BLD-19 LandsD All Works Departme

nts

Incoming Spatial Building data

DAM3 Building DWG A-Y-1 - 1 181.2 8.1 181.2 8.1 348,566

BLD-20 CED LandsD Incoming Spatial Building data

DAM3 Building DGN O-Q-1 - 4 1 0 4 0 6,748



Process ID

Data User /

Subject PD

Data Provider


Strategy3

Related CSU

Format Freq. Size

(Mega Bytes)

Freq.

(Per Yr)

Tech. Effort

(Manday/

process)

Prof. Effort

(Manday/

process)

Annual Tech. Effort

(Manday /Yr)

Annual Prof. Effort

(Manday /Yr)


(HKD/Yr)

BLD-21 RVD LandsD Incoming Spatial Building data

DAM3 Building Arc/Info O-W-1 - 52 0 0 0 0 0

BLD-23 PlanD BD Incoming Textual Building data

DAM3 Building Excel A-Y-1 - 1 24 0 24 0 40,488

BLD-24 PlanD HD Incoming Textual Building data

DAM3 Building Excel A-Y-1 - 1 2 0 2 0 3,374

BLD-26 BD RVD Incoming Textual Building data

DAM3 Building Hardcopy O-D-1 - 365 0 0 0 0 0

BLD-27 RVD BD Incoming Textual Building data

DAM3 Building Hardcopy O-W-5 - 260 0.08 0 20 33,740

BLD-28 RVD BD Incoming Textual Building data

DAM3 Building Hardcopy O-M-1 - 12 5 0 60 101,220

BLD-29 RVD LandsD Incoming Textual Building data

DAM3 Building Hardcopy O-W-5 - 260 0.24 0 60 101,220

BLD-07 LandsD LandsD Outgoing Textual Building data

DAM3 Building ASCII O-M-1 - 12 1.09 0.08 13 1 27,225

BLD-30 TDD LandsD Incoming Spatial Building data

DAM3 Building DWG (2000) O-Q-1 - 4 0.5 0 2 0 3,374

BLD-31 TDD LandsD Incoming Textual Building data

DAM3 Building 0 O-Q-1 - 1 2 0 2 0 3,374

LOT-01 LandsD LandsD Outgoing Spatial Lot data

DAM3 Lot EOO O-M-1 - 12 2.59 0.08 31 1 57,591


DAM3 Lot DGN O-M-1 - 12 4.09 0.08 49 1 87,957


DAM3 Lot DWG O-M-1 - 12 2.25 0.08 27 1 50,843


DAM3 Lot DXF O-M-1 - 12 2.25 0.08 27 1 50,843

LOT-05 PlanD LandsD Incoming Spatial Lot data

DAM3 Lot Arc/Info Library

7.2.1

O-Q-1 - 4 1 0 4 0 6,748



Process ID

Data User /

Subject PD

Data Provider


Strategy3

Related CSU

Format Freq. Size

(Mega Bytes)

Freq.

(Per Yr)

Tech. Effort

(Manday/

process)

Prof. Effort

(Manday/

process)

Annual Tech. Effort

(Manday /Yr)

Annual Prof. Effort

(Manday /Yr)


(HKD/Yr)

LOT-06 PlanD LandsD Incoming Spatial Lot data


7.2.1

O-Q-1 - 4 0.5 0 2 0 3,374

LOT-07 C&SD LandsD Incoming Spatial Lot data

DAM3 Lot E00 O-Q-1 - 4 0.625 0 2.5 0 4,218

LOT-08 HyD LandsD Incoming Spatial Lot data

DAM3 Lot Arc/Info Library pre

7.0

O-Y-2 - 2 4 0.8 8 1.6 21,966

LOT-09 DSD LandsD Incoming Spatial Lot data

DAM3 Lot Hardcopy A-Y-1 - 1 20 0 20 0 33,740

LOT-10 RVD LandsD Incoming Spatial Lot data

DAM3 Lot Arc/Info O-W-1 - 52 0 0 0 0 0

LOT-11 CED LandsD Incoming Spatial Lot data

DAM3 Lot E00 O-Q-1 - 4 0.5 0 2 0 3,374

LOT-12 PlanD LandsD Incoming Textual Lot data


7.2.1

A-Y-1 - 1 0 0 0 0 0

LOT-14 CED LandsD Incoming Textual Lot data

DAM3 Lot E00 O-Q-1 - 4 0.5 0 2 0 3,374

RCL-01 LandsD LandsD Outgoing Spatial Road Centreline data

DAM3 Road Centreline

E00 O-M-1 - 12 2.83 0.17 34 2 67,946

RCL-02 LandsD LandsD Outgoing Textual Road Centreline data


ASCII O-M-1 - 12 0.83 0.083 10 1 22,164

RCL-03 PlanD LandsD Incoming Spatial Road Centreline data


Arc/Info Library

7.2.1

O-Y-2 - 2 1 0 2 0 3,374

RCL-04 C&SD LandsD Incoming Spatial Road Centreline data


ASCII (Arc/Info Exported

ASCII)

O-Q-1 - 4 1 0 4 0 6,748

RCL-05 HyD LandsD Incoming Spatial Road DAM3 Road Arc/Info O-Y-2 - 2 8.2 0 16.4 0 27,667



Process ID

Data User /

Subject PD

Data Provider


Strategy3

Related CSU

Format Freq. Size

(Mega Bytes)

Freq.

(Per Yr)

Tech. Effort

(Manday/

process)

Prof. Effort

(Manday/

process)

Annual Tech. Effort

(Manday /Yr)

Annual Prof. Effort

(Manday /Yr)


(HKD/Yr)

Centreline data Centreline Coverage 7.0

RCL-06 WSD LandsD Incoming Textual Road Centreline data


ASCII O-Y-1 - 1 8 0 8 0 13,496

RCL-07 TDD LandsD Incoming Spatial Road Centreline data


DWG (2000) O-Y-2 - 2 3.5 0 7 0 11,809

RCL-08 TDD LandsD Incoming Textual Road Centreline data


ASCII O-Y-2 - 2 3.5 0 7 0 11,809

SLP-01 LandsD LandsD Outgoing Spatial Slope data

DAM3 Slope DGN O-M-1 - 12 0.29 0.07 3.5 0.84 10,351

SLP-02 LandsD LandsD Outgoing Textual Slope data

DAM3 Slope ASCII O-M-2 - 24 0.19 0.03 4.5 0.75 11,562

SLP-03 LandsD LandsD Outgoing Textual Slope data

DAM3 Slope Excel O-M-2 - 24 0.28 0.03 6.75 0.75 15,358

SLP-04 HyD CED Incoming Spatial Slope data

DAM3 Slope DGN A-Y-2 - 2 2 0.2 4 0.4 8,866

SLP-05 HyD LandsD Outgoing Spatial Slope data

DAM3 Slope ArcSDE 8.1.2

O-Y-2 - 2 2 0.2 4 0.4 8,866

SLP-06 LandsD CED Incoming Spatial Slope data

DAM3 Slope DGN O-M-1 - 12 0.375 0.06 4.5 0.72 11,403

SLP-07 DSD CED Incoming Spatial Slope data

DAM3 Slope DGN SE A-Y-1 - 1 0 0 0 0 0

SLP-08 WSD CED Incoming Spatial Slope data

DAM3 Slope DGN SE O-M-1 - 12 5 0 60 0 101,220

SLP-09 PlanD LandsD Incoming Textual Slope data

DAM3 Slope Arc / Info 7.2.1

A-Y-1 - 1 0 0 0 0 0

SLP-10 CED CED Outgoing Spatial Slope data

DAM3 Slope DGN O-M-1 - 12 0 0 0 0 0

SLP-11 CED CED Outgoing Textual Slope data

DAM3 Slope DBF O-M-1 - 12 0.5 0 6 0 10,122

SLP-12.1 CED BD Incoming Spatial Slope DAM3 Slope Hardcopy A-Y-500 - 500 0.08 0 40 0 67,480



Process ID

Data User /

Subject PD

Data Provider


Strategy3

Related CSU

Format Freq. Size

(Mega Bytes)

Freq.

(Per Yr)

Tech. Effort

(Manday/

process)

Prof. Effort

(Manday/

process)

Annual Tech. Effort

(Manday /Yr)

Annual Prof. Effort

(Manday /Yr)


(HKD/Yr)

data SLP-12.2 CED HyD Incoming Spatial Slope

data DAM3 Slope Hardcopy A-Y-500 - 500 0.08 0 40 0 67,480

SLP-12.3 CED WSD Incoming Spatial Slope data

DAM3 Slope Hardcopy A-Y-500 - 500 0.08 0 40 0 67,480

SLP-14.1 CED LandsD Incoming Textual Slope data


SLP-14.2 CED HD Incoming Textual Slope data


SLP-14.3 CED HyD Incoming Textual Slope data


SLP-14.4 CED TDD Incoming Textual Slope data


SLP-14.5 CED WSD Incoming Textual Slope data


SLP-13 CED LandsD Incoming Spatial Slope data

DAM3 Slope DGN O-M-1 - 12 0 0 0 0 0

TPU-01 PlanD PlanD Outgoing Spatial TPU data

DAM3 TPU DGN O-Y-2 - 2 0.25 0 0.5 0 844


DAM3 TPU E00 O-Y-2 - 2 0.25 0 0.5 0 844


DAM3 TPU Arc/Info Coverage

O-Y-2 - 2 0 0 0 0 0


DAM3 TPU ArcView SHAPEFILE

O-Y-2 - 2 0.25 0 0.5 0 844

TPU-05 HyD PlanD Incoming Spatial TPU data

DAM3 TPU ArcView SHAPEFILE

O-Y-2 - 2 0.4 0 0.8 0 1,350

TPU-06 LandsD PlanD Incoming Spatial TPU data

DAM3 TPU Arc/Info Coverage

6.x

A-Y-1 - 1 10 0 10 0 16,870

TPU-07 C&SD PlanD Incoming Spatial TPU DAM3 TPU E00 A-Y-1 - 1 0.25 0 0.25 0 422



Process ID

Data User /

Subject PD

Data Provider


Strategy3

Related CSU

Format Freq. Size

(Mega Bytes)

Freq.

(Per Yr)

Tech. Effort

(Manday/

process)

Prof. Effort

(Manday/

process)

Annual Tech. Effort

(Manday /Yr)

Annual Prof. Effort

(Manday /Yr)


(HKD/Yr)

data TPU-08 RVD PlanD Incoming Spatial TPU

data DAM3 TPU Arc/Info A-Y-1 - 1 0 0 0 0 0

TPU-09 DSD PlanD Incoming Spatial TPU data

DAM3 TPU Hardcopy A-Y-1 - 1 2 0 2 0 3,374

TPU-10 DSD PlanD Incoming Textual TPU data

DAM3 TPU Excel A-Y-1 - 1 0 0 0 0 0

DDS OF LANDS DEPARTMENT -

Documents

Transcript of DDS OF LANDS DEPARTMENT -