Difference between revisions of "Import Background Image"
| Line 10: | Line 10: | ||
#Now you might be in a tricky position; if the original image is in 8 bit you must force it into the three bands RGB to obtain a 24 bit-image. This might be possible only if you export to an output raster with .bmp-format. If so, open the bitmapped file in, e.g., Paint and save it as .tif-file | #Now you might be in a tricky position; if the original image is in 8 bit you must force it into the three bands RGB to obtain a 24 bit-image. This might be possible only if you export to an output raster with .bmp-format. If so, open the bitmapped file in, e.g., Paint and save it as .tif-file | ||
#Did you obtain a corresponding World file (.tfw or .bpw)? This is needed for geo-referencing purposes, and in most GIS's a built-in functionality (automatically runned), else you might need to create such file separately | #Did you obtain a corresponding World file (.tfw or .bpw)? This is needed for geo-referencing purposes, and in most GIS's a built-in functionality (automatically runned), else you might need to create such file separately | ||
| − | #Did your World file turn out alright? Sometimes EOL is misinterpret and then you must edit the .tfw-file so that it contain six rows. | + | #Did your World file turn out alright? Sometimes EOL is misinterpret and then you must edit the .tfw-file so that it contain six rows |
| + | #Finally, the spatial reference of an image should be set to the Swedish Grid RT90, 2.5 gon West, to enable viewing in PlanWise [Redundant? What is important is probably that different imported maps and images are in same system.]. | ||
Now return to PlanStart, and in menu "External data" > "Import background image...": | Now return to PlanStart, and in menu "External data" > "Import background image...": | ||
| Line 21: | Line 22: | ||
Before you go on with importing the pyramides (i.e. the divided background image), make sure this is done to a forest database where no other image data is overwritten. | Before you go on with importing the pyramides (i.e. the divided background image), make sure this is done to a forest database where no other image data is overwritten. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
*'''Tip 1''' | *'''Tip 1''' | ||
| − | : | + | :Since creating pyramids for large images is time-consuming, |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Revision as of 14:54, 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 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.
However, this is the somewhat advanced steps in importing images:
- In your GIS, open the raster image
- If necessary, zoom to/select the area of interest (to decrease the extent of the image and hence the file-size)
- Choose "Export Raster Data" (or similar)
- Now you might be in a tricky position; if the original image is in 8 bit you must force it into the three bands RGB to obtain a 24 bit-image. This might be possible only if you export to an output raster with .bmp-format. If so, open the bitmapped file in, e.g., Paint and save it as .tif-file
- Did you obtain a corresponding World file (.tfw or .bpw)? This is needed for geo-referencing purposes, and in most GIS's a built-in functionality (automatically runned), else you might need to create such file separately
- Did your World file turn out alright? Sometimes EOL is misinterpret and then you must edit the .tfw-file so that it contain six rows
- Finally, the spatial reference of an image should be set to the Swedish Grid RT90, 2.5 gon West, to enable viewing in PlanWise [Redundant? What is important is probably that different imported maps and images are in same system.].
Now return to PlanStart, and in menu "External data" > "Import background image...":
- In "Create pyramides", the catalogue with graphical files must contain at least one graphical .tif-file with a corresponding world .tfw-file (formatted as described above)
- In "Create pyramides", the catalogue with pyramid files can be empty, created files will end up here
- Choose correct map type and "Create"
- Looking at the pyramides of an image, you will find it divided into several images, or layers, with different resolution in each layer. The presentation of such image in a GIS/Map viewer will then be done more rapid, adapting to current view-scale.
Before you go on with importing the pyramides (i.e. the divided background image), make sure this is done to a forest database where no other image data is overwritten.
- Tip 1
- Since creating pyramids for large images is time-consuming,