LUPMIS - GIS User Manual for Land Use Planning

Annex 10: 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). Data standards are explained in this Chapter, internal technical standards in Annex 1.2.

• Filename for vector files:

	Syntax	Example	Content
In ...dra folder:
	district _roads	Kasoa_roads.dra (sample)	only lines, styles 1-21
	district _roadsmain	Ejisu_roadsmain.dra	only lines, styles 1-21
	district _settlements	Asan_settlements.dra (sample)	only points, styles 1-8
	district _settlementsmain_region	Kasoa_settlementsmain_region.dra (sample)	only points, styles 1-9
	district _utils [not defined yet]	Kasoa_utils.dra	only lines
	district _region	Ejisu_region.dra (sample)	only 1 polygon, style 1
	district _district	Dodowa_district.dra (sample)	only polygon(s) (can be 1 or more), style 1
	district _district_ year	Dodowa_district_2000.dra	only polygon(s) (can be 1 or more) of a previous survey (e.g. 2000), style 1
	district _districtcapitals	Dodowa_districtcapitals.dra	only point(s) (can be 1 or more)
	district _councils	Ejisu_councils.dra	only polygons
	district _rivers	Kasoa_rivers.dra (sample)	only lines (if they form polygons, see 'waterbodies'), styles 1-5
	district _riversmain	Kasoa_riversmain.dra	only lines (if they form polygons, see 'waterbodies'), style 1-2
	district _waterbodies	Kasoa_waterbodies.dra (sample)	only polygons (if they form lines, see 'rivers'), style 6-13
	district _landuse	Dodowa_landuse.dra	only polygons, style 1-30
	district _landuse_symbols	Dodowa_landuse_symbols.dra	only points (for symbols), style 151-179, style for legend in separate file
	district _contours	Ejisu_contours.dra (sample)	interval of 50 feet (!) or better, only lines
	district _contours100	Ejisu_contours100.dra	100 feet (!) interval, in exceptional cases also in 250 ft interval, only lines
	district _UPNgrid	Kasoa_UPNgrid.dra (sample)	only lines, 1 km grid
	district _soils	Ejisu_soils.dra	not necessarily suitabilities, only polygons
	district _popdensity	Axim_popdensity.dra	only polygons, style 1 (very high) - 4 (low)
	district _concessions	Axim_concessions.dra	only polygons, style 1
	district _minerals	Axim_minerals.dra	only points
	district _annotations	Axim_annotations.dra	structure to be defined
In ...SDF folder:
	district _SDFarea	Save_SDFarea.dra	only 1 polygon
	district _SDF	Save_SDF.dra	only polygons
	district _growthzone	Western_growthzone.dra	only polygons
	district _settlementsproposed	Ejisu_settlementsproposed.dra	only points
In ...StrPl folder:
	name of structure plan _StrPlarea	Ejisu NW_StrPlarea.dra (sample)	only 1 polygon
	name of structure plan _StrPl	Ejisu NW_StrPl.dra (sample)	only polygons
	district _neighbour	Ejisu_neighbour.dra	only polygons
	district _roadsproposed	Kasoa_roadsproposed.dra	only lines
	district _roadsmainproposed	Kasoa_roadsmainproposed.dra	only lines
	district _utilsproposed [not defined yet]	Dodowa_utilsproposed.dra	only lines
	district _electr	Kasoa_electr.dra	only points, style 1-4
	district _health	Kasoa_health.dra	only points, style 32-37
	district _education	Kasoa_education.dra	only points, style 59-62
	district _waste	Kasoa_waste.dra	only points, style 1-4
	district _transportpoints	Kasoa_transportpoints.dra	only points, style 124-137
	district _touristsites	Kasoa_touristsites.dra	only points, style 1-6
	district _waterdistr	Axim_waterdistr.dra	only points, style 1-3
