The Data Inspector addresses developers, data scientists, and business analysts. Inspecting data on the HERE platform – structurally as well as visually – can help you understand the data’s value for your use case or can help you debug the data that you produce on the platform yourself.
The Data Inspector essentially consists of these two interfaces:
One that lets you programmatically create a visualization for Protobuf-encoded data by defining which elements of your data shall be presented and in what way. This interface is called a GeoJSON rendering plugin and it transforms your Protobuf-encoded data to GeoJSON.
The point-and-click UI that lets you interact with the data. It offers visual clues on where your data is located and how it is distributed geographically. It lets you view the data visually on a map using a GeoJSON plugin to transform the data and a GeoJSON rendering engine to visualize it. In case the data is already formatted as GeoJSON, it renders directly.
The platform lets you attach a GeoJSON plugin to your schema. So, when you share your data with someone, the schema and the plugin are implicitly shared with it. This way, they can benefit from the visualization that you've created. In fact, a number of platform data sets already have a schema and plugin attached so that you can enjoy automatic decoding and visualization for these data layers out of the box.
Moreover, the Data Inspector allows you to download data for a selected partition for further analysis in these formats:
The Data Inspector allows visualizing the following types of data:
Protobuf-encoded data visualized with custom GeoJSON rendering plugins:
GeoJSON data visualized with the dedicated GeoJSON rendering engine:
Several layers from the HERE Map Content catalog (Cartography, Roads - Topology & Geometry, and Building Footprints) visualized out of the box with the special rendering engine or a dedicated rendering plugin:
The Data Inspector is available as a component integrated in the HERE platform portal as well as in form of a library. For most cases, the portal application is all you need. You can even develop a rendering plugin there. The Data Inspector Library lets you create a customized Data Inspector tool for special cases that you might have. For more information, see the use cases in the chapter below.
The Data Inspector Library allows you to do the following:
Whenever searching for certain types of data stored in the platform, one of the first things you may be interested in is where that data is available geographically.
For HERETiled layers, the Data Inspector provides a coverage map (as a green overlay on top of the base map) that shows the geographical distribution of layer data on a global or local sale, depending on a zoom level.
But if the data is generically partitioned, then there is no way of knowing where the data would be at until you load the data itself – and that can be a very heavy operation. In that case, the platform still offers you the possibility to state in which countries your data is available through a layer description.
For more information on data coverage analysis, see Analyze Data Coverage.
Once you know approximately what the data coverage of a certain layer looks like, you can dive deeper into the contents of the layer, so that you can select a certain catalog for usage in your projects, or maybe even select it for purchase (through HERE Marketplace).
The information on the layer's page in the portal can help you out, of course, but to know more about the data, use the Data Inspector. This tool brings lots of data inspection capabilities, including those listed below:
For more information on inspection capabilities, see the How To chapters.
As a platform pipeline developer, you take platform data as your pipeline input. Then, to ensure that every processing stage fits your overall purpose, you can inspect your pipeline output with the Data Inspector.
The Data Inspector Library allows you to:
View visualized partition data directly in the platform Data Inspector. For this, though, your schema with rendering plugins must be deployed to the platform and bundled with a layer. Equally, your pipeline application must be deployed to the platform, configured, and launched in Pipeline API.
View a local (off-line) partition exactly as it will be visualized in the portal. You can also view a local schema (and rendering plugin) exactly as it would be visualized in the portal. This is the convenient way since all the pipeline development and testing is happening on your local staging environment. Once completed, you deploy a perfectly finetuned pipeline application to the platform.
For more information, see Pipelines Developer Guide.
The platform is extremely flexible in how it allows you to store and structure your data. Every layer can be tiled or non-tiled, and every layer can have its own data format. However, you are recommended to store your data in HERE tiles in GeoJSON or in Protobuf with a well-defined Protobuf schema.
HERETiled GeoJSON layers can be instantly visualized by the Data Inspector.
For more information on rendering plugins, see Create Rendering Plugins.
For more information, see Library Modules Overview.
To build and run applications based on the Data Inspector Library, you need the following:
To get started with the Data Inspector Library, follow these steps:
For the terms and conditions covering this documentation, see the HERE Documentation License.