Difference between revisions of "Import Background Image"

From Heureka Wiki
Jump to navigation Jump to search
Line 1: Line 1:
 
A forest map related to the stand register data can be imported ("Link to existing area..." or "Import forest map..." > "Import from shape") only if the format is "Shape". Digital maps in other formats should be converted before import. Linking is done by using the .dbf-file of the map and the three first fields of the register's .csv-file (MapId, StandId, and SubStandId, respectively).
 
A forest map related to the stand register data can be imported ("Link to existing area..." or "Import forest map..." > "Import from shape") only if the format is "Shape". Digital maps in other formats should be converted before import. Linking is done by using the .dbf-file of the map and the three first fields of the register's .csv-file (MapId, StandId, and SubStandId, respectively).
  
A background image (in raster format, as opposed to the vector format above) can be imported and viewed with the forest map. Preferrably, the image should be in .tiff-file format (but other graphical formats is possible, e.g. .bmp). ''NB: Only one layer per type (Road-, Terrain-, and Ortomap) is possible to import to the forest database, any new image-import will overwrite the old, already imported images!'' This is of course unfortunate and will be fixed in future releases. A roadmap, more or less covering the entire company's sphere of activities, might be imported once and for all while the ortophotos probably would be added continuously as new areas are to be analysed.  
+
Background images (in raster format, as opposed to the vector format above) can be imported and viewed with the forest map. Preferrably, the image should be in .tiff-file format (but other graphical formats are possible, e.g. .bmp). ''NB: Only one layer per type (Road-, Terrain-, and Ortomap) is possible to import to the forest database, any new image-import will overwrite the old, already imported images!'' This is of course unfortunate and will be fixed in future releases. A roadmap, more or less covering the entire company's sphere of activities, might be imported once and for all while the ortophotos probably would be added continuously as new areas are to be analysed.  
  
 
Associated pyramid file is used for geo-referencing. Any conversions - coordinate system transformations - should be done prior to import. [The map-viewer in PlanWise is based on the Swedish Grid (RT90, 2.5 gon V), redundant?]
 
Associated pyramid file is used for geo-referencing. Any conversions - coordinate system transformations - should be done prior to import. [The map-viewer in PlanWise is based on the Swedish Grid (RT90, 2.5 gon V), redundant?]

Revision as of 11:46, 7 May 2009

A forest map related to the stand register data can be imported ("Link to existing area..." or "Import forest map..." > "Import from shape") only if the format is "Shape". Digital maps in other formats should be converted before import. Linking is done by using the .dbf-file of the map and the three first fields of the register's .csv-file (MapId, StandId, and SubStandId, respectively).

Background images (in raster format, as opposed to the vector format above) can be imported and viewed with the forest map. Preferrably, the image should be in .tiff-file format (but other graphical formats are possible, e.g. .bmp). NB: Only one layer per type (Road-, Terrain-, and Ortomap) is possible to import to the forest database, any new image-import will overwrite the old, already imported images! This is of course unfortunate and will be fixed in future releases. A roadmap, more or less covering the entire company's sphere of activities, might be imported once and for all while the ortophotos probably would be added continuously as new areas are to be analysed.

Associated pyramid file is used for geo-referencing. Any conversions - coordinate system transformations - should be done prior to import. [The map-viewer in PlanWise is based on the Swedish Grid (RT90, 2.5 gon V), redundant?]