A10.1 General standards - LUPMISManual

Go to content

Main menu:

Annexes 1-10 > A10. Standards

Annex 10: Standards

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

An information system depends on the data standards and the consistency of using the established standards. It is one of the greatest challenge to use and to implement all data standards.

This standardized data syntax will enable cross-computer handling and transfer of LUPMIS data and applications. Data standards are explained in this Chapter, internal technical standards in Annex 1.2. They can also be viewed in the LUPMIS Tools at the 'info' references of the Printing Tools. Individual classes of all standard maps are listed in Annex 6.


A10.1 General Standards

  • Vector file format:

- At LUPMIS / TCPD: DRA (see part A of  Annex 1.2 and Chapter 1.1)


- For exchange with external users also: SHP (can be exported from Map Maker:
Main Menu > Utilities > Vector utilities > Export files > to ArcView Shape file)


  • Vector file names follow a strict standard system for their names, classes and folders, listed in Annex 10.2. If file name standards are not maintained, no automatic printing can be done and no referencing from databases!!!



  • Raster file names follow a strict standard system for their names, classes and folders, listed in Annex 10.3.


  • World files for orthophotomaps (see Annex 2.3):

- At LUPMIS / TCPD: Internal in Map Maker JPG
- For exchange with external users also: Exported through Map Maker (Main Menu > Utilities > Bitmap utilities > Convert file format > from JPG > ... > World File)


  • Terrain model format: TBD


  • Database format: MySQL


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


  • Units: Meter


  • Horizontal accuracy:  

- 3 m for Local Plans
- 10 m for Structure Plans




  • Name for planning area / project community: 2-10 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.

- Structure Plan: 1:25,000 - 1:30,000 recommended
- Local Plan: 1:2500,
Try not to make the Local Plan not too large (not exceeding 2000 parcels).


  • 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
- 'Snapped'


  • Classes / classifications:    

- As styles (For full listings, see Annex 6)



  • 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.4.6)

  • Names and codes of Regions, Districts and Settlements

- Regions: 1-10 (see Annex 9.5.1, derived from master file 'Ghana_region.dra' )


- Districts: Region code + 2-digit District code (see
Annex 9.5.2, derived from master file 'Ghana_district.dra' )


- Settlements (in accordance with master file 'Ghana_settlementsmain_nation.dra'):

-- In metros and municipialities of GAMA: 1-digit code for submetro + 2-digit code for 'community'
-- Outside: 3-digit settlement code


  • Parcel layer:

- DRA-ID: UPN
- DRA-Display label: At Local Plans: Streetname and housenumber, at other maps: Name of unit
- DRA-Styles: Classification, e.g. planning units (see Annex 6.2 for SDF, Annex 6.3 for Structure Plan, Annex 6.4 for Local Plan, etc)



  • Altitude:

- Meters, in display label, but often derived from feet-based topographic maps

- Street name and house number in 'display label' of Local Plan DRA file
- No spaces in house numbers (e.g. 17A, not 17 A)
- First house number, then street name (e.g. 17 Oxford Str, not Oxford Str 17)
- One space between street name and house number (17 High Str, not 17High Str, not 17-High Str, not 17,High Str)
- Use abbreviations whenever possible (Ave, Str, Rd etc)
- There is a strict convention on naming of streets: _streetlines, _streettext, _streetpoly, _streetpoints

- Roads are different to streets: Roads are mainly GPS-tracked single lines (centre line) maps covering longer distances (not only urban).
- Dual carriageways are dual (parallel) lines.

- - - - -


TBD: To be defined

  

 
Back to content | Back to main menu