Differences

This shows you the differences between two versions of the page.

--- arma3:terrain:road-shapefiles-real-world-data [2017/10/06 19:12] – http to https switch. snakeman
+++ arma3:terrain:road-shapefiles-real-world-data [2024/08/02 19:07] (current) – links added. snakeman
@@ Line 1: / Line 1: @@
-====== Road Shapefiles from Real World Data ======
+====== ArmA 3 Road Shapefiles from Real World Data ======
+[[https://www.pmctactical.org/forum/viewforum.php?f=68|ArmA 3 Forum]], [[:arma3|ArmA 3]], [[arma3:config|ArmA 3 Config]], [[arma3:missions|ArmA 3 Missions]], [[arma3:modeling|ArmA 3 3D Modeling]], [[arma3:scripting|ArmA 3 Scripting]], [[arma3:terrain|ArmA 3 Terrain]], [[arma3:texturing|ArmA 3 Texturing]], [[arma3:tools|ArmA 3 Tools]]
 **How to use real world data road shapefiles from OpenStreetMap (OSM) in ArmA 3**.
@@ Line 103: / Line 105: @@
 Note: for example plain deserts (heightmap) of iraq easily allows OSM road features of 9000 but the rugged mountains (heightmap) of afghanistan crashes for less then 5000. So use your own judgement with all these gazillion variables when you track down the amount of roads your terrain can handle.
+Mexico juarez 81km terrain had 7469 road features which caused virtual blocks crash. After global mapper 6m combine 4056 it still crashed. Finally after I cleanly reduced the features by deleting FCLASS roads to number I didn't write down (damn) and then 6m combine down to 1139 the crash was avoided.
 OSM shapefiles come with all kinds of backyard "path" roads etc, you might want if not have to remove some of these.
@@ Line 169: / Line 173: @@
 ====== Simplify Road Shapefiles ======
-Most likely your OSM downloaded road shapefiles are too complex for terrain builder / arma3, so you need to simplify them. Meaning there are way too many vertices in the polylines which can be reduced.
+**Simplify Road Polylines**
+Most likely your OSM downloaded road shapefiles are too complex for terrain builder, so you //might// need to simplify them. Meaning there are way too many vertices in the polylines which can be reduced. **Note 2018-03-02 update:** arma3 loads any OSM poly line shape file just fine, there is no need to simplify for arma3's sake, PMC has done hundred terrains with various size and quality OSM road poly lines and all of them have been working great.
 If you import too complex or "large" road shapefiles to terrain builder it will start to stutter and freezes up.
@@ Line 176: / Line 182: @@
 From enter simplification threshold dialog, use horizontal threshold 10 and vertical threshold elevation (meters) 0.2 for good results.
+====== Combine Road Features ======
+USA Los Angels 40km terrain openstreetmap.org road polylines even after "bad roads" reduction were over 17,000 features which is like ten thousand over the limit. They need to be reduced. Please note that this was some very odd issue on these specific OSM shapes because normal roads / streets were split up to hundreds of small features when it should have been one feature.
+I have not experienced such splitting up of polylines in other terrains in this scale.
+Select all roads -> RMB in the viewport -> crop/combine/split functions -> combine. Then use about 6 meter value, should work fine (we used also 20m but that might be too large). In select combine options menu let it be default (combine any overlapping and everything else ticked).
@@ Line 223: / Line 238: @@
 [[http://www.mapcruzin.com/free-world-country-arcgis-maps-shapefiles.htm|mapcruzin.com]]\\
 [[http://extract.bbbike.org/|extract.bbbike.org]]