Studio: Customization

Customize the LuciadFusion Studio web front-end and extend the LuciadFusion Platform back-end.

Basics

How-to guides

Frequently asked questions

Reference guides

Studio: Getting started

Get started with LuciadFusion Studio. LuciadFusion Studio is a web-based end-user application to manage your geospatial data. It:

Basics

How-to guides

Frequently asked questions

Reference guides

User guides

Getting Started: Installation

Set up your system so that you can start developing with LuciadFusion.

Basics

How-to guides

Frequently asked questions

Reference guides

Studio: Deployment

Deploy your LuciadFusion Studio application.

Reference guides

Getting Started: LuciadFusion reference information

Find out which product tier gets you what functionality, and read some tips for a smooth interaction with our support desk services.

Basics

How-to guides

Getting Started: Choose your technology

Before starting to build your application, learn about the different options LuciadFusion has to offer. This allows you to pick the one most suited for your application.

Basics

Reference guides

Getting Started: User Guides

The LuciadFusion product comes with a number of end-user applications:

User guides

Studio: REST API

The LuciadFusion Studio REST API allows to automate the data management operations you do in the web interface.

Frequently asked questions

Data Formats: OGC 3D Tiles

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 LuciadLightspeed, we support 3D tiles which contain a payload with:

The OGC 3D Tiles format describes the structure of a 3D tile hierarchy. It consists of:

Basics

How-to guides

Frequently asked questions

Main classes

Data Formats: Luciad Point Cloud format

The LuciadFusion product can preprocess and tile multiple LIDAR data files (LAS/LAZ files) into a single data set. This data set is stored in the Luciad Point Cloud (LPC) format, and the entry file is the tilestore.lpc file.

The LPC data can be served by LuciadFusion using the OGC 3D Tiles protocol, but it can also be opened directly by LuciadLightspeed.

Basics

How-to guides

Frequently asked questions

Main classes

Data Formats: OSGB

OSGB is a file format that originates from OpenSceneGraph. It is supported as an exchange format by various 3D modeling tools. The format describes a hierarchy of textured 3D models, similar to the OGC 3D Tiles format. Each tile is stored in a separate .osgb file, which can use relative paths to reference its children.

For more information, see http://www.openscenegraph.org.

Basics

Frequently asked questions

Main classes

Lightspeed Views: Visualizing vector data

Learn how to display, style and label vector data.

Basics

How-to guides

Frequently asked questions

Main classes

Main packages

Reference guides

Data Formats: Bing Maps

Bing Maps (previously named Virtual Earth) is a web mapping service provided by Microsoft, offering traditional road maps, aerial photo views, and searching capabilities.

The LuciadLightspeed Bing Maps functionality integrates the Bing Maps imagery service into LuciadLightspeed. More specifically, you can do the following:

Basics

Frequently asked questions

Main classes

Reference guides

Lightspeed Views: Interacting with the view

To convert user input into actions on the view, the LuciadLightspeed API uses the concept of a ILspController. Controllers allow the user to use the mouse, keyboard or touch input to:

Basics

How-to guides

Frequently asked questions

Main classes

Main packages

Reference guides

GXY Views: Interacting with the view

To convert user input into actions on the view, the LuciadLightspeed API uses the concept of a ILcdGXYController. Controllers allow the user to use the mouse, keyboard or touch input to:

Basics

How-to guides

Frequently asked questions

Main classes

Main packages

Reference guides

Lightspeed Views: UI widgets

The LuciadLightspeed API offers a number of ready-to-use UI widgets for a Lightspeed view. Examples are

Frequently asked questions

GXY Views: UI widgets

The LuciadLightspeed API offers a number of ready-to-use UI widgets for a GXY view. Examples are

Frequently asked questions

Data Formats: CSV

Geospatial Comma Separated Values (CSV) files are based on the CSV specification. To store the geometry, they use a single column with a Well Known Text (WKT) encoded geometry. For point data, another option is to use separate columns to store the X and Y values.

Basics

Frequently asked questions

Main classes

Main packages

Data Formats: DMED/DTED

Decode and visualize data in the DMED and DTED format (*.dmed, *.dt0, *.dt1, *.dt2).

Basics

Frequently asked questions

Geodesy and Geometry: Geodesy

The LuciadLightspeed 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.

Basics

How-to guides

Frequently asked questions

Main packages

Reference guides

Geodesy and Geometry: Geometry

The LuciadLightspeed Geometry functionality comes with the Advanced GIS Engine component. It provides support for the calculation of binary topological relations, intersection points, the convex hull, and constructive boolean operations of shapes in 2D spaces. This functionality is useful for various applications, for example:

The Advanced GIS Engine component supports the standard LuciadLightspeed shapes. These shapes can originate from any source.

The Advanced GIS Engine component has implementations for a number of 2D spaces: Cartesian, spherical, and ellipsoidal. The mathematical calculations of each implementation are specialized to work in these spaces. For example, the spherical and ellipsoidal implementations work with geodesic lines.

Basics

How-to guides

Frequently asked questions

Reference guides

Data Formats: GeoTIFF and BigTIFF

Decode and visualize data in the GeoTIFF and BigTIFF format (*.tif, *.tiff).

Basics

Frequently asked questions

Getting Started: Installation

Set up your system so that you can start developing with LuciadLightspeed.

Basics

How-to guides

Frequently asked questions

Reference guides

Models: Reading and writing

Models are the containers for geospatial data and their properties.

Learn how to:

Basics

Frequently asked questions

Main classes

Reference guides

Models: Handling vector data

Learn how to decode your vector data into LuciadLightspeed shapes.

Basics

How-to guides

Frequently asked questions

Main classes

Main packages

Third Party Tools: Proguard

Deployed LuciadLightspeed-based applications must be obfuscated. Proguard is a tool that can be used for this purpose.

Basics

Frequently asked questions

Architecture: Services mechanism

The service loader mechanism allows you to query all available instances of an interface, and to register your own instances of an interface. This is used for two reasons:

Basics

Frequently asked questions

Main classes

Main packages

Reference guides

Data Formats: SHP

The shapefile format (shp) is a format developed by Esri to store geospatial vector data and attributes. It can contain points, lines and polygons.