In ...SL folder:
	district _SLoverview	Kasoa_SLoverview.dra (sample)	labels should be equal to Sector Layout names (see below), only polygons
	name of Sector Layout	Papaase.dra (sample)	free full naming of Sector Layout, but should be equal to label in _SLoverview layer (see above), only polygons
	name of Sector Layout .dbf	Papaase.dbf	attribute file with housenumbers etc
	name of Sector Layout _scan	Papaase_scan.jpg	raster
	name of Sector Layout _streetnames	Papaase_streetnames.dra sample	street names, only as text, see also Chapter 7.8.3
	name of Sector Layout _footprint	Papaase_footprint.dra (sample)	existing structures of buildings, only polygons or only lines
	name of Sector Layout _streets	Papaase_streets.dra (sample)	polygons of streets within a Local Plan, with classes (styles) of 118-123, no islands !
	name of Sector Layout _roadsexisting	Papaase_roadsexisting.dra	existing structures of carriageways / roads, and of surrounding area for Sector Layout, only lines
	name of Sector Layout _roadsproposed	Papaase_roadsproposed.dra (sample)	proposed carriageways in the Sector Layout, only lines
	name of Sector Layout _value	Papaase_value.dra	value of parcels (for land revenue and IGF)
For Internet handling:
	name of Sector Layout .kmz	Papaase_2.kmz	any map for internet display (spaces in name replaced with underscore)
	name of Sector Layout _upn.kmz	Papaase_2_upn.kmz	Local Plans with UPN, displayed on mouse over (spaces in name replaced with underscore)
	name of Sector Layout _status.kmz	Papaase_2_status.kmz	Local Plan status (spaces in name replaced with underscore)
	name of Sector Layout _streets.kmz	Papaase_2_sreets.kmz	Local Plan streets, polygons, no islands ! (spaces in name replaced with underscore)
	name of Sector Layout _structures.kmz	Papaase_2_structures.kmz	Structures and houses (spaces in name replaced with underscore)

Filename for raster files:
-- For orthophotomaps and satellite images: xxxyyyy of bottom left corner + year + width + height + resolution, e.g. 7680609_2008_2x1_40.jpg (see part F of Annex 1.2)
-- For topo maps: xxxyyyy of bottom left corner + width + height + scale + SMD code + local name (see part G of Annex 1.2 and parts B and D of Chapter 5.3.1), e.g. 7490581_28x28_50_0501C2_KasoaSW.jpg
-- name of community images/photos + year + indexcoverage + size
-- name of community images/photos + year + coverage
-- name of community images/photos + year + index + size

• Filename for database files:TBD

• Vector file format:

-- At LUPMIS / TCPD: DRA (see part A of Annex 1.2 and Chapter 1.1)
-- For exchange with LIS: SHP

• Raster file format: JPG (see part A of Chapter 5.3.1)

• World file (see Annex 2.3): Internal

• Terrain model format: TBD

• Database format: MySQL

• Coordinate system: WGS 84 / UTM (see Annex 2.2)

• Units: Meter

• Horizontal accuracy:

-- 3 m for surveys
-- 10 m for plans

• Parcel numbering: UPN (see Chapter 7.7.1)

• Folder structure: See part C of Annex 1.2

• Name for planning area / project community: 3-8 letters, no space, unique. It is recommended to use the name of the district capital (see part D of Annex 1.2). Long full name is also entered in Permit Database.

• Features in one vector layer: 1

• Topology of GIS layers:

-- Close without overshoot
-- Not duplicated
-- All road junctions with line break
-- One label per feature
-- All adjacent polygons without slivers
-- All adjacent polygons without overlap

• Classes:

-- As styles (see Annex 6 )
-- Special attention for roads (90 for main roads), rivers (101-105), villages (101-104), waterbodies (24), district (80)

• Metadataformat: TBD

• Names for Local Plans ('Sector Layouts'):

-- Free naming, as it should appear on the map, can contain space(s). Recommended not to use very long names (see part J of Chapter 8.1.5)

• Names and codes of Regions and Districts (see here)

• Parcel layer:

-- DRA file with DBF attribute file
-- Only parcel polygons, no road/river etc polygons (see step 9 of Chapter 7.6.3)
-- DRA-ID: UPN
-- DRA-Label: UPN (The identity can be automatically checked through the quality control at the Permit Database, see Chapter 8.1.3)
-- DRA-Styles: Local Plan class (see Annex 6.5)
-- DBF-ID: UPN
-- DBF-LocalPlanClass: Local Plan class (copy)
-- DBF-LocalPlanZone: Copy from Structure Plan class
-- Additional fields are possible

• Altitude:

-- Meters, in display label

• Street names:

-- Name in display label
-- Use abbreviations whenever possible (Ave, Str, Rd etc)
-- Attached style file: No line, label lines

• Permit Database (see also step 3 of Annex 18.2):

-- MDB / MDE file
-- ID (autonumber, as primary key)
-- UPN (text, field size:13)
-- Additional fields are possible.

- - - - -

TBD: To be defined