LUPMIS - GIS User Manual for Land Use Planning

A18.7 Map Maker In / Out Files

Level of expertise required for this Chapter: Expert / Programmer; general Map Maker training

There are many ways to manipulate Map Maker data and its set-up with external files (great strength of Map Maker!):

• MME ('Map Maker Export'): Content of entire vector file, in ASCII, predefined key words, can be edited with any (clean) text editor or modified through a program. Program access through the MMmacro command 'convert file'; can also be accessed through the menu: Utilities > Vector utilities > Import / Export files > Map Maker Export file

• XY: Coordinates of points or vertices, can contain ids, in ASCII, can be edited with any (clean) text editor or modified through a program. More documenation and exercises in Annex 16. Program access through the MMmacro command 'convert file'; can also be accessed through the menu: Utilities > Vector utilities > Import / Export files > Map Maker XY file

• LOC: Short form of vector file, does not include labels, in ASCII, can be edited with any (clean) text editor or modified through a program. Program access through the MMmacro command 'convert file', though import is not recommended; can also be accessed through the menu: Utilities > Vector utilities > Import / Export files > Map Maker LOC file

• TXT: Useful at the import/export of the definition of charts, in ASCII, can be edited with any (clean) text editor or modified through a program. Can also be accessed and edited through the Program manager > Style > Labels > Data chart > Chart

• PTP: Definition of all layers (and project), in ASCII, can be edited with any (clean) text editor or modified through a program. In a programming environment better than GEO files (see below). Program access through the MMmacro command 'add layer'; can also be accessed through the menu: File > Page templates > Edit template

• GEO: Project definition file, in ASCII, can be edited with any (clean) text editor or modified through a program (though 2.option after PTP files, see above). Program access through the MMmacro commands 'load project' or 'save project'; can also be accessed through the menu: File > Open Project / Save Project as or File > Page templates > Edit template

• CSV: Standard 'comma separated value' format, in ASCII, can be edited with any (clean) text editor or modified through a program.

• DBF ('database file'): Outdated attribute file format, can be modified through a program (in php with the commands dbase_definition, dbase_create etc, but requires dbase extension). Can be read in Excel; can also be accessed through the menu: Utilities > Database utilities > Edit database

• EMF: Standard graphics file, e.g. for templates and legends. In a programming environment better than BMP files (see below). Can be incorporated in the program through the MMmacro command 'Save legend', or through the Project manager > Project legend > Preview > Save to Enhanced Metafile or Map furniture > Furniture type > Enhanced Meta file

• BMP: Standard graphics file, e.g. for templates. Can be incorporated in the program (though 2. option after EMF files, see above), or through Map furniture > Furniture type > Bitmap file

The best way to understand the full syntax, is to create - through the menu - a sample of the import/export file and study it.

In LUPMIS, there are also established file standards for input/output:

• XYT (xy of templates): 'Planning templates' with same syntax as XY files, desribed above

• TXL (layout as text files): Raw layouts for LUPMIS maps