For an overview of Data Organization, see the following video.
The data storage hierarchy in the HERE platform consists of the following parts:
There are two categories of layers as follows:
Short term storage (useful for quick access)
Long term storage (better for applications where data retention is required)
If you are creating your own catalog and layers, including a schema for each layer enables you to share data with others by defining how others should consume the data.
For information on catalogs, layers, and partitions, see the Data API.
For an overview of Data Formats, see the following video.
You can upload data to the platform using a variety of file formats. These include:
You can also upload your own files in the format of your choice.
If you want to visualize your data in the platform Data Inspector, you can format your data using GeoJSON or protobuf. GeoJSON renders in the Data Inspector, but protobuf requires a rendering plugin. You can, however, use a HERE protobuf Schema if it suits your use case. These schemas include:
You can also use HERE tools to build your own custom renderer.
By attaching a schema to your layers containing data in a protobuf format, consumers are able to download the schema for decoding by using the generated language bindings in Java and Scala applications. This also allows you to drill down into the contents in the inspector tab.
You can choose a HERE schema for your use, or develop your own using HERE's Maven archetype schema generator and upload them yourself. If you want to work with your own custom schema, you can build a rendering plugin to visualization your data on the map.
If you use HERE's visualization tools, you must specify HERE tile as your partitioning format.