LUPMIS - GIS User Manual for Land Use Planning

A1.2 LUPMIS Data Syntax

Level of expertise required for this Chapter: Intermediate

A standardized data syntax will ease the cross-computer handling and enable transfer of Map Maker projects (see Chapter 1.6). For general standards, see 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) dra, with all vector files (DRA), from survey, other agencies, compiled etc
• C:\LUPMIS\(area) photos, with all georeferenced aerial photos, including indexes etc
• C:\LUPMIS\(area) plans, with all (draft and final) plans and auxiliary data for planning
• C:\LUPMIS\(area) SL, with all scanned, georeferenced TCPD sector layouts, including indexes
• C:\LUPMIS\(area) topo, with all scanned, georeferenced topo maps, including indexes etc

• C:\LUPMIS\LUPMISManual, with this manual (in HTML format)
• C:\LUPMIS\Permits, with permits
• C:\LUPMIS\Permits\Scans, with scanned permit documents
• 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 dra
C:\LUPMIS\Kasoa photos
C:\LUPMIS\Kasoa SL
C:\LUPMIS\Kasoa topo
C:\LUPMIS\Temp

- - - - -

D) Planning areas and project communities have a 3-6 letter code.

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) LUPMIS raster files (images) have following file name syntax xxxyyy_yyyy_axb or
xxxyyy_yyyy_axb_c, where:

• xxx = Easting of bottom left corner of tile (in km, UTM)
• yyy = Northing of bottom left corner of tile (in km, UTM), can also be 4 digits
• yyyy = Year
• a = Horizontal tile size in km (W-E)
• b = Vertical tile size in km (N-S)
• If necessary, add c for the pixel size in cm or m. This can be omitted, if pixel size thas the default size of 80-100 cm

For example:

• 780610_2008_6x3: Tile with bottom left corner coordinates of 780000 / 610000 of a tile size of 6 x 3 km with a pixel size of 80-100 cm. of the year 2008
• 790612_2008_2x1_40: Tile with bottom left corner coordinates of 790000 / 612000 of a tile size of 2 x 1 km, with pixel size of 40 cm, of the year 2008

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

- - - - -