We are trying to convert Real World Terrain to runtime. Do you have any tips for that?

In general, you made the right observations about features of assets.
But I want to correct you a little bit about the features of Online Maps:

- The size of the map is not fixed, and you can have any size you want.
Usually in cases like yours, the center area is drawn with the map, and the distant plans using Horizon scripts.
https://forum.infinity-code.com/viewtopic.php?id=808

- The map can be real-world sized. Example:
https://infinity-code.com/atlas/online- … ample.html

- Yes, out of the box the Online Maps cannot use SRTM.
But it can be forced by writing your own Elevation Manager, or by intercepting elevation data download requests.
It's not hard if you have a programmer on the team.

Unfortunately, I can't recommend you which asset to choose, but I'll point out that according to your requirements it seems to me that Real World Terrain will suit you better.

I am working on a project which creates digital twin of certain location. Application will able to create an area with online or offline data. the app doesn't need to stream the terrains, terrain should be static and highest quality.

I am planning to use your assets for this project but couldn't decide which one suits more for my needs.

I can summarize the requirements as follows;

- should work runtime on windows build (online and offline)
- should be able to use local or online data (local data without custom server)
- should create huge areas like 100 km2
- should be able to save created terrains
- shoud be able to create buildings with osm and shape files

When I reviewed your applications, I made the following observations;

Real World Terrain:
- Working editor only
- Working with online data sources as tiles
- Creating terrain with offline data only works with custom servers and If I have a big satellite imagery I have to tile myself (correct me if I am wrong)
- Can create huge areas

Online Maps v3
- Working runtime
- Canvas size limited, I can't create 100 km2 area (corret me if I am wrong)
- Unable to maintain real world scale. Scale changes according to canvas size and zoom amount
- Can't use SRTM elevation data (Free bing tiers running out too fast)
- Can't freeze generated terrain and use it offline

These are my observation and assumptions. Whichever asset meets the needs I said more, I can start with it and develop the rest.