Basics

Frequently asked questions

Main classes

Main packages

GXY Views: Working with the GXY view

The main entry point for visualization in LuciadLightspeed is the view. You start from the view to determine which layers to show on your map, to manage layer object selection, style objects on your map, determine the world position of screen coordinates, and so on. Here you can read about various topics related to the customization of your GXY view, and learn a number of ways to tailor your GXY view to the application you are building.

Basics

How-to guides

Frequently asked questions

Main classes

Main packages

Reference guides

Getting Started: Choose your technology

Learn about the different options LuciadLightspeed has to offer before you start building your application, and pick the most suitable technology up front.

Basics

Frequently asked questions

Reference guides

Getting Started: Product reference information

Find out which data types are supported out-of-the-box, which product tier gets you what functionality, and what some of the commonly used terms mean.

Basics

How-to guides

GXY Views: Asynchronous painting

The GXY view implementation is highly optimized. It allows you to paint domain objects asynchronously to guarantee a responsive view.

Basics

Main packages

Reference guides

GXY Views: Performance

Learn how to ensure the performance of your GXY views.

Basics

Reference guides

Data Formats: GML

The Open Geospatial Consortium's (OGC) Geography Markup Language (GML) is an XML-based data format for describing, storing and exchanging geographical data. LuciadLightspeed provides support for several versions of the GML format. The LuciadLightspeed GML packages allow you to integrate GML data files into LuciadLightspeed applications, encode LuciadLightspeed models to a GML data file, and apply some customizations.

Basics

Reference guides

GXY Views: Visualizing vector data

Learn how to display, style and label vector data.

Basics

How-to guides

Reference guides

Models: Model references

Learn how you can support geospatial data references.

LuciadLightspeed supports a wide range of georeferences. Find out how to integrate your geospatial data reference.

Basics

How-to guides

Reference guides

Models: Working with domain object properties

Vector domain objects typically have a geometry as well as other associated properties. An example might be a model containing road data. Its domain objects do not only contain the road geometry, but they also have properties such as the name of the road, or the speed limit for that road.

You can use those properties in various places:

Much of this functionality is generally available in the LuciadLightspeed API. The only requirement for your model data is that it offers a uniform interface to access those properties. That is what the com.luciad.datamodel.ILcdDataObject interface is for.

Here you will learn how to use and interact with this interface, and how to implement it for your own domain objects.

Basics

How-to guides

Main classes

Main packages

Reference guides

Getting Started: Upgrading LuciadLightspeed

You can set up your development project in a certain way to prepare it for future upgrades of LuciadLightspeed to a new version. Those precautions allow you to maximize the benefit you get from new features and preserve your modifications.

How-to guides

Reference guides

Getting Started: Basic application

Get started with the LuciadLightspeed API, and write your first application.

This page contains a number of tutorials illustrating the basic usage of our API to write your first application.

Basics

Reference guides

Architecture: Logging

LuciadLightspeed allows you to set up a logging framework to generate and handle log messages from its classes. You can also monitor application performance.

Basics

How-to guides

Main classes

Main packages

GXY Views: Visualizing a grid

Learn how to add a grid, such as a typical grid with meridian and parallel lines, to your view with the help of a few grid grid layer implementations in LuciadLightspeed.

How-to guides

Main classes

Main packages

Architecture: Packaging

LuciadLightspeed can be integrated with many technologies and frameworks. You can find out more about logging, internationalization, application container frameworks, obfuscation, and much more.

Basics

How-to guides

Data Formats: Magnetic north

Decode and visualize charts containing magnetic north lines. On such a line the declination of the magnetic north vector is constant. Lines are calculated with a certain interval (e.g. every 5 degrees).

There is support for files containing the parameters of the IGRF or the WMM magnetic model.

Basics

How-to guides

Main packages

Models: Supporting custom formats

Learn how you can add support for your own business data in a custom format.

LuciadLightspeed comes with built-in support for a number of data formats like SHP, GeoJSON, DTED, ... . It also allows you to add support for your own data format by implementing a few interfaces.

Basics

How-to guides

Data Formats: Earth tilesets

LuciadLightspeed allows you to combine multiple and large raster datasets into an Earth tileset. An Earth tileset is multi-leveled and tiled, resulting in great visualization performance.

The recommended way to preprocess datasets is using the Tiling Engine API instead of the Luciad Earth tilesets. Luciad Earth tilesets are only included for reasons of continuity and backward compatibility.

Basics

Frequently asked questions

Main classes

Main packages

Reference guides

Models: Handling raster data

Learn how to decode your raster data as images for image models for further processing and visualization.

Basics

Main classes

Main packages

Reference guides

Architecture: Threads and locks

LuciadLightspeed uses various threads to prepare, process and display data. This way, LuciadLightspeed can take advantage of your computer's multiple processor cores, and keep the UI responsive. There are some basic threading and locking rules for LuciadLightspeed applications that you can apply to prevent concurrency errors and ensure optimal efficiency.

Basics

How-to guides

Main classes

Models: OpenCL

OpenCL enables hardware-accelerated computations. LuciadLightspeed and LuciadFusion use it for line-of-sight computations in the Terrain Analysis Engine component, for instance. OpenCL computations are performed at the model level. This means that OpenCL can be used with Lightspeed views as well as with GXY views.

How-to guides

Lightspeed Views: Troubleshooting

A limited number of hardware platforms or an outdated graphics driver may cause trouble for the OpenGL and OpenCL components of LuciadLightspeed.

Basics

How-to guides

Architecture: Core concepts

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 LuciadLightspeed API consists of the following MVC components:

Basics

Main classes

Third Party Tools: Maven

You can make LuciadLightspeed available through Apache Maven, a development project management and build automation tool.

Basics

Models: Handling multi-dimensional data

Learn how to decode data with multiple dimensions, such as scientific measurement data, so that its dimensions are preserved for filtering and visualization.

Basics

Main classes

Main packages

Third Party Tools: OSGi(TM)

Make your LuciadLightspeed application compatible with an OSGi framework. For more information about OSGi , see http://www.osgi.org.

Basics

Lightspeed Views: Vertical view

