About the Project¶
osgEarth is a 3D mapping SDK for OpenSceneGraph applications. It’s different than traditional terrain engines in an important way: osgEarth does not require you to build a 3D terrain model before you display it. Instead, it will access the raw data sources at application run time and composite them into a 3D map on the fly. No terrain model is actually stored to disk, though it does use caching techniques to speed up the rendering of the map.
The goals of osgEarth are to:
- Enable the development of 3D geospatial appliations on top of OpenSceneGraph.
- Make it as easy as possible to visualize terrian models and 3D maps.
- Interoperate with open mapping standards, technologies, and data.
So if it for me?
So: does osgEarth replace the need for offline terrain database creation tools? In many cases it does.
Consider using osgEarth if you need to:
- Get a terrain base map up and running quickly and easily
- Access open-standards map data services like WMS, WCS, or TMS
- Integrate locally-stored data with web-service-based data
- Incorporate new geospatial data layers at run-time
- Run in a “thin-client” environment
- Deal with data that may change over time
- Integrate with a commercial data provider
Since osgEarth is a free open source SDK, the source code is available to anyone and we welcome and encourage community participation when it comes to testing, adding features, and fixing bugs.
The best way to interact with the osgEarth team and the user community is through the support forum. Please read and follow these guidelines for using the forum:
- Sign up for an account and use your real name. You can participate anonymously, but using your real name helps build a stronger community (and makes it more likely that we will get to your question sooner).
- Limit yourself to one topic per post. Asking multiple questions in one post makes it too hard to keep track of responses.
- Always include as much supporting information as possible. Post an earth file or short code snippet. Post the output to
osgearth_version --caps. Post the output to
gdalinfoif you are having trouble with a GeoTIFF or other data file. List everything you have tried so far.
- Be patient!
The osgEarth team supports its efforts through professional services. At Pelican Mapping we do custom software development and integration work involving osgEarth (and geospatial technologies in general). We are based in the US but we work with clients all over the world. Contact us if you need help!
This means that:
- You can link to the osgEarth SDK in any commercial or non-commercial application free of charge.
- If you make any changes to osgEarth itself, you must make those changes available as free open source software under the LGPL license. (Typically this means contributing your changes back to the project, but it is sufficient to host them in a public GitHub clone.)
- If you redistribute the osgEarth source code in any form, you must include the associated copyright notices and license information unaltered and intact.
- iOS / static linking exception: The LGPL requires that anything statically linked to an LGPL library (like osgEarth) also be released under the LGPL. We grant an exception to the LGPL in this case. If you statically link osgEarth with your proprietary code, you are NOT required to release your own code under the LGPL.