v.in.genamap is a quick hack to convert Genamap export files (type 25 with .EE extension) into Grass ascii vector files and site files. It has been used quite extensively over here, but not been tested rigidly. Usage: v.in.genamap input=name [points=name] [lines=name] [areas=name] [scale=value] Parameters: input Genamap export file (.EE) to be imported into GRASS points Name of site-file for points lines Name of vector-file for lines ("areas" to treat lines as area edges and append them to the area-layer) areas Name of vector-file for areas ("lines" to treat area elements as lines and append them to the line layer) scale Scaling factor for numeric attributes default: 1 The following conversion rules are followed: - If no output files are specified, the name of the Genamap export file will be stripped of its .EE extension and used as base name for site and/or vector layers. These will be created as soon as point or line elements are encountered. By default, line and area elements will be put into different vector layers. - Genamap entries of type POINT are put into a site file with their tag as attribute. - Entries of type LINE with a tag in the header line are put in a line vector file. - Entries of type LINE without a tag in the header line are put in an area vector file - Alternatively, line entities can be appended to the area layer, and area entities can be appended to the line layer. However, an entity cannot be put into both line and area layers. This means that Genamap maps with areas surrounded by tagged lines can NOT be imported in one run. - Numeric LINE and AREA tags are converted to integer attributes; you can give a scaling factor for floating point numbers - Non-numeric tags will be assigned to integer attributes in the order they are encountered in the export file. The tags themselves are copied to Grass categories. Grass vector files are less complex than Genamap maps, so maps that verify ok under Genamap will give errors when running v.support. Try to observe the following rules for import maps: - Do not mix lines and areas within one map - Do not mix numeric and non-numeric tags in one map - Don't make your maps too complex; divide where possible. - Don't connect islands with a line to the surrounding area, or leave open ended lines within an area. Jan Hartmann Faculty of Environmental Sciences University of Amsterdam jhartman@scanner.frw.uva.nl