GeoJSON Data

GeoJsonDataSource allows you to render geometric objects provided in the GeoJSON format. It corresponds with the RFC7946 GeoJSON Specification and supports the following geometry types:

• Point
• LineString
• Polygon
• MultiPoint
• MultiLineString
• MultiPolygon

Supported geometric objects with additional properties are Feature objects. Sets of Feature objects are contained in the FeatureCollection objects.

This data source supports the following custom style properties for Feature objects:

• tooltip
• style.color
• style.fill
• radius and more

For more information on supported custom style properties, see Style GeoJSON Visualization.

Supported Data Providers

The GeoJSON data source supports these data providers:

• A direct GeoJSON object, which you can provide by uploading a file.
• A catalog layer from the Data Service where Content-Type is application/geo+json or application/vnd.geo+json and the data is in the GeoJSON format.
• A catalog layer from the Data Service with rendering plugins that can decode any data into the GeoJSON format.
• A catalog layer that references road segments and their offsets for location referencing instead of longitude and latitude values that can be visualized with rendering plugins.

If you use the Data API, the catalog layer must be of type versioned or volatile and use the HERE Tile partitioning scheme. For more information on partitioning, see the Partitions chapter in the Data User Guide.

Connect to Data Service

The GeoJSON data source renders the data contained in the layers whose Content-Type is application/geo+json or application/vnd.geo+json without decoding it.

Otherwise, the protobuf.js library is used to decode the raw data from the layer into a JSON object. The JSON object is then decoded into a GeoJSON object using the relevant rendering plugin.

const geoJsonDataSource = new GeoJsonDataSource({
    dataStore: {
        hrn: HRN.fromString("Your HRN string"),
        layer: "Layer name",
        getBearerToken: () => Promise.resolve("Your Token")
    }
});
mapView.addDataSource(geoJsonDataSource);

// Select tile when data source is ready
mapView.addEventListener(MapViewEventNames.DataSourceConnect, () => {
    geoJsonDataSource.selectTile(geoJsonDataTile);
});

Rendering plugins can be present in a Data Service catalog or included from a local file. If your catalog does not have a rendering plugin, you can create your own JavaScript JSON-to-GeoJSON translator and visualize the data with the GeoJSON data source.

To use your own plugin, update the parameter externalRenderingPluginName with the name of your plugin like in the following example:

const geoJsonDataSource = new GeoJsonDataSource({
    dataStore: {
        hrn: HRN.fromString("Your HRN string"),
        layer: "Layer name",
        getBearerToken: () => Promise.resolve("Your Token")
    },
    externalRenderingPluginName: "renderer.plugin.template" // `renderer.plugin.template.js` file must be placed into project root directory
});
mapView.addDataSource(geoJsonDataSource);
mapView.addEventListener(MapViewEventNames.DataSourceConnect, () => {
    geoJsonDataSource.selectTile(geoJsonDataTile);
});

Provide a GeoJSON Object

const geoJsonDataSource = new GeoJsonDataSource({});
mapView.addDataSource(geoJsonDataSource);

const geoJsonData: FeatureCollection = {
    "type": "FeatureCollection",
    "features": [
        {
            "type": "Feature",
            "properties": {},
            "geometry": {
                "type": "Point",
                "coordinates": [
                    16.4074,
                    39.9042
                ]
            }
        }
    ]
};

mapView.addEventListener(MapViewEventNames.DataSourceConnect, (event: any) => {
    if (event.dataSourceName === geoJsonDataSource.name) {
        geoJsonDataSource.renderGeoJson(geoJsonData); // visualize GeoJSON object
    }
});

Optional Parameters

• intersectionAgent { InteractiveIntersectionAgent }: An instance of InteractiveIntersectionAgent that fires events when someone interacts with a geometry object. Use it to set custom handlers for mouse-over events or to display geometry tooltips.

• dataStore { GeoJsonDataStoreParameters & DataStoreClientParameters }: Connection parameters to provide data from the Data Service. If omitted, the data source can still take the GeoJSON data that you pass into renderGeoJson.

• externalRenderingPluginName { string }: The name of a custom rendering plugin. A JavaScript file with the same name or with the prefix rendering. must exist in the project's root directory. This rendering plugin is used instead of the standard plugin that comes with the Data Service.

GeoJSON from Catalog Example App

Before you can visualize GeoJSON data from a catalog, you need to know one of the following:

• The HERE Resource Name (HRN) of the layer whose Content-Type is application/geo+json or application/vnd.geo+json
• The HRN of the catalog where a rendering plugin is published and that has Scheme.hrn defined in the catalog configuration.

You can create and extend your own schemas by using Maven archetypes in the HERE Data SDK for Java & Scala. For more information, see the Create and Extend Schemas chapter in the Archetypes Developer Guide.

To visualize some test data first, you can use the following public sample catalog:

HRN: "hrn:here-cn:data::olp-cn-here:cn-1"
layer name: "geojson"
level: "12"

To visualize GeoJSON data from a catalog, follow these steps:

1. Install the web app generator and enter your application name when prompted.

2. When prompted What kind of data will you visualize on top of the Base map?, select the option GeoJSON from a data layer.

3. When prompted HRN of the Catalog you want to visualize?, enter the HRN of the catalog that contains GeoJSON data.

4. When prompted Name of the layer you want to visualize?, enter the name of the layer containing a GeoJSON rendering or the HRN of the layer whose Content-Type is application/geo+json or application/vnd.geo+json.

5. When prompted On which level the data is stored?, enter the minimum zoom level that is required for the data to render.

6. Once the code is generated, you can build and serve the web app by running the following command:

   npm run start
   

7. Open http://localhost:8080 in your favorite web browser to see the generated app.

   To see the base map, update the authentication form with the credentials that you obtained from the platform portal.

GeoJSON Data from File Example App

After you generate the web app (see the example above), you need to upload your GeoJSON file. If you want to visualize some test data first, you can use the following GeoJSON sample:

{
    "type": "FeatureCollection",
    "features": [
        {
            "type": "Feature",
            "properties": {
                "tooltip": "You can have some tooltip for each Feature",
                "style": {
                    "fill": "blue"
                }
            },
            "geometry": {
                "type": "Polygon",
                "coordinates": [
                    [
                            [116.404, 39.899],
                            [116.450, 39.858],
                            [116.530, 39.868],
                            [116.541, 39.921],
                            [116.471, 39.937],
                            [116.404, 39.899]
                    ]
                ]
            }
        }
    ]
}

To visualize GeoJSON data from the file, follow these steps:

1. Install the web app generator and enter your application name when prompted.

2. Select the option GeoJSON from a file when prompted What kind of data will you visualize on top of the Base map?.

3. Once the code is generated, you can build and serve the web app by running the following command:

   npm run start
   

4. Open http://localhost:8080 in your favorite web browser to see the generated app.

   To see the base map, update the authentication form with the credentials that you obtained from the platform portal.