LuciadLightspeed allows you to model your geospatial data for representation in a view that is not a map. Such a view is known as a vertical view, or as a profile view. It is typically used to map altitude points over a cross-section of terrain data.

Basics

Main classes

Main packages

GXY Views: Vertical view

LuciadLightspeed allows you to model your geospatial data for representation in a view that is not a map. Such a view is known as a vertical view, or as a profile view. It is typically used to map altitude points over a cross-section of terrain data.

Basics

Main classes

Main packages

OGC Web Server Suite: OGC CSW server

The OGC CSW specification defines a standard interface for catalog services.

A catalog service publishes metadata on geographical data, formatted as records. Instead of returning the data itself, it gives information on how the data may be retrieved. You can compare it to the result of a query of a web search engine. Rather than displaying the requested information, the search engine displays the result of the web search as a number of links and summaries to web pages containing the information requested.

LuciadFusion allows you to build an OGC-compliant Catalog Service for the Web (CSW).

Basics

Reference guides

OGC Standards: OGC Filters

For many applications, you need to identify a particular subset of a data set by specifying a number of conditions, so that you can take further action on that subset only. LuciadLightspeed allows you to use OGC Filters to identify that data subset. OGC Filters are based on a specification by the Open Geospatial Consortium (OGC), which represents the OGC filter in the XML format. In addition, the specification document defines a set of OGC expressions for expressing a computed property of a given object.

The LuciadLightspeed OGC Filter API provides a Java object representation of OGC filters and expressions independently from the XML encoding.

Basics

How-to guides

Main packages

Reference guides

Data Formats: Fusion client

The Fusion client API has two purposes:

Basics

How-to guides

Reference guides

Big Data: Pre-process raster data

The Tiling Engine is a service that organizes geospatial source data in a hierarchical tile structure, called a coverage. This organization into a multi-leveled tile pyramid is called fusion, and optimizes access to the data for the purpose of querying, visualization, and analysis.

The Tiling Engine consists of API that allows you to optimize imagery, elevation, and multi-dimensional data in a pre-processing step. It takes your data, and turns it into a high-performance tile pyramid repository on disk. The resulting multi-leveled coverages allow for a much smoother visualization and analysis experience in Luciad products as well as other OGC clients.

Multi-leveling and tiling data offers advantages in cases similar to these:

The tiles can be stored as individual coverages, or as part of a Tile Store. A Tile Store is a logical structure combining various coverages.

Basics

Reference guides

Big Data: Pre-process point cloud data

Pre-processing point cloud data consists of taking all the point cloud data sets, splitting them up into manageable chunks, and adding multi-leveling in the form of big, lower-quality tiles. The objective of the pre-processing is to make sure that the data set can be served efficiently from a server to a client. The tiled point cloud coverage can be served with a protocol, such as the OGC 3D Tiles protocol.

Basics

Main classes

Data Formats: LAS/LAZ

The LASer format is an exchange format for three-dimensional point clouds. It uses the .las extension.

LASer LiDAR files also come in a compressed variant, called LASzip. In that case, they have the .laz extension.

The specifications are maintained by the ASPRS foundation. See http://www.asprs.org/Committee-General/LASer-LAS-File-Format-Exchange-Activities.html for more information about the specifications.

The LASer format is a binary format roughly consisting of three parts:

Basics

How-to guides

Frequently asked questions

Main packages

Reference guides

Data Formats: E57

The E57 format for point cloud storage consists of two parts:

For more information about the specifics of E57, you can visit the libe57 website at http://libe57.org/.

Basics

How-to guides

Frequently asked questions

Main packages

Reference guides

Data Formats: JPEG2000

Decode and visualize data in the JPEG2000 format (*.jp2, *.j2k).

Basics

Data Formats: JPIP

Decode and visualize data from a JPIP data stream (JPEG 2000 Interactive Protocol).

Basics

Data Formats: KML

Keyhole Markup Language (KML) is an XML-based file format for storing and visualizing geographic data in Earth browsers. The file format was originally developed by Keyhole Inc. for use with their Earth Viewer application, which is currently known as Google Earth.

Basics

Frequently asked questions

Main packages

Reference guides

Data Formats: Collada

An interchange file format for 3D models such as buildings, bridges, monuments, .... .

Frequently asked questions

Lightspeed Views: Visualizing raster data

Learn how to display and style raster data.

Basics

How-to guides

Frequently asked questions

Main classes

Main packages

Reference guides

Lightspeed Views: Working with the view

The main entry point for visualization in LuciadLightspeed is the view. You use a view 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 Lightspeed view, and learn a number of ways to tailor your Lightspeed view to the application you are building.

Basics

How-to guides

Frequently asked questions

Main classes

Main packages

Reference guides

Lightspeed Views: Working with a JavaFX view

If you prefer to build your Lightspeed view with JavaFX GUI components instead of Swing, you can use a TLspFXView. All 2D/3D Lightspeed view and controller functionality in the LuciadLightspeed API remains available to you, no matter what type of Lightspeed view you use.

Basics

Frequently asked questions

Main classes

Main packages

Data Formats: Wavefront OBJ

Decode and visualize data in the Wavefront OBJ format (*.obj).

Basics

Frequently asked questions

Data Formats: OpenFlight

Decode and visualize data in the OpenFlight format (*.flt).

Basics

Frequently asked questions

Lightspeed Views: OpenGL

Find out how and why LuciadLightspeed makes use of the OpenGL API. Also learn about the OpenGL tools offered by LuciadLightspeed to help you develop OpenGL-based applications efficiently.

Basics

How-to guides

Lightspeed Views: Adding graphical effects

Lightspeed views support a number of graphical effects which are applied globally, across all layers. These effects serve to improve the realism, sense of depth or scale, or simply the aesthetics of the images produced by the view. The lighting effect, for example, greatly improves the user's perception of the shape of 3D objects.

How-to guides

Main classes

Main packages

Lightspeed Views: Printing and exporting

LuciadLightspeed allows you to print out the maps displayed in a LuciadLightspeed view, by creating printable objects. In addition, you can display a preview of the layout of your print before you start the printout. Exporting the map to a GeoTIFF file is also a possibility.

