A1.2 Technical standards - LUPMISManual

A1.2 Technical Standards

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

a) Map Maker geographical files

b) Folder structure

c) Administrative units (Districts etc) and codes

d) Dates

e) Orthophoto maps and satellite images

f) Topo maps

g) Docs for permit applications

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 geographical files
  

Map Maker (geo)graphical files have the extension DRA.

• b) Folder structure
  

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

• C: \ LUPMIS
  

• C: \ LUPMIS \ (district)
  

• C: \ LUPMIS \ (district) \ (district) dra, with vector files with original data from surveys, other agencies, etc (content)

• C: \ LUPMIS \ (

  district

  ) \ (

  district

  ) dra \ Tools, with legends and other output from LUPMIS Tools
  

• C: \ LUPMIS \ (district) \ (district) dra \ Backup, with backups

• C: \ LUPMIS \ (district) \ (district) photos, with all georeferenced aerial photos, including indexes etc (subfolders are allowed and are recognized; subfolders with the names Non-LUPMIS, Additional, Old, Temp, Work, Tools, Backup, TempCanBeDeleted, OriginalFormat, OriginalCoordSystem, OriginalTileswill not be automatically referenced and backupped)

• C: \ LUPMIS \ (district) \ (district) topo, with all scanned, georeferenced topo maps, including indexes etc (no subfolders)

• C: \ LUPMIS \ (district) \ (district) SDF, with all (draft and final) SDF plans and auxiliary data for SDF planning (content)

• C: \ LUPMIS \ (

  district

  ) \ (

  district

  ) SDF \ Tools, with legends and other output from LUPMIS Tools
  

• C: \ LUPMIS \ (district) \ (district) SDF \ Backup, with backups

• C: \ LUPMIS \ (district) \ (district) StrPl, with all (draft and final) Structure Plans and auxiliary data for Structure planning (content)

• C: \ LUPMIS \ (

  district

  ) \ (

  district

  ) StrPl \ Tools, with legends and other output from LUPMIS Tools
  

• C: \ LUPMIS \ (district) \ (district) StrPl \ Backup, with backups

• C: \ LUPMIS \ (district) \ (district) LP, with all previous scanned, georeferenced TCPD sector layouts and Local Plans, including indexes (content) (previously: SL folder)

• C: \ LUPMIS \ (

  district

  ) \ (

  district

  ) LP \ Tools, with legends and other output from LUPMIS Tools (previously: SL \ Tools)
  

• C: \ LUPMIS \ (district) \ (district) LP \ Backup, with backups (previously: SL \ Backup)

• C: \ LUPMIS \ (district) \ (district)  permits, with permit data. (The actual Permit Database is stored in MySQL)

• C: \ LUPMIS \ (district) \ (district)  permits \ Tools, with output from LUPMIS Tools

• C: \ LUPMIS \ (district) \ (district)  permits \ Docs, with scanned permit documents

• C: \ LUPMIS \ (district) \ (district) permits \ Permits, with permits

• C: \ LUPMIS \ (district) \ (district)  permits \ Backup, with backups

• C: \ LUPMIS \ (district) \ (district)  rev, with all data for the IGF module. (The actual Revenue Database IGF is stored in MySQL)

•  C: \ LUPMIS \ (district) \ (district)  rev \ Tools, with output from LUPMIS Tools

•  C: \ LUPMIS \ (district) \ (district)  rev \ DemandNotices, with Demand Notices, printed from the LUPMIS Revenue Tools (created automatically)

•  C: \ LUPMIS \ (district) \ (district)  rev \ Receipts, with receipts, printed from the LUPMIS Revenue Tools (created automatically)

•  C: \ LUPMIS \ (district) \ (district)  rev \ Log, with log files from the LUPMIS Revenue Tools

•  C: \ LUPMIS \ (district) \ (district)  rev \ Backup, with backups

• C: \ LUPMIS \ LUPMISReports, with a library of planning-related documents, which can be accessed through the LUPMIS Reports Tools. Because of the huge size of this library, it has to be installed from the 'LUPMIS Supplement CD' (see Annex 11).
  

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

• C: \ LUPMIS \ LUPMISGISintro, with an introduction into GIS (in HTML format)
  

• C: \ LUPMIS \ LUPMISOtherMaps, with non-archived maps in JPG format
  

• C: \ LUPMIS \ Programs with all programs, graphic files, templates, GIS utility software, 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. You can clean this folder with the 'Clear temp file' Drawing Tool.
  

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'.

• c) Administrative units (Districts etc) and codes
  

For computer handling, the names of Districts, planning areas and project communities have a 2-10 letter code without spaces (see district setup procedure in Annex 9.1).

For example:

• Kasoa
  

• Ejisu
  

• Asan
  

• Western
  

• Ghana
  

All Districts have a 3-digit code (in Upper East, 4-digits), where the first digit (in Upper East, 2 digits, e.g. number 10) stands for the Region, the follow 2 digits for the consecutive numbering of the Districts in the Region. This code had been established by the Ministry for Local Government around 2012.

Region code:

1   Greater Accra Region

2   Central Region

3   Western Region

4   Eastern Region

5   Ashanti Region

6   Volta Region

7   Brong Ahafo Region

8   Northern Region

9   Upper West Region

10  Upper East Region

• d) Dates
  

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

- - - - -

• e) Orthophoto maps and satellite images
  

Orthophoto maps and satellite images have following file name syntax XXXYYYY_AAAA_WxH_R, 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 (!)
  

• AAAA = Year
  

• W = Horizontal tile size in km (width, W-E)
  

• H = Vertical tile size in km (height, N-S)
  

• R = pixel size in cm (resolution)
  

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
  

• f) Topo maps
  

Scanned topo maps have following file name syntax XXXYYYY_WxH_S_I_N, 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 (!)
  

• W = Horizontal extension in km (width, W-E)
  

• H = Vertical extension in km (width, W-E)
  

• S = scale in thousands
  

• I = code of Survey & Mapping Division (SMD), if available
  

• N = 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.2 for vector file names, Annex 10.3 for 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.2 and 9.3.