LUPMIS - GIS User Manual for Land Use Planning

A1.2 Technical Standards

Level of expertise required for this Chapter: Intermediate; specifically for LUPMIS @ TCPD

A standardized data syntax will ease the cross-computer handling and enable transfer of Map Maker projects (see Chapter 1.6). Internal technical standards are explained in this Chapter, data standards in Annex 10.

A) Map Maker graphical files have the extension DRA.

- - - - -

B) Map Maker database files have the extension DBF.

They should contain following fields:

• ID, text string, as the main link column
• Style, integer, as the code for the standard display (which is to be transferred to the internal style definition by: In live layer: Right-mouse > Live layer actions > Basic operations > Set styles by data > Choose data column window: Select Style (from the DBF file) > OK)

By default, following fields are also created:

• Spare
• Area, with area size in sqm

- - - - -

C) The LUPMIS folder structure should be synchronized in all installations (data / network server, network clients, stand-alone):

• C: \ LUPMIS
• C: \ LUPMIS \ (area)

• C: \ LUPMIS \ (area) \ (area) dra, with all vector files (DRA), from survey, other agencies, compiled etc (content)
• C: \ LUPMIS \ (area) \ (area) dra \ Backup, with backups
• C: \ LUPMIS \ (area) \ (area) dra \ Tools, with legends and other output from LUPMIS Tools

• C: \ LUPMIS \ (area) \ (area) photos, with all georeferenced aerial photos, including indexes etc (subfolders are allowed and are recognized)
• C: \ LUPMIS \ (area) \ (area) topo, with all scanned, georeferenced topo maps, including indexes etc

• C: \ LUPMIS \ (area) \ (area) SDF, with all (draft and final) SDF plans and auxiliary data for SDF planning (content)
• C: \ LUPMIS \ (area) \ (area) SDF \ Backup, with backups
• C: \ LUPMIS \ (area) \ (area) SDF \ Tools, with legends and other output from LUPMIS Tools

• C: \ LUPMIS \ (area) \ (area) StrPl, with all (draft and final) Structure Plans and auxiliary data for Structure planning (content)
• C: \ LUPMIS \ (area) \ (area) StrPl \ Backup, with backups
• C: \ LUPMIS \ (area) \ (area) StrPl \ Tools, with legends and other output from LUPMIS Tools

• C: \ LUPMIS \ (area) \ (area) SL, with all previous scanned, georeferenced TCPD sector layouts and Local Plans, including indexes (content)
• C: \ LUPMIS \ (area) \ (area) SL \ Backup, with backups
• C: \ LUPMIS \ (area) \ (area) SL \ Tools, with legends and other output from LUPMIS Tools

• C: \ LUPMIS \ (area) \ (area) permits, with permits and backups
• C: \ LUPMIS \ (area) \ (area) permits\scans, with scanned permit documents

• C: \ LUPMIS \ LUPMISManual, with this manual (in HTML format)
• C: \ LUPMIS \ Exercises

• C: \ LUPMIS \ Temp, for all temporary, work and intermediate files and for testing and learning. You have to do your own housekeeping in this folder, but it is a good practice to have a date stamp (see below) in all file names.

For example:
C:\LUPMIS
C:\LUPMIS\Kasoa
C:\LUPMIS\Kasoa\Kasoa dra
C:\LUPMIS\Kasoa\Kasoa photos
C:\LUPMIS\Kasoa\Kasoa SL
C:\LUPMIS\Kasoa\Kasoa topo
C:\LUPMIS\Temp

Technical note: If a subfolder inside ...photos is called 'Temp' or 'Work' or 'Non-LUPMIS', it will not be used for archive of JPG for the ' Printing Tools'.

- - - - -

D) Names of planning areas and project communities (computer name for districts) have a 3-8 letter code (see standards in Annex 10).

For example:

• Kasoa
• Ejisu
• Asan
• Save
• Dodowa

- - - - -

E) Dates should be written in the format of yymmdd, where:

• yy = Year
• mm = Month
• dd = Day
• If necessary, add _hh for the hour (24 hours).

For example:

• 091515: 15th of May, 2009
• 090301_12: 1st of March, 2009, 12 noon

- - - - -

F) Orthophoto maps and satellite images have following file name syntax xxxyyyy_YYYY_axb_c, where:

• xxx = Easting of bottom left corner of tile (in km, UTM) in 3 digits
• yyyy = Northing of bottom left corner of tile (in km, UTM) in 4 digits (!)
• YYYY = Year
• a = Horizontal tile size in km (W-E)
• b = Vertical tile size in km (N-S)
• c = pixel size in cm

For example:

• 7800610_2008_6x3_80.jpg: Image tile with bottom left corner coordinates of 780000 / 610000 of size of 6 x 3 km with a pixel size of 80, of the year 2008
• 7900612_2008_2x1_40.jpg: Image tile with bottom left corner coordinates of 790000 / 612000 of size of 2 x 1 km, with pixel size of 40 cm, of the year 2008

G) Scanned topo maps have following file name syntax xxxyyyy_axb_d_e_f, where:

• xxx = Easting of bottom left corner of tile (in km, UTM) in 3 digits
• yyyy = Northing of bottom left corner of tile (in km, UTM) in 4 digits (!)
• a = Horizontal extension in km (W-E)
• b = Vertical extension in km (N-S)
• d = scale in thousands
• e = code of Survey & Mapping Division (SMD), if available
• f = name (optional)

For example: 7490581_28x28_50_0501C2_KasoaSW.jpg: Topo sheet with bottom left corner coordinates of approx 749000 / 581000 of size of 28 x 28 km, from topomap 1:50,000, referenced as 0501C2 by SMD, at Kasoa SW

See also Annex 10 for vector file names of raster files.

See Chapter 5.3.1 parts B and D for application, and references to flight index maps with tiles syntax through Annex 9.

- - - - -