OLP Release Announcements

Open Location Platform 2.2.0 release

By HERE Technologies team | 15 January 2019

Highlights

Account & Permissions

Group Level Administration

Any users can now create groups, reducing the burden on organization level Admin to administer all groups.

The creator of the group becomes the default Group Admin, giving them permissions to administer the group, including:

  • Add users and apps to the group
  • Remove users and apps from the group
  • Delegate other users in the group as Group Admins.

With this change, the former Admin role is now an Org Admin. As before, Org Admins can manage group membership, but they also now receive the ability to delegate other users in a group to be Group Admins.

Therefore, groups can now be administered by:

  • the creator of the group
  • a delegated Group Admin
  • an Org Admin

In the event that you created many Org Admins to distribute the administrative load, you can now reduce the number of Org Admins, relying instead of self-organizing groups to administer their own membership.

Note that new users must be invited by an Org Admin, as before.

Map Content

Map data version is as follows:

  • Global View, including:
    • Asia Pacific (APAC)
    • Middle east / Africa (MEA)
    • India (RN)
    • Antarctica (ANT)
    • Taiwan (TWN)
    • South America (SAM)
    • Western Europe (WEU)
    • Australia (AU)
    • North America (NA)
    • Eastern Europe (EEU)

Pipelines

Known Issues

Issue

A pipeline failure or exception can sometimes take several minutes to respond.


Issue

If multiple pipelines consuming data from a single stream layer all belong to the same group (pipeline permissions are managed via a group), then each of those pipelines will only receive a subset of the messages from the stream. This is due to the fact that the pipelines share the same Application ID.

Workaround

Use the Data Library to configure your pipelines to consume from a single stream. If your pipelines/applications use the Direct Kafka connector type, you can specify a Kafka consumer group ID per pipeline/application. If the Kafka consumer group IDs are unique, the pipelines/applications will consume all messages from the stream.

If your pipelines use the HTTP connector type, we recommend that you create a new group for each pipeline/application, each with its own application ID.


Issue

Pipelines are not private to a user by default; they must be shared with exactly one group when created.

Workaround

Share the pipeline with a group containing only one user.


Issue

Pipelines can only be shared with users who belong to the same group.

Workaround

Share the pipeline with a group containing the specific set of users.

Data

Added

  • The HERE Live Weather Europe data catalog has increased coverage into Eastern Europe.

Known Issues

Issue

Catalogs not associated with a realm are not visible in OLP.


Issue

Data encryption is limited to:

  • Versioned data at rest
  • Stream layer data
  • Index layer data
  • Notebooks

In-flight data encryption is not consistently implemented across OLP.

You should not send sensitive data or personal information to OLP at this time.


Issue

When you use the Data API or Data Library to create a catalog or layer, the app credentials used do not automatically enable the user who created those credentials to discover, read, write, manage and share those catalogs and layers.

Workaround

After the catalog is created, use the app credentials to enable sharing with the user who created the app credentials. You can also share the catalog with other users, apps and groups.


Issue

When creating an Index Layer and processing stream data in a data archive pipeline, it is possible to select Parquet as a data format. However, a corresponding Spark Connector is not available with this release, making it non-trivial to consume data in this format. As a mitigation, we recommend you not use Parquet format with this release.


Issue

Some older catalogs cannot be shared temporarily because the catalog owners don't have permissions assigned to them yet. This issue only applies to older catalogs. Contact us to report each occurrence as a bug.

Notebooks

Known Issues

Issue

Notebooks do not support Flink.


Issue

Neither platform.here.com nor Notebooks are compatible with Internet Explorer 11.


Issue

Notebooks do not contain support for Stream Layers.


Issue

Notebooks only support Python 3.

Account & Permissions

Added

  • Added feature for group level administration. Any users can now create groups. Groups are administered by the group creator, by designated group admins, and/or by organization admins.

Known Issues

Issue

A finite number of access tokens (~ 250) are available for each app or user. Depending on the number of resources included, this number may be smaller.

Workaround

Create a new app or user if you reach the limitation.


Issue

Only a finite number of permissions are allowed for each app or user in the system across all services. It will be reduced depending on the inclusion of resources and types of permissions. Delete pipelines/pipeline templates to recover space.


Issue

All users and apps in a group are granted permissions to perform all actions on any pipeline associated with that group. There is no support for users or apps with limited permissions. For example, you cannot have a reduced role that can only view pipeline status, but not start and stop a pipeline. Limit the users in a pipeline's group to only those users who should have full control over the pipeline.


Issue

When updating permissions, it can take up to an hour for changes to take effect.

Map Content

Added

  • The following new layers have been introduced in HERE Map Content.

  • HERE Map Content: HERE Places

  • HERE Map Content: Places for HERE Essential Map
  • HERE Map Content: Places Metadata