Basics

How-to guides

Frequently asked questions

Main classes

Main packages

Lightspeed Views: Visualizing a grid

Learn how to earn how to add a grid, such as a typical grid with meridian and parallel lines, to your view with the help of grid layer builders.

How-to guides

Main classes

Main packages

GXY Views: Visualizing raster data

Learn how to display and style raster data.

Basics

How-to guides

Frequently asked questions

Data Formats: Arc/Info ASCII grid

Decode and visualize data in the Arc/Info ASCII grid format (*.asc, *.grd).

Basics

Data Formats: BIL

Decode and visualize data in the BIL format (*.bil).

Basics

Data Formats: USGS DEM

Decode and visualize data in the USGS DEM format (*.dem).

Basics

Data Formats: ETOPO

Decode and visualize data in the ETOPO format (*.ETOPO2.raw.bin, *.ETOPO2v2_MSP.raw, ETOPO5.DAT).

Basics

Data Formats: GeoJSON

Decode and visualize data in the GeoJSON format (*.json, *.json.gz, *.json.zip, *.geojson).

Basics

Data Formats: LuciadLightspeed JAI

Decode and visualize data in the LuciadLightspeed JAI format (*.jai).

Basics

Lightspeed Views: .NET integration

Although LuciadLightspeed consists of a Java-based API, you can embed it into a .NET application, by coupling the .NET application and its UI components to LuciadLightspeed. As a result, the application gains full access to: the LuciadLightspeed functionality and OpenGL-powered performance.

Basics

Data Formats: MapInfo MAP

Decode and visualize data in the MapInfo MAP format (*.map).

Basics

Data Formats: MapInfo MIF

Decode and visualize data in the MapInfo MIF format (*.mif).

Basics

Data Formats: MapInfo TAB

Decode and visualize data in the MapInfo TAB format (*.tab).

Basics

Models: Clustering model objects

LuciadLightspeed allows you to transform a model so that it clusters objects and you can maintain an overview during visualization. Find out how.

Basics

Main classes

Main packages

Lightspeed Views: Offscreen views

Offscreen views are used in testing scenarios or server use cases. On a server, you often want to build images, but you don't want to visualize them directly on screen. You want to render them to an internal memory buffer instead. Off-screen views are also useful when you want to prepare an image for visualization at a later stage.

Basics

Main classes

Data Formats: OpenStreetMap

Decode and visualize OpenStreetMap raster tiles from a tile server or OpenStreetMap vector data from a database.

Basics

Architecture: Performance guidelines

During the design and implementation phases, you can take several measures to optimize the performance of your LuciadLightspeed application.You can take steps to boost performance at the model level as well as at the view level.

Basics

Lightspeed Views: Performance

Learn how to ensure the performance of your Lightspeed views.

Basics

Big Data: Large vector data sets on a Lightspeed view

The visualization of a large data set on a map poses 2 big challenges:

Here you will learn about the different available options in the LuciadLightspeed API to visualize such large vector datasets on a Lightspeed view.

Basics

Big Data: Large vector data sets on a GXY view

The visualization of a large data set on a map poses 2 big challenges:

Here you will learn about the different available options in the LuciadLightspeed API to visualize such large vector datasets on a GXY view.

Basics

Data Formats: POL

Decode and visualize data in the POL format (*.pol).

Basics

GXY Views: Printing

LuciadLightspeed allows you to print out the maps displayed in a LuciadLightspeed view, by creating printable objects. In addition, you can display a preview of the layout of your print before you start the printout.

Basics

Main classes

Main packages

Data Formats: LuciadLightspeed RST

Decode and visualize data in the LuciadLightspeed RST format (*.rst).

Basics

OGC Standards: OGC SLD Styling

LuciadLightspeed allows you to structure styling information according to OpenGIS Styled Layer Descriptor (SLD) Profile and Symbology Encoding (SE) standards, and apply that styling information to an ILcdModel to create an ILspLayer or an ILcdGXYLayer.

As such, you can separate style from content.

Basics

Frequently asked questions

Main packages

Reference guides

Data Formats: TFW/JGW

Decode and visualize data in the TFW and JGW format (*.tfw, *.jgw).

Basics

Models: ISO metadata standards

Find out how LuciadLightspeed implements standards ISO 19115 and ISO19139, which allow you to add standardized metadata to your data models.

Basics

Main classes

Main packages

Lightspeed Views: Oculus Rift

The Oculus Rift is a virtual reality (VR) head-mounted display. By putting it on, you place yourself in a virtual world. To provide such an immersive experience, the Oculus Rift has several tracking sensors. They allow you to freely look around in the virtual world.

LuciadLightspeed allows you to create LuciadLightspeed applications for the Oculus Rift. It offers the following functionality:

Main packages

Reference guides

Data Formats: OGC GeoPackage

OGC GeoPackage is an open, standards-based, platform-independent, portable, self-describing, compact format for transferring geospatial information.

Basics

How-to guides

Frequently asked questions

Main packages

Reference guides

Data Formats: SQLite SpatiaLite

SQLite SpatiaLite is an extension of SQLite adding fully fledged Spatial SQL capabilities to SQLite.

Basics

How-to guides

Frequently asked questions

Main packages

Reference guides

Data Formats: Oracle Locator

The LuciadLightspeed Database Connectors component provides support for seamlessly integrating Oracle Locator databases into LuciadLightspeed applications. It includes support for the more complex features that are offered by Oracle Spatial, with the exception of Oracle GeoRasters, for which the LuciadLightspeed Oracle Spatial functionality is also required. Within Oracle Locator, both the Relational Model and the Object-Relational Model are supported.

The Relational Model is based on sets of tables, called layers, containing columns with traditional primitive SQL types. When interpreted correctly, they represent various geometries. This representation is fairly difficult to maintain and to work with. The Relational Model is deprecated and no longer supported by Oracle.

This page focuses on the newer Object-Relational Model. It is based on additional SQL types for representing various geometries. These can be inserted as single entities into spatial columns, which can co-exist with traditional non-spatial columns.

