Import Background Image - Revision history

Peder at 15:40, 7 December 2011

2011-12-07T15:40:54Z

Peder at 19:02, 17 February 2010

2010-02-17T19:02:44Z

Peder at 19:01, 17 February 2010

2010-02-17T19:01:17Z

Peder: moved Import of forest map and background image to Import Background Image

2010-02-17T18:59:18Z

moved Import Background Image to Import Background Image

Peder at 18:58, 17 February 2010

2010-02-17T18:58:31Z

Peder at 15:43, 29 December 2009

2009-12-29T15:43:08Z

Hah at 13:59, 8 September 2009

2009-09-08T13:59:04Z

Hah at 13:55, 8 September 2009

2009-09-08T13:55:03Z

Hah at 13:53, 8 September 2009

2009-09-08T13:53:44Z

Hah at 13:48, 8 September 2009

2009-09-08T13:48:46Z

@@ Line 15: / Line 15: @@
 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 "Path to grapichal files", the folder 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.
+#In "Path to pyramide files", the folder with pyramid files can be empty, created files will end up here.
 #Choose correct map type and "Create".
 #Looking at the pyramids 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.

@@ Line 1: / Line 1: @@
 [[User's guide to PlanStart]]
-'''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 .tif-file format (but other graphical formats are possible, e.g. bitmaps). ''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:

@@ Line 1: / Line 1: @@
-[[Category:User's Guides|PlanStart|PlanStart]]
+[[User's guide to PlanStart]]
 '''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 .tif-file format (but other graphical formats are possible, e.g. bitmaps). ''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.
@@ Line 26: / Line 23: @@
 *'''Tip 1'''
 :Since creating pyramids for large images are time-consuming, look for databases with already imported image data and possibilities to use such as the forest database in the following analyses.

@@ Line 2: / Line 2: @@
 [[Category:PlanStart]]
 [[Category:Database]]
 '''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 .tif-file format (but other graphical formats are possible, e.g. bitmaps). ''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.

← Older revision		Revision as of 15:43, 29 December 2009
Line 1:		Line 1:
		+	[[Category:User's Guides\|PlanStart\|PlanStart]]
		+	[[Category:PlanStart]]
		+	[[Category:Database]]
		+
	'''A forest map''' corresponding to the stand register data can be imported ("External data" > "Import forest map...") only if the format is "Shape". Digital maps in other formats should be converted before import. ''Once in while, one must convert a shape-file to shape... this to make it readable by the system and probably due to some data format specification.'' 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''' corresponding to the stand register data can be imported ("External data" > "Import forest map...") only if the format is "Shape". Digital maps in other formats should be converted before import. ''Once in while, one must convert a shape-file to shape... this to make it readable by the system and probably due to some data format specification.'' 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).

← Older revision	Revision as of 18:59, 17 February 2010
(No difference)

@@ Line 17: / Line 17: @@
 #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 contains six rows. This can be done in, e.g., Notepad (but beware of any double extensions after saving, like "*.tfw.txt" - rename any file with such name).
+#Did your World file turn out alright? Sometimes EOL is misinterpret and then you must edit the .tfw-file so that it contains six rows. This can be done in, e.g., Notepad (but beware of any double extensions after saving, like "*.tfw.txt" - rename files with such names).
 #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 the same system, in future releases preferrably in SWEREF99].

@@ Line 1: / Line 1: @@
-A '''forest map''' corresponding to the stand register data can be imported ("External data" > "Import forest map...") only if the format is "Shape". Digital maps in other formats should be converted before import. ''Once in while, one must convert a shape-file to shape... this to make it readable by the system and probably due to some data format specification.'' 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''' corresponding to the stand register data can be imported ("External data" > "Import forest map...") only if the format is "Shape". Digital maps in other formats should be converted before import. ''Once in while, one must convert a shape-file to shape... this to make it readable by the system and probably due to some data format specification.'' 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).
 Settings in the dialog box, following the selection of Shape database, follows:
 #In "Attribute"-drop list, select columns in the .dbf-file or constants (with user-defined values).
 #Add attributes and change the column length if necessary.
 #By padding with zeros and selecting space between columns, preview and confirm that the shape database key corresponds to the stand register. Press "Ok".
-'''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 .tif-file format (but other graphical formats are possible, bitmaps?). ''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:
@@ Line 15: / Line 17: @@
 #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 contains six rows.
+#Did your World file turn out alright? Sometimes EOL is misinterpret and then you must edit the .tfw-file so that it contains six rows. This can be done in, e.g., Notepad.
-#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 the same system, in future releases preferrably in SWEREF?].
+#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 the same system, in future releases preferrably in SWEREF99].
 Now return to PlanStart, and in menu "External data" > "Import background image...":
@@ Line 26: / Line 28: @@
 Before you go on with importing the pyramids (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 are time-consuming, look for databases with already imported image data and possibilities to use such as the forest database in the following analyses.