The OGC 3D Tiles protocol is designed for streaming and rendering massive 3D geospatial content such as Photogrammetry, 3D Buildings, BIM/CAD, Instanced Features, and Point Clouds from a server to a client. It defines a hierarchical data structure and a set of tile formats which deliver renderable content.
In LuciadCPillar, we support 3D tiles that contain a payload with:
B3DMor Batched 3D Model format)
The OGC 3D Tiles format describes the structure of a 3D tile hierarchy. It consists of:
tileset.json. It can link to other
tileset.jsonfiles or data files.
LuciadCPillar provides support for the MIL-STD-2525B, MIL-STD-2525C, MIL-STD-2525D, APP-6A, APP-6B and APP-6C military standards, and partial support for APP-6D. These standards define a symbol set that is used to plan and execute military operations in support of Command, Control, Communications, Computers, and Intelligence (C4I) functions. The MIL-STD-2525 standards were developed by the United States Department of Defense (DOD), while the APP-6 standards were developed by the North Atlantic Treaty Organization (NATO).
To convert user input into actions on the map, LuciadCPillar offers an API controller toolset. Those map interactions include map navigation, object selection and editing. Using the LuciadCPillar controller API, you can interact with the map with a mouse, keyboard or touch, no matter what UI toolkit you are using.
Find out which data types are supported out-of-the-box, and what some of the commonly used terms mean.
An OGC Web Map Service (WMS) returns static maps, rendered as images. The WMS specification defines a standard web service interface for the retrieval of maps of geographical data over the Internet. In general, a WMS is accessed by a client application that provides the user with interactive controls.
The LuciadCPillar WMS Client API provides an easy framework to connect with a WMS service and use the available data in an application. You can build programs that access all information published inside the WMS capabilities, choose the desired layers and visualize the resulting data on the map.
The client supports automatic re-projection of the retrieved maps, when the geographical reference of the client application is not supported by the WMS. The data is always retrieved using a tiled approach.
The LuciadCPillar API is fully equipped to handle the geodetic aspect of geospatial data with high accuracy: it covers geodetic and Cartesian coordinate reference systems, geodetic datums, transformations and projections, and so on.
Learn about the conventions used in the API for all supported languages.
Learn about common problems and how you can solve them.
LuciadCPillar allows you to create and manage vector data models. You can create geometries from scratch, decode vector data into feature models, and query those feature models to retrieve specific data.
Create geometries within LuciadCPillar.
Set up your system so that you can start developing with LuciadCPillar.
LuciadCPillar provides a API toolset for efficiently visualizing features on the map. You can also style and label those features in accordance with your requirements.
The main entry point for visualization in LuciadCPillar is the map. You use a map to determine which layers to show, and to perform functions such as zooming in on particular areas, limiting the area that the user can see or interact with, determining world position of screen coordinates, and so forth. Here you can read about various topics related to the customization of your map, and learn a number of ways to tailor your map to the application you are building.
LuciadCPillar uses various threads to prepare, process and display data. This way, LuciadCPillar can take advantage of your computer's multiple processor cores, and keep the UI responsive. There are some basic threading rules for LuciadCPillar applications that you can apply to prevent concurrency errors and ensure optimal efficiency.
OGC GeoPackage is an open, standards-based, platform-independent, portable, self-describing, compact format for transferring geospatial information.
LuciadCPillar allows you to create and manage elevation data models from GeoPackage files.
LuciadCPillar allows you to create raster data models. You can create raster models from scratch or decode raster data into raster models.
An OGC Web Map Tile Service (WMTS) serves digital maps in the form of predefined image tiles. The OGC WMTS specification standardizes how a WMTS server publishes the available images, as well as how the images are exchanged between a WMTS server and a WMTS client.
LuciadCPillar provides WMTS model API that allows you to connect to a WMTS server and create a LuciadCPillar WMTS data model.
The Hexagon Smart Point Cloud (HSPC) format offers tiled and multi-leveled point cloud data which can be loaded and visualized natively by LuciadCPillar.
HSPC is a proprietary Hexagon format. Hexagon Geosystems sensors, such as the BLK2GO or the BLK360, produce HSPC data.
The HSPC format describes a 3D tiles hierarchy, using :
Learn how to display and style large-scale point clouds, streamed over the Internet.
LuciadCPillar currently supports OGC 3D Tiles with PNTS points and Hexagon Smart Point Clouds (HSPC).
Learn how to display and style large-scale 3D mesh data, streamed over the Internet.
Learn how to display raster data.
The idea behind the MVC design pattern is to separate the data, the representation of the data, and the user interaction from each other. This separation results in a simpler design of the application and a higher flexibility and re-usability of code.
The LuciadCPillar API consists of the following MVC components:
Get started with the LuciadCPillar API.
GdalModelDecoder to decode and visualize data in the GeoTIFF format (
GdalModelDecoder to decode and visualize data in the Esri Shapefile format (
LuciadCPillar allows you to set up a logging framework to generate and handle log messages from its classes.
Find out how the new features and feature updates of this version can benefit you.
LuciadCPillar allows you to visualize elevation data on the Map as 3D terrain. Geometries are draped on the terrain by default.