arma3:terrain:real-world-data-global-mapper
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
arma3:terrain:real-world-data-global-mapper [2017/01/29 23:18] – created real-world-data-global-mapper initial page. snakeman | arma3:terrain:real-world-data-global-mapper [2024/08/02 18:58] (current) – links added. snakeman | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Real World Data Acquisition Using Global Mapper ====== | + | ====== |
+ | |||
+ | [[https:// | ||
**How to get terrain heightmap and satellite texture into Terrain Builder using Global Mapper.** [[http:// | **How to get terrain heightmap and satellite texture into Terrain Builder using Global Mapper.** [[http:// | ||
Line 6: | Line 8: | ||
- | ====== | + | ====== |
- | **How to use Global Mapper to create real world data terrain for arma3.** | + | **Using existing ASCII Grid .ASC heightmap file.** |
- | This ASCII Grid ASC tutorial assumes you have downloaded heightmap from [[http:// | + | This ASCII Grid ASC tutorial assumes you have downloaded heightmap from using [[arma3: |
**Terrain: | **Terrain: | ||
- | - start global mapper | ||
- open data files -> select your ASC | - open data files -> select your ASC | ||
- tools -> configure -> projection, select projection dropdown UTM, zone 31, apply and ok | - tools -> configure -> projection, select projection dropdown UTM, zone 31, apply and ok | ||
Line 31: | Line 32: | ||
Global Mapper v18 Digitizer Tool RMB menu: | Global Mapper v18 Digitizer Tool RMB menu: | ||
- | {{ http:// | + | {{ https:// |
Global Mapper v18 Export Menu menu: | Global Mapper v18 Export Menu menu: | ||
- | {{ http:// | + | {{ https:// |
Global Mapper v18 Digitizer Tool RMB Advanced Feature Creation: | Global Mapper v18 Digitizer Tool RMB Advanced Feature Creation: | ||
- | {{ http:// | + | {{ https:// |
Global Mapper v18 Digitizer Tool RMB Create Area/ | Global Mapper v18 Digitizer Tool RMB Create Area/ | ||
- | {{ http:// | + | {{ https:// |
- | ====== | + | ====== |
- | We use online map sources, world imagery, to download satellite texture. | ||
- | |||
- | **Satellite texture:** | ||
- | - click globe button (connect to online data) | ||
- | - choose world imagery, click connect | ||
- | - file -> export -> export raster/ | ||
- | - sample spacing put both x/y axis to 1 meters | ||
- | - select export bounds tab | ||
- | - tick crop to selected area feature(s) box and click ok | ||
- | - choose file name like satellite_texture_lco.bmp and click save | ||
- | all done | ||
- | |||
- | |||
- | ====== ASTER GDEM Heightmap ====== | ||
- | |||
- | - Start global mapper | ||
- click globe button (connect to online data) | - click globe button (connect to online data) | ||
- select aster gdem and hit connect | - select aster gdem and hit connect | ||
Line 77: | Line 62: | ||
- give file name to your exported asc, click save | - give file name to your exported asc, click save | ||
+ | Remember that you should use SRTM heightmaps from opentopo which are higher quality than ASTER GDEM. | ||
- | ====== World Imagery Satellite Texture ====== | ||
+ | ====== Satellite Texture World Imagery ====== | ||
+ | |||
+ | We use online map sources, world imagery which is [[http:// | ||
+ | |||
+ | **Satellite texture:** | ||
- click globe button (connect to online data) | - click globe button (connect to online data) | ||
- choose world imagery, click connect | - choose world imagery, click connect | ||
- | - file -> export -> export raster/ | + | - file -> export -> export raster/ |
- | - sample spacing put both x/y axis to 1 meters | + | - sample spacing |
- select export bounds tab | - select export bounds tab | ||
- tick crop to selected area feature(s) box and click ok | - tick crop to selected area feature(s) box and click ok | ||
- | - choose file name like satellite_texture_lco.bmp and click save | + | - choose file name like satellite_texture_lco.png and click save |
+ | All done! | ||
- | Our attempts to export 40960 x 40960 resolution world imagery satellite texture ended up Global Mapper freezing with 0% CPU usage. | + | Our attempts to export 40960 x 40960 resolution world imagery satellite texture ended up Global Mapper freezing with 0% CPU usage. |
+ | |||
+ | See also [[arma3: | ||
+ | |||
+ | |||
+ | ====== Export Satellite BMP Color Palette ====== | ||
+ | |||
+ | **Global Mapper v11, v13 and v15 exports RGB, v18 exports only indexed color BMP images.** | ||
+ | |||
+ | Example BMP color palette comparison, left global mapper exported BMP and right terra incognita saved original JPG image: | ||
+ | {{ https:// | ||
+ | Notice the 256 color palette (indexed) as it shows limited colors on the farm fields. | ||
+ | |||
+ | We did comparison | ||
+ | |||
+ | JPG with quality slider 95% and PNG 24bit has no visible differences. On file sizes (in my example) PNG is 1.25mb where JPG is 418kb. | ||
+ | |||
+ | Quality slider has no effect on BMP export image quality. | ||
+ | |||
+ | Summary: always export 24bit PNG files instead for maximum image quality. | ||
Line 97: | Line 107: | ||
This assumes you have read world imagery satellite texture part so you know how to export satellite image. | This assumes you have read world imagery satellite texture part so you know how to export satellite image. | ||
- | - on bmp export options dialog, select tiling tab | + | - on PNG export options dialog, select tiling tab |
- tick " | - tick " | ||
- put both rows and columns to value 2 | - put both rows and columns to value 2 | ||
Line 111: | Line 121: | ||
B1 bottom left\\ | B1 bottom left\\ | ||
B2 bottom right | B2 bottom right | ||
+ | |||
+ | |||
+ | ====== Large Satellite Textures ====== | ||
+ | |||
+ | If you have a very large, huge, satellite texture like above 40960 x 40960 resolution, it basically needs to be exported as tiles. Not only tiles but **enough tiles** so the tile size remains small, do not exceed 20480 resolution! | ||
+ | |||
+ | We would recommend tile size more close to rough 10,000 to keep them nice and small. Yes the more tiles you have the more cumbersome they are to import into terrain builder, but once you have exported the tiles you can use [[arma2: | ||
+ | |||
+ | If you try to export too large tiles, then global mapper writes the BMP files somehow incorrectly and they are not readable with photoshop (or imagemagick). For example we tried to export 35,500 resolution images and it failed. This might be different for PNG 24bit files, needs to be tested, however for now you should export as tiles. | ||
+ | |||
+ | When importing these tiles into terrain builder you can use even larger resolutions so you can stitch these tiles together and import only 2 x 2 tiles instead of 25 hehe. Use good numbers for tiles, like 2 x 2, 4 x 4 and 5 x 5. There are bad tile grid setups, here is example table of different resolutions divided by values: | ||
+ | < | ||
+ | 20480 | ||
+ | 2 == 10240 | ||
+ | 3 == 6826.666666666667 | ||
+ | 4 == 5120 | ||
+ | 5 == 4096 | ||
+ | 6 == 3413.333333333333 | ||
+ | 7 == 2925.714285714286 | ||
+ | 8 == 2560 | ||
+ | |||
+ | 40960 | ||
+ | 2 == 20480 | ||
+ | 3 == 13653.33333333333 | ||
+ | 4 == 10240 | ||
+ | 5 == 8192 | ||
+ | 6 == 6826.666666666667 | ||
+ | 7 == 5851.428571428571 | ||
+ | 8 == 5120 | ||
+ | |||
+ | 81920 | ||
+ | 2 == 40960 | ||
+ | 3 == 27306.66666666667 | ||
+ | 4 == 20480 | ||
+ | 5 == 16384 | ||
+ | 6 == 13653.33333333333 | ||
+ | 7 == 11702.85714285714 | ||
+ | 8 == 10240 | ||
+ | |||
+ | 102400 | ||
+ | 2 == 51200 | ||
+ | 3 == 34133.33333333333 | ||
+ | 4 == 25600 | ||
+ | 5 == 20480 | ||
+ | 6 == 17066.66666666667 | ||
+ | 7 == 14628.57142857143 | ||
+ | 8 == 12800 | ||
+ | </ | ||
+ | As you can see **you should not export tiles 3 x 3, 6 x 6 and 7 x 7 because they wont be even numbers**, global mapper rounds UP the resolution and then you end up with 2 pixel too large tiles. I doubt nobody want to export much more tiles as even the 81920 resolution drops to 20480 with four tiles. | ||
+ | |||
+ | This is not very important, its just your own convenience when importing few or many tiles into terrain builder, if you get global mapper to successfully export 40960 then that's great :-) | ||
+ | |||
+ | Rule of thumb: | ||
+ | * Global mapper export **many small tiles** | ||
+ | * Terrain builder import **few large tiles** | ||
+ | |||
+ | |||
+ | ====== Darken and Merge Satellite Tiles ====== | ||
+ | |||
+ | You need to darken most downloaded satellite images as arma3 v1.60 introduced visual upgrade requires very dark satellite texture. | ||
+ | |||
+ | Also you might want to merge the exported satellite images to something bit larger before importing to terrain builder. | ||
+ | |||
+ | See [[arma3: | ||
+ | |||
+ | |||
+ | ====== Map Catalog for Satellite Texture ====== | ||
+ | |||
+ | When you have saved large satellite texture image using [[arma3: | ||
+ | |||
+ | - File -> create new map catalog, choose file name and click save. | ||
+ | - Now you get modify map catalog dialog, click Add directory button and click ok. | ||
+ | - Enter file mask(s) to open dialog, write *.map into the input field and click ok. | ||
+ | - Now global mapper will load all the .map files in the directory. when its done click ok. | ||
+ | - Modify map catalog click ok | ||
+ | |||
+ | This map catalog helps global mapper to handle large amounts of OziExplorer .map satellite texture tiles without causing heavy performance loss or memory usage. | ||
+ | |||
+ | The map catalogue is shown in global mapper as blue grid with red backgrounds when you are zoomed out, when you zoom in it will load those satellite images. | ||
+ | |||
+ | If you have very small satellite images or few of them, then this map catalog creation might be not needed, experiemnt it and see for yourself. | ||
+ | |||
+ | |||
+ | ====== User Created Grid Label ====== | ||
+ | |||
+ | When you use digitizer tool and create grid, it will have a label in center of the grid. You don't want this as it will be printed on any satellite texture you export. | ||
+ | |||
+ | To delete the label select digitizer tool, double click on your grid to bring up modify feature info dialog, then just erase (select and hit DEL key) the text on name field. | ||
+ | |||
+ | |||
+ | ====== Load Online Data Only to Grid ====== | ||
+ | |||
+ | Create grid (user created features), then click globe button (connect to online data) and tick " | ||
+ | |||
+ | |||
+ | ====== Grid Selections ====== | ||
+ | |||
+ | Select your user created feature layer and digitizer tool. RMB to your grid -> advanced selection options -> select all line features within the selected areas -> select no option. | ||
Line 124: | Line 232: | ||
- select export bounds tab | - select export bounds tab | ||
- tick crop to selected area feature(s), click ok | - tick crop to selected area feature(s), click ok | ||
+ | |||
+ | This exact same method do not work in global mapper v18, it just saves the whole shapefile as is without any cutting, clipping or cropping :( | ||
+ | |||
+ | See [[arma3: | ||
+ | |||
+ | |||
+ | ====== Export Split FCLASS ====== | ||
+ | |||
+ | Global Mapper can split your exported shapefiles into different files. In this example our OSM data has FCLASS attribute and we want to export currently seen data into individual shapefiles named according to FCLASS. | ||
+ | |||
+ | File -> Export -> vector/ | ||
+ | |||
+ | |||
+ | ====== Latitude Longitude ====== | ||
+ | |||
+ | CTRL-L copy pastes coordinates from mouse position into clipboard. | ||
+ | |||
+ | |||
+ | ====== Terrain Center Position ====== | ||
+ | |||
+ | **Howto get absolute center position of your terrain** from the user created feature grid. | ||
+ | |||
+ | Digitizer tool, CTRL-LMB drag box around left bottom corner and then right upper corner vertices. Then RMB in the grid and choose Crop/ | ||
+ | |||
+ | Now you can select the middle vertice, this is absolute center position of your terrain. | ||
+ | |||
+ | Select the vertice -> RMB -> Vertex editing -> set position of selected vertices. In this dialog click geographic coordinates (lat/lon), now you can see and copy paste latitude / longitude values. | ||
- | ====== | + | ====== |
- | [[arma3: | + | RMB google/maps location |
+ | In global mapper zoom quite close to any position (doesn' | ||
- | ====== Finding Location On Globe ====== | ||
- | Go to maps.google.com and navigate to the place which interests you. | + | ====== Tips ====== |
- | RMB position | + | If you want to export user created features, just RMB the layer and choose layer -> export, then save it as shapefile. |
- | You can also use Global Mapper -> Connect to Online data (Online Sources) -> World street map, to open street maps which show you locations in countries just like maps.google would. However maps.google is much faster / optimized and has some search plus additional features. |
arma3/terrain/real-world-data-global-mapper.1485731923.txt.gz · Last modified: 2017/01/29 23:18 by snakeman