The Oracle Spatial User’s Guide and Reference provides all the necessary information on setting up, maintaining, and using spatial databases. This page explains how spatial data can be imported from, and exported to, spatial databases.

Basics

How-to guides

Frequently asked questions

Main classes

Reference guides

Data Formats: DB2 Spatial

The LuciadLightspeed Database Connectors component provides support for seamlessly integrating DB2 Spatial and Geodetic databases into LuciadLightspeed applications.

The DB2 Spatial Extender and the Geodetic Data Management Feature are extensions for the DB2 database system. They introduce additional SQL types for representing various types of geometries. These can be inserted as single entities into the spatial columns, which can co-exist with traditional non-spatial columns. The extensions then provide additional functions for indexing and querying the spatial data.

The IBM manual DB2 Spatial Extender and Geodetic Data Management Feature, User’s Guide and Reference provides all the necessary information on setting up, maintaining, and using spatial databases. This page explains how spatial data in DB2 can be accessed from LuciadLightspeed.

Basics

How-to guides

Frequently asked questions

Main classes

Reference guides

Data Formats: Informix Geodetic

The Informix Geodetic functionality in the LuciadLightspeed Database Connectors component provides support for seamlessly integrating IBM Informix Geodetic databases into LuciadLightspeed applications.

The IBM Informix Geodetic Datablade (IGD) is an extension for the IBM Informix Dynamix Server. The IGD introduces additional SQL types for representing various geometries. These can be inserted as single entities into the spatial columns, which can co-exist with traditional non-spatial columns.

The IBM Informix Geodetic User’s Guide and Reference provides all the necessary information on setting up, maintaining, and using spatial databases. This page explains how spatial data can be imported from, and exported to, spatial databases.

Basics

How-to guides

Frequently asked questions

Main classes

Reference guides

Data Formats: Informix Spatial

The Informix Spatial functionality in the LuciadLightspeed Database Connectors component provides support for seamlessly integrating IBM Informix Spatial databases into LuciadLightspeed applications.

The IBM Informix Spatial Datablade (ISD) is an extension for the IBM Informix Dynamix Server. The ISD introduces additional SQL types for representing various geometries. These can be inserted as single entities into the spatial columns, which can co-exist with traditional non-spatial columns.

The IBM Informix Spatial User’s Guide and Reference provides all the necessary information on setting up, maintaining, and using spatial databases. This page explains how spatial data can be imported from, and exported to, spatial databases.

Basics

How-to guides

Frequently asked questions

Main classes

Reference guides

Data Formats: Microsoft SQL Server databases

The LuciadLightspeed Database Connectors component provides support for the seamless integration of Microsoft SQL Server databases into LuciadLightspeed applications.

The Microsoft SQL Server Documentation provides all the necessary information on the setup, maintenance and use of spatial databases. This page explains how spatial data can be imported from, and exported to, spatial databases.

Basics

How-to guides

Frequently asked questions

Main classes

Reference guides

Data Formats: PostgreSQL PostGIS

The LuciadLightspeed Database Connectors option provides provides support for seamlessly integrating PostgreSQL PostGIS databases into LuciadLightspeed applications.

PostGIS adds support for geographic objects to the PostgreSQL object-relational database. In effect, PostGIS "spatially enables" the PostgreSQL server, allowing it to be used as a backend spatial database for geographic information systems (GIS). PostGIS introduces additional SQL types for representing various geometries. These can be inserted as single entities into the spatial columns, which can co-exist with traditional non-spatial columns.

The PostgreSQL Manual and PostGIS Manual provide all the necessary information on setting up, maintaining, and using spatial databases. This guide explains how spatial data can be imported from, and exported to, spatial databases.

Basics

How-to guides

Frequently asked questions

Main classes

Reference guides

Data Formats: OGC WCS

An OGC Web Coverage Service (WCS) returns coverages. A coverage consists of space-varying information. It is a collection of geospatial data, with property values that vary as geographic locations change. Typical examples of coverages are demographic information like population density, weather charts with temperature information, or elevation maps. The information has not been rendered by the server and is intact.

The OGC WCS specification defines a standard interface for the querying of coverages. The LuciadLightspeed WCS client API provides a simple framework for connecting to a WCS and obtaining coverage data from it.

Basics

How-to guides

Frequently asked questions

Main packages

Reference guides

OGC Web Server Suite: OGC WCS server

Create your own OGC WCS server.

Basics

How-to guides

Reference guides

Data Formats: OGC WFS

A OGC Web Feature Service (WFS) service client allows you to insert, update, delete, query and discover geographic features on an OGC server. WFS delivers GML representations of simple geospatial features in response to queries from HTTP clients. Clients access geographic feature data through WFS by submitting a request for just those features that are needed for an application.

The OGC WFS specification defines a standard interface for querying and manipulating geographic data. Queries can be formulated based on various spatial and non-spatial constraints, as defined by the OGC Filter specification.

A WFS provides geographic information in a rich format, without any prior interpretation or rendering, and with full georeferencing. This contrasts with, for instance, the WMS interface, which renders maps on the server side and returns simple images to the client. The default exchange format for geographic features is GML, another OGC standard.

The LuciadLightspeed WFS client API provides a simple framework for connecting to a WFS and retrieving feature data from it. Additionally, support is offered to send transactions to the WFS, enabling users to update, delete and / or insert features on the server.

Basics

How-to guides

Frequently asked questions

Main packages

Reference guides

OGC Web Server Suite: OGC WFS server

Create your own OGC WFS server.

Basics

How-to guides

Reference guides

Data Formats: OGC WMS

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 LuciadLightspeed 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 in a 2D and 3D view.

The client supports automatic re-projection of the retrieved maps, when the geographical reference of the client application is not supported by the WMS. In addition, you can choose to retrieve the data using a tiled approach, next to the classic map approach. The styling of a layer can optionally be configured through an OGC Styled Layer Descriptor (SLD), if supported by the server.

Next to the ability to retrieve map data, the LuciadLightspeed WMS Client API supports various other requests defined by the WMS specification. This includes support for GetFeatureInfo requests to retrieve more information about a particular point on a map, GetLegendGraphic requests to acquire legend symbols and DescribeLayer requests to obtain feature/coverage-type information for a layer. Vendor specific requests are also supported and can be easily integrated in the API.

Basics

How-to guides

Frequently asked questions

Main packages

Reference guides

Data Formats: OGC WMTS

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.

Since the structure of the image data is strictly defined, visualizing data from a WMTS server is usually much more efficient than from a WMS server.

The LuciadLightspeed WMTS client API provides a model decoder that connects to a WMTS server.

Basics

How-to guides

Frequently asked questions

Main packages

Reference guides

Data Formats: ECDIS

An Electronic Chart Display and Information System (ECDIS) is a computer-based navigation system which is used to visualize digital nautical data, as an alternative to paper nautical charts. Nautical data includes all information which may be of assistance for the safe navigation of vessels at sea and harbors, such as sea depth information, positions of buoys, lights, wrecks, and so on. The data to be rendered can be either vector or raster data.

Data for vector-based ECDIS systems are distributed as cells, called Electronic Navigational Charts (ENC). Each ENC cell contains nautical data for a specific region, ranging from very large regions, such as parts of oceans, to small regions, like berthing areas inside harbors.

Multiple ENC cells may be grouped into a catalogue. Catalogues are useful for the efficient distribution and processing of ENC cells: they provide an index of all their ENC cells, together with the spatial extent of each cell. This allows for the efficient retrieval of geographical data for a specific region and scale, without the need to scan each individual ENC file.

Basics

How-to guides

Frequently asked questions

Reference guides

OGC Web Server Suite: OGC WMS server

Create your own OGC WMS server.

Basics

How-to guides

Reference guides

Data Formats: XML

The LuciadLightspeed XML binding framework allows you to convert XML documents into Java content trees and the other way around. The framework supports other LuciadLightspeed XML-based formats, such as GML, AIXM and OGC Filter.

Basics

Main packages

Data Formats: DIMAP

Decode and visualize DIMAP data.

Basics

Main classes

Data Formats: ECW

Decode and visualize data in the ECW format (*.ecw, *.ers).

Basics

Data Formats: ACE2

Decode and visualize data in the ACE2 format (*.ace2).

Basics

Data Formats: Arc/Info Binary Grid

Decode and visualize data in the Arc/Info Binary Grid format (*.adf).

Basics

Data Formats: Azavea Raster Grid

Decode and visualize data in the Azavea Raster Grid format (*.arg, *.json).

Basics

Data Formats: Magellan BLX Topo

Decode and visualize data in the Magellan BLX Topo format (*.blx, *.xlb).

Basics

Data Formats: BSB Nautical Chart

Decode and visualize data in the BSB Nautical Chart format (*.kap).

Basics

Data Formats: Convair PolGASP

Decode and visualize data in the Convair PolGASP format (*.img).

Basics

Data Formats: ELAS DIPEx

Decode and visualize data in the ELAS DIPEx format .

Basics

Data Formats: USGS First Generation DOQ

Decode and visualize data in the First Generation USGS DOQ format (*.doq).

Basics

Data Formats: USGS New Labelled DOQ

Decode and visualize data in the USGS New Labelled DOQ format (*.doq).

Basics

Data Formats: Arc/Info Export E00 GRID

Decode and visualize data in the Arc/Info Export E00 GRID format (*.e00).

Basics

Data Formats: ERDAS Imagine Raw

Decode and visualize data in the ERDAS Imagine Raw format (*.raw).

Basics

Data Formats: NASA ELAS

Decode and visualize data in the NASA ELAS format .

Basics

Data Formats: ERDAS Imagine

Decode and visualize data in the ERDAS Imagine format (*.img).

Basics

Data Formats: EOSAT FAST Format

Decode and visualize data in the EOSAT FAST Format format .

Basics

Data Formats: GDAL Virtual

Decode and visualize data in the GDAL Virtual format (*.vrt).

Basics

Data Formats: GRASS ASCII Grid

Decode and visualize data in the GRASS ASCII Grid format .

Basics

Data Formats: Golden Software ASCII Grid

Decode and visualize data in the Golden Software ASCII Grid format .

Basics

Data Formats: Golden Software Binary Grid

Decode and visualize data in the Golden Software Binary Grid format .

Basics

Data Formats: Golden Software Surfer 7 Binary Grid

Decode and visualize data in the Golden Software Surfer 7 Binary Grid format .

Basics

Data Formats: NOAA vertical datum shift

Decode and visualize data in the NOAA vertical datum shift format (*.gtx).

Basics

Data Formats: Grid eXchange File

Decode and visualize data in the Grid eXchange File format (*.gxf).

Basics

Data Formats: ENVI .hdr Labelled Raster

Decode and visualize data in the ENVI .hdr Labelled Raster format (*.hdr).

Basics

Data Formats: HF2/HFZ heightfield raster

Decode and visualize data in the HF2/HFZ heightfield raster format (*.hf2).

Basics

Data Formats: USGS LULC Composite Theme Grid

Decode and visualize data in the USGS LULC Composite Theme Grid format .

Basics

Data Formats: SGI Image Format

Decode and visualize data in the SGI Image Format format (*.bw, *.rgb, *.rgba, *.sgi).

Basics

Data Formats: Snow Data Assimilation System

Decode and visualize data in the Snow Data Assimilation System format (*.hdr).

Basics

Data Formats: SRTM HGT Format

Decode and visualize data in the SRTM HGT Format format (*.hgt, *.DEM).

Basics

Data Formats: VTP Binary Terrain Format

Decode and visualize data in the VTP Binary Terrain Format format (*.bt).

Basics

Data Formats: GeospatialPDF

Decode and visualize data in the GeospatialPDF format (*.pdf).

Basics

Data Formats: GeoSPOT

Decode and visualize data in the GeoSPOT format (*.DSC, *.REP).

Basics

Data Formats: MrSID

Decode and visualize data in the MrSID format (*.sid).

Basics

Data Formats: SwissDHM

Decode and visualize data in the SwissDHM format (*.mlt, *.mbl).

Basics

Real Time Data: Dynamic data