Changed

  • This section describes data format version changes.
Old Version New Version Change
v2:2.4.0 v2:2.5.0 Released Places protos
v2:2.5.0 v2:2.6.0 Added SocialSignal message to Places proto
  • HERE Map Content uses the following data formats:
Data Format
hrn:here:schema:::com.here.schema.rib:topology-geometry_v2:2.6.0
hrn:here:schema:::com.here.schema.rib:road-attributes_v2:2.6.0
hrn:here:schema:::com.here.schema.rib:address-attributes_v2:2.6.0
hrn:here:schema:::com.here.schema.rib:administrative-places_v2:2.6.0
hrn:here:schema:::com.here.schema.rib:placelocations_v2:2.6.0
hrn:here:schema:::com.here.schema.rib:cartography_v2:2.6.0
hrn:here:schema:::com.here.schema.rib:building-footprints_v2:2.6.0
hrn:here:schema:::com.here.schema.rib:navigation-attributes_v2:2.6.0
hrn:here:schema:::com.here.schema.rib:advanced-navigation-attributes_v2:2.6.0
hrn:here:schema:::com.here.schema.rib:lane-attributes_v2:2.6.0
hrn:here:schema:::com.here.schema.rib:street-names_v2:2.6.0
hrn:here:schema:::com.here.schema.rib:road-traffic-pattern-attributes_v2:2.6.0
hrn:here:schema:::com.here.schema.rib:adas-attributes_v2:2.6.0
hrn:here:schema:::com.here.schema.rib:trasnport-attributes_v2:2.6.0
hrn:here:schema:::com.here.schema.rib:meta_v2:2.6.0
hrn:here:schema:::com.here.schema.rib:places_v2:2.6.0

Known Issues

Issue

The coverage for the ADAS layer is initially limited to North America and Western Europe.

Workaround

Additional HERE Map Content coverage and inclusion details can be obtained by OLP Customer Solutions or OLP Technical Customer Support.

Marketplace

Known Issues

Issue

After a Catalog is marked "Marketplace Ready", the Catalog may take up to 2 hours to show in the Provider Management Group's list of Catalogs.

Workaround

Contact technical support if the Provider Management Group cannot see the Marketplace Ready catalog after more than 2 hours has passed.


Issue

When a Marketplace Provider grants data access to a Marketplace Consumer, there could be a delay before the Consumer can see the data catalog in their licensed data area.

Workaround

Contact technical support if the Consumer Management Group cannot see the licensed data after more than 2 hours has passed.


Issue

If you are a Workspace user and have pipelines that use the Kafka Direct connector to connect to stream data, no messages-in and bytes-in metrics can be collected.

Workaround

You can instrument your pipelines with custom messages-in and bytes-in metrics. Contact technical support if you need assistance.


Issue

Marketplace users do not receive stream data usage metrics when reading data from Kafka direct.

Workaround

You must write data to a stream layer using the Ingest REST API in order to receive usage metrics.

You must use the Data Library configured to use the HTTP connector type in order to receive usage metrics and read data from a stream layer.

Web & Portal

Known Issues

Issue

Data visualization in the Portal is only available for versioned and volatile layers.

Workaround

Create your own visualization for your own schemas creating a GeoJSON renderer and making it part of that schema. Out of the box, however, only data can be visualized that is formatted according to the following schema formats:

  • GeoJSON
  • HERE Reality Index Topology
  • HERE Reality Index Building Footprints
  • HERE Reality Index Cartography
  • HERE Traffic Flow
  • SDII

Issue

Some PDF documentation has formatting errors.


Issue

The custom runtime configuration for a pipeline version has a limit of 64 characters for the property name, and a limit of 255 characters for the value.

Workaround

For the property value, there is no workaround. For the property name, you can define a shorter name in the configuration and map that to the actual, longer name within the pipeline code.


Issue

The Portal can't be used to delete pipeline templates.

Workaround

Use the CLI or API to delete pipeline templates.


Issue

In the Portal, new jobs and operations are not automatically added to the list of jobs and operations for a pipeline version while the list is open for viewing.

Workaround

Refresh the Jobs and Operations pages to see the latest job or operation in the list.


Issue

The Portal can't be used to force a batch pipeline version to run. It will run on its own when the input catalogs' version is updated.

Workaround

Use the CLI or API to force a batch pipeline version to run, or wait for the input catalogs' version to update. For more information, see the Troubleshooting section in the Pipelines Developer Guide.


Issue

The pipelines list page is sometimes slow to load.


Issue

Some older catalogs cannot be shared temporarily because the catalog owners don't have permissions assigned to them yet. This issue only applies to older catalogs. Contact us to report each occurrence as a bug.