Importing_Raster.........................

1. Importing Raster Converting to MRR format for Planet

2. Grid File Constraints There are a few constrains for the grid files in Planet: A grid file should be projected (i.e. not Lat/Long). Grid files must align with a (0, 0) reference point. A properly aligned grid is one where the xmin and ymin (i.e. coordinates of the center of the bottom-left bin) are a whole number multiple of the cell size (i.e. resolution). MapInfo Units(Z value) needs to be defined, generally to meters. Pixels needed to be square. 2

3. Converting inputs to MRR 3 Tool: Raster  Raster Operations  Convert Specify the Units(Z), If requested, specify the projection info.

4. Merging converted MRR, if needed. 4 Tool: Raster  Raster Operations  Merge Merge Region : Union Merge Operator : Stamp Resample Method : Bilinear for elevation files(DEM, DTM, DSM) Nearest for clutter or clutter height files

5. Reprojecting MRR 5 Tool: Raster  Raster Operations  Reproject New Projection: It should be the same as the projection used for the project Interpolation: Bilinear for elevation files(DEM, DTM, DSM) Nearest for clutter or clutter height files New Cell Size : It should be an integer value

6. Verifying the reference point (the 0,0 Reference) 6 Tool: Raster  Raster Info Cell size(X and Y): They should be equal and an integer. Origin of the raster : The values represent the lower left corner of the lower left pixel of the raster. 0,0 Reference Grid files must align with a (0, 0) reference point. A properly aligned grid is one where the xmin and ymin (i.e. coordinates of the center of the bottom-left bin) are a whole number multiple of the cell size (i.e. resolution). (World origin X +(Cell size / 2)) / Cell size = Whole number (World origin Y +(Cell size / 2)) / Cell size = Whole number If results are not valid, a correction is needed.

7. Aligning (correcting the 0,0) the raster, if needed. 7 There are many ways of doing this. We will try with the simplest. Open the raster in a Mapper. Make the Cosmetic Layer editable. Draw a polygon around the raster. Spatial  Insert Save the Cosmetic Layer as BigArea.tab MAP  Cosmetic  Save Cosmetic Objects Get the bounds of the polygon Right click on the polygon Calculate the new bounds (Integer(Bound value/30))+(Cellsize / 2) X1 9183.87 9195 X2 1368269.37 1368255 Y1 4455330.75 4455345 Y2 6553973.64 6553965 Must be a region, not a polygon original new x1 469.886,370000 m 469.905,000000 m =ROUND(B2/cellsize;0)* cellsize +( cellsize / 2) x2 684.527,240000 m 684.525,000000 m =ROUND(B3/cellsize;0)* cellsize -( cellsize / 2) y1 6.168.098,440000 m 6.168.105,000000 m =ROUND(B4/cellsize;0)* cellsize +( cellsize / 2) y2 6.380.089,430000 m 6.380.085,000000 m =ROUND(B5/cellsize;0)* cellsize -( cellsize / 2)

8. Aligning (correcting the 0,0) the raster, if needed. 8 Rasterize the BigArea.tab . The goal here is to create a raster that properly referenced and larger than the raster we are correcting. Tool: Raster  Raster Operations  Rasterize Assign Value = Fixed Value Overlay Value = 0 Cell Size = 30 Output Raster Type = Numeric Background Value = NULL Data Units = Meters Output Geometry = Checked Raster Bounds = Values from step 6

9. Aligning (correcting the 0,0) the raster, if needed. 9 Align the reprojected raster to the BigArea raster Input file = eu_dem_Reproject Primary Raster = BigArea_Rasterize Resample Methods = Bilinear Bilinear for elevation files Nearest for clutter or clutter height files

10. Final Check 10 Tool: Raster  Raster Info Cell size(X and Y): They should be equal and an integer. Origin of the raster : The values represent the lower left corner of the lower left pixel of the raster. Grid files must align with a (0, 0) reference point. A properly aligned grid is one where the xmin and ymin (i.e. coordinates of the center of the bottom-left bin) are a whole number multiple of the cell size (i.e. resolution). (World origin X +(Cell size / 2)) / Cell size = Whole number (World origin Y +(Cell size / 2)) / Cell size = Whole number If results are not valid, a correction is needed. MapInfo Units should be defined

11. Thank you! www.infovista.com 11