Dynamic data introduces a new dimension to existing georeferenced, two-dimensional or three-dimensional data: time. To handle the increased complexity that time adds to that kind of data, the Real-time Engine component provides the com.luciad.realtime package. This package contains components for implementing real-time related functionalities and animations on a map. It provides the ability to play back a simulation in fast or real time, and update one or more map views at desired refresh rates.

An example of the increased complexity handled by the Real-time Engine component is the decluttering of labels for moving objects. Standard labeling algorithms can cause a label to jump from one location to another when overlap is about to occur. The realtime package provides a highly specialized labeling algorithm that gently moves the labels around to avoid overlap.

Main packages

Reference guides

Real Time Data: Radar feeds

Radar feeds in any format can be visualized on a Lightspeed view.

Main packages

Reference guides

Data Formats: Oracle Spatial

The LuciadLightspeed Database Connectors component extends the LuciadLightspeed Oracle Locator functionality by adding support for decoding GeoRaster data stored in Oracle Spatial tables.

The Oracle Spatial GeoRaster book provides a complete description of the tables and data structures used for rasters. Briefly, Oracle rasters are stored in two related data structures, called SDO_GEORASTER and SDO_RASTER, respectively. The first structure contains raster metadata (format and storage parameters, georeferencing, spatial extent, etc) while the second contains the binary data, in a separate table. See http://download.oracle.com/docs/cd/B19306_01/appdev.102/b14254/toc.htm for more information.

Basics

Frequently asked questions

Main classes

Data Formats: Google Earth Enterprise repositories

Decode and visualize data encoded in a Google Earth Enterprise repository.

Important: this functionality still has beta status.

Basics

Main classes

Data Formats: GDF

The package format.gdf is part of the LuciadLightspeed Graph and Routing Engine component, and allows you to access GDF (Geographic Data Files) data. This developer's guide gives a short introduction to the GDF format, and explains how to incorporate it in your LuciadLightspeed applications using the format.gdf package.

With the GDF functionality, you can:

Frequently asked questions

Main classes

Reference guides

Networking and Route Planning: Networking and Route Planning

Many geographical data have a network-like structure: roadmaps, railways, pipelines, ... . The Graph and Routing Engine component offers networking and route planning functionality to support for all kinds of network-related processing. It provides classes for representing graphs and implementations of algorithms for calculating shortest routes in a graph, creating a trace, and so on.

Basics

Reference guides

Terrain Analysis: Elevation data

Learn how to work with elevation data in the Terrain Analysis API.

Reference guides

Terrain Analysis: Contours

LuciadLightspeed provides several contour finders in the package com.luciad.contour. Refer to the javadoc of that package for an overview of the API.

Main packages

Reference guides

Terrain Analysis: Extreme points

Calculate the lowest and highest points in an area.

Reference guides

Terrain Analysis: Hypsometry

The Terrain Analysis Engine provides support to compute and display hypsometric views of elevation data.

Reference guides

Terrain Analysis: Line of sight

The Terrain Analysis Engine provides classes to compute the line-of-sight between two points and between a point and its environment. Both direct and radar line-of-sight computations are supported. Due to radar wave properties a radar can look over the hill. How far it can see over the hill is controlled by the K-factor which is a measure for atmospheric reflection of radar waves. In practice the radius of the earth will be multiplied with the K-factor, thus flattening the earth and extending the horizon. A typical value for the K-factor is 4/3.

Reference guides

Terrain Analysis: Viewsheds

The Terrain Analysis Engine provides viewsheds to compute which parts of a threedimensional scene are visible in the presence of obstacles like buildings and terrain. Conceptually a viewshed divides a volume into visible and invisible regions with respect to an observer. For instance it answers the following questions:

In general, a viewshed defines an interface to determine whether any point in threedimensional space is visible or not.

Reference guides

Terrain Analysis: Visibility

The Terrain Analysis Engine provides functionality to compute the visibility from a shape to another shape. This computation is illustrated in the sample samples.tea.gxy.visibility.MainPanel. By using the shape-to-shape visibility computations, the following questions can be answered:

Reference guides

Data Formats: NetCDF

The NetCDF data format describes array-oriented scientific data.

NetCDF scientific weather data is stored as gridded datasets. The types of measurement and the dimensions along which they are measured determine the structure of the datasets. The measurements are referred to as variables. Temperature, humidity, and cloud cover are all examples of variables. The dimensions of the measurements typically consist of the location coordinates of the measurement, the time of the measurement, and other parameters, such as the altitude at which the measurement was taken. For instance, atmospheric temperature can be measured at a specific location, but at multiple times and vertical positions. These measurements results in a NetCDF temperature dataset, with measurement grids organized along the spatial, temporal and vertical dimensions.

By default, NetCDF allows multiple sets of variables in a single file, so one file can contain both salinity and temperature measurements for example.

The NetCDF standard itself does not impose any semantic rules or conventions, just like XML files or comma-separated value files.

LuciadLightspeed mainly uses the NetCDF format to decode data that complies with the Climate and Forecast (CF) Metadata Conventions. The CF conventions define metadata that describe what the data in each NetCDF variable represents, and the spatial and temporal properties of this data. The data model is widely used in climate and weather forecast systems and in other geoscience communities, and has been adopted by the Open Geospatial Consortium.

Basics

How-to guides

Frequently asked questions

Reference guides

Data Formats: GRIB

GRIB (GRIdded Binary or General Regularly-distributed Information in Binary form) is a concise data format. It is commonly used in meteorology to store historical and forecast weather data.

Basics

How-to guides

Frequently asked questions

Reference guides

Data Formats: BUFR

The Binary Universal Form for the Representation of meteorological data (BUFR) format describes weather features and other natural phenomena such as volcanic activity.

BUFR is a binary format that contains the location and other details of weather and other natural phenomena, such as clouds, jet streams, volcanoes, and tropical cyclones. The World Area Forecast System (WAFS) produces Significant Weather (SIGWX) bulletins in the BUFR format. LuciadLightspeed can decode these WAFS SIGWX files as vector features and visualize the data in a manner similar to the SIGWX charts that WAFS also produces.

LuciadLightspeed only supports decoding WAFS SIGWX BUFR files. BUFR files that do not follow this standard cannot be decoded.

Basics

How-to guides

Main classes

