Library Modules Overview

This chapter provides an overview of the main HERE Data Inspector Library modules. For a full list of Data Inspector Library components, see the Data Inspector Library API Reference.

UI Components

  • @here/interactive-mapview-ui: A package that contains core Data Inspector Library UI components:

    • DataInspector: A configurable UI widget that combines the MapView class with multiple widgets. DataInspector represents the main Data Inspector window that you can access from the portal or when running Data Inspector Library example applications.

    • DecodedPanel: A UI widget that allows displaying decoded partition data, partition ID, partition size, and the timestamp of the last update of the data contained in a selected partition(s) (for versioned layers only).

      This widget also displays the Download data button. For a selected partition, this button allows downloading raw data, data decoded with the linked Protobuf schema, and GeoJSON data translated with the rendering plugin.

      Any errors that may occur during the partition data decoding process are also displayed in this panel.

      The DecodedPanel widget includes a resize handle that allows you to resize the panel horizontally.

      When you select a certain feature of a data source in the map view, the DecodedPanel highlights the data for this specific feature.

    • ControlPanel: A UI element that serves as a container for other widgets, such as UserAuthForm or InteractiveFilteringControl.

    • ToolBar: A UI widget with various controls for the map and data sources. This widget is commonly used as part of the DataInspector class, but you can also use the ToolBar class as a standalone component.

      The toolbar may contain buttons for showing and hiding the Control Panel, Map View, Partitions List, and Decoded Panel, as well as the language switcher and a full screen button. For more details, see the ToolBarState API reference.

    • InteractiveFilteringControl: A UI component that allows showing or hiding specific features of a data source.

    • InfoPanel: This class is used to display an infopopup that shows a detailed list of feature properties (as key-value pairs) on click. To define the details you want to show in the infopopup, use the description style property of a GeoJSON object. description can be applied to any geometry type. To implement this control, use the installInfoWidgets method (import { installInfoWidgets } from "@here/interactive-mapview-ui/lib/Utils";).

    • InfoTooltip: This class is used to display short info in a tooltip on a visualized feature on hover. To define the details you want to show in the tooltip, use the title style property of a GeoJSON object. title can be applied to any geometry type. To implement this control, use the installInfoWidgets method (import { installInfoWidgets } from "@here/interactive-mapview-ui/lib/Utils";).

    • InteractiveStatsPanel: A UI component that displays runtime information from connected data sources. For example, you can see what events were triggered, or get statistics on how long it takes to download and decode partition data.

    • UserAuthForm: A UI form that allows you to enter your platform credentials. You can use it along with the @here/olp-sdk-authentication module (the UserAuth class) to provide data sources with a valid access token.

    • ZoomLevelWidget: A UI widget that shows the current MapView zoom level and allows you to switch between zoom levels.

      Note

      You can also use double-click zooming functionality integrated into the DataInspector. By double-clicking in the map view, the map is zoomed in by one level, and by right-double-clicking in the map view, the map is zoomed out by one level. The location that you click, in this case, stays in the same screen position under the mouse cursor.

    • RenderingSettings: A UI widget with a set of controls that allow you to quickly develop and run rendering plugins for both custom and default layer schemas. For more information, see the Create Rendering Plugins chapter.

    • RenderingPluginEditorMonaco: A component that uses Monaco Editor for live JavaScript syntax check and autocompletion. For more information, see the Create Rendering Plugins chapter.

    • VersionPicker: A widget used by the DataInspector class to choose the version of the catalog currently displayed in the DataInspector's data source. This class has a set of UI widgets for showing the current catalog's version in the DataInspector's ToolBar class and a modal dialog box that enlists all the catalog's versions.

    • TileMenu: A context menu for a tile that allows copying the ID of the currently selected partition in MapView, decode partition data, view and copy the geocoordinates of the currently selected location on the map. Also, for a selected partition, this menu allows downloading raw data, data decoded with the linked Protobuf schema, and GeoJSON data translated with the rendering plugin.

      You should create an instance of TileMenu only once and further operate via the TileMenu.setState method.

    • StatusBar: A UI widget that allows showing various status messages to users. This component is automatically created by the DataInspector but can also be used without it.

    • SdiiControls: A set of control widgets for @here/sdii-datasource that allow for SDII features filtering: switching on/off paths, different types of road signs, or other events.

    • RibControls: A set of control widgets for @here/rib-datasource that allow for HERE Map Content Data features filtering: switching on/off segments, nodes from the Topology layer, different categories of objects from the Roads - Topology & Geometry and Building Footprints layers.

    • CoverageControls: A UI widget that contains controls for adjusting the appearance of a data size heat map.

    • MapControlHandler: A class that enables interaction with the MapView using mouse or touch events.

    • TileControlHandler: A class that provides tile-selection and mouse-hover functionality for the InteractiveDataSource and CoverageDataSource. This component also allows controlling the context menu displayed by right-clicking a tile. TileControlHandler is automatically created by the DataInspector but can be also used without it.

    • SearchComponent: A UI widget that is used to search for a partition ID, specific geographical coordinates (lat/long), locations, and places. Also, this component provides the history of recent searches. It is enabled by default.

  • @here/fileupload: A UI file upload field with a button for the @here/olp-geojson-datasource component that you can use to upload GeoJSON files. This data is then immediately rendered by the @here/olp-geojson-datasource.

Data Sources

External Dependencies for Data Sources

  • three.js: A cross-browser JavaScript library for WebGL
  • protobufjs: A protobuf parser for JavaScript
  • earcut: A polygon triangulation library

A full list of dependencies can be found in the External Dependencies chapter.

Utility Components

  • @here/interactive-datasource-protocol: This component provides an abstract base class that you can use to start developing your own data sources that support features, raycasting, and more. Any custom data source should extend the InteractiveDataSource class and support the following actions:
    • Select and deselect tiles.
    • Select and highlight features.
    • Render multiple tiles of levelWithData on multiple zoom levels (via a composed tile feature).
    • Perform raycasting with InteractiveIntersectionAgent including mouse-over and click functionality for each feature.

  • @here/geometry-data-provider: Because some data has no geometry information in it, but can be mapped to other geometry, this component provides geometry to visualize the types of data that relies on it.

    This component contains classes for providing road geometry that can be used for visualizing such data as traffic and speed limits.

  • @here/generator-visualization-app: Generates a sample web app with a set of custom-defined Data Inspector Library components. Use it to create your own base application and to develop a custom data source.

results matching ""

    No results matching ""