Data Formats: AIXM 3.3/4.x

The Aeronautical Information Exchange Model or AIXM is an XML-based data format developed by Eurocontrol to encode and distribute aeronautical information. The format contains support for a wide variety of aeronautical data, such as airports, airspaces, routes, navaids and procedures. This developer’s guide focuses on the use of AIXM versions 3.3, 4.0 and 4.5, on which the implementation in the format.aixm package is based. Detailed information about the AIXM format and the various specifications can be obtained from Eurocontrol’s website.

The AIXM component allows you to:

Basics

Frequently asked questions

Main packages

Reference guides

Data Formats: DAFIF

The DAFIF specification defines a data format for a wide variety of aeronautical information, such as air spaces, routes, waypoints, navaids, airports and runways. This page describes how you can decode and visualize this data using the LuciadLightspeed API.

Basics

Frequently asked questions

Main packages

Reference guides

Data Formats: ARINC

The ARINC 424 specification defines a data format for a wide variety of aeronautical information, such as airspaces, routes, waypoints, navaids, airports, heliports and runways. The ARINC 424 specification can be obtained from the ARINC website.

The ARINC component allows you to:

Basics

Frequently asked questions

Main packages

Reference guides

Data Formats: AIXM 5

The Aeronautical Information Exchange Model (AIXM) is an XML-based aeronautical data format developed jointly by Eurocontrol and FAA. It is designed to enable the management and distribution of Aeronautical Information Services (AIS) data in digital format. The format contains support for a wide variety of aeronautical data, such as airports, airspaces, routes, navaids, and procedures. It also covers dynamic data, which is known as Digital NOTAM , and electronic Terrain and Obstacle Data (eTOD). Detailed information about the AIXM format and the various specifications can be obtained from Eurocontrol’s website. For more information, please visit http://www.aixm.aero.

The AIXM 5.1 component allows you to:

Basics

How-to guides

Frequently asked questions

Reference guides

Data Formats: Binz

Decode data in the Binz format (*.binz), and convert it to OGC 3D Tiles data.

Basics

Main classes

Reference guides

Data Formats: Microstation DGN

Decode and visualize data in the Microstation DGN format (*.dgn).

Basics

Frequently asked questions

Data Formats: AutoCAD DWG and DXF

Decode and visualize data in the AutoCAD DWG and DXF format.

Basics

Frequently asked questions

Big Data: Pre-process 3D meshes to OGC 3D Tiles

Use a 3D Tiling Engine to tile and multi-level 3D meshes to a 3D Tiles tileset optimized for streaming. You have access to a command line sample that supports OBJ input files and georeferencing, and a more flexible API that allows you to plugin custom mesh formats and custom references.

Basics

How-to guides

Data Formats: BCI

Decode and visualize data in the BCI format (*.matrxmap).

Basics

Data Formats: MGCP

The LuciadLightspeed Defense Standards component includes the package com.luciad.format.mgcp for creating MGCP layers.

The MGCP functionality allows you to:

Basics

Main packages

Reference guides

Data Formats: CADRG

Decode and visualize data in the CADRG (Compressed ARC Digitized Raster Graphics) format (*.toc).

Basics

Frequently asked questions

Main classes

Data Formats: CIB

Decode and visualize data in the CIB (Controlled Image Base) format.

Basics

Main classes

Data Formats: ECRG

Decode and visualize data in the ECRG format (TOC.xml).

Basics

Data Formats: NITF/NSIF

Decode and visualize data in the NITF/NSIF (STANAG 4545) format (*.ntf).

Basics

Data Formats: ASRP/USRP/ADRG

Decode and visualize data in the ASRP/USRP/ADRG format (01.THF, *01.GEN, *01.QAL, .SOU, *.IMG).

Basics

Data Formats: VPF

The LuciadLightspeed Defense Standards component includes the package com.luciad.format.vpf for decoding and displaying Vector Product Format (VPF) data.

The VPF functionality allows you to:

Basics

Frequently asked questions

Main packages

Reference guides

Data Formats: ASDI

The package com.luciad.format.asdi provides the ability to decode and display ASDI data. It enables to decode ASDI data from a file or from a live stream. It enables to replay ASDI data from a file as if it came from a live stream. Finally it offers access to the parsed messages directly, offering fine-grained control.

The FAA provides airlines and other aviation-related organizations with access to near real-time air traffic data from the National Airspace System (NAS) through the ASDI feed of the Enhanced Traffic Management System (ETMS). More information on ASDI can be obtained from http://www.fly.faa.gov/ASDI/asdi.html.

Main packages

Reference guides

Data Formats: ASTERIX

ASTERIX is the EUROCONTROL standard for exchanging ATM surveillance data. More information on the ASTERIX standard can be obtained from EUROCONTROL http://www.eurocontrol.int/asterix/.

The LuciadLightspeed Radar Connectors component offers the com.luciad.format.asterix package. The ASTERIX functionality provides the ability to decode and display ASTERIX data. It allows you to decode ASTERIX data from a file or from a live stream of radar data. It also allows you to replay ASTERIX data from a file as if it came from a live stream.

Basics

Frequently asked questions

Main packages

Reference guides

Symbology: Military Symbology

The Defense Symbology component 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). Additionally, support is offered for TTA-106 V4. This is a military standard developed by DGA (Direction Générale de l’Armement). It extends the APP-6A symbology with a number of new units and tactical symbols.

The Defense Symbology component allows a LuciadLightspeed user to create MIL-STD 2525b, MIL-STD 2525c, MIL-STD 2525d, APP-6A, APP-6B, APP-6C and a subset of the APP-6D symbols and visualize them on a map. The MIL-STD and APP-6 standards each have a separate package in the API, but their use is completely analogous.

Basics

How-to guides

Frequently asked questions

Reference guides

Data Formats: NVG

NATO Vector Graphics address the requirement to unambiguously convey and display situational awareness information suitable for a Common Operational Picture (COP).

NVG consists of a data/file format for the encoding of battle space objects into overlays, and protocols for the automated exchange of the overlays.

The NVG functionality in LuciadLightspeed allows you to:

Basics

How-to guides

Frequently asked questions

Reference guides