HERE Map Attributes API, get Administrative Shape polygons using Java

Customers using the HERE Map Attributes API may observe one or more of the following:

A country, state, province, county, or other administrative boundary is returned as multiple geometry fragments.
Spatial operations fail because the administrative shape is incomplete.
Downloaded geometry does not represent the full administrative region when only a single tile is processed.
Large administrative areas appear fragmented across several map tiles.
Additional processing is required to merge geometry before spatial analysis or visualization.

Answer
======

This behavior is expected when retrieving administrative boundaries from the HERE Map Attributes API. Administrative unit geometries can span multiple Map Attributes tiles, and the complete shape must be collected from all relevant tiles and merged into a single geometry before use in spatial operations.

To obtain a complete administrative boundary, download all geometry components associated with the target administrative entity across the relevant Map Attributes tiles and combine them into a unified topology or polygon using a GIS or geometry-processing library.

Product
=======

HERE Map Attributes REST API
Administrative Boundary / Administrative Attribute layers

Root Cause
==========

The HERE Map Attributes platform is tile-based. Large administrative regions such as countries, states, provinces, and counties may extend across many map tiles. As a result, the geometry for a single administrative entity is stored and delivered in multiple parts rather than as one consolidated polygon.

Impact
======

If only a subset of tiles is processed:

The returned geometry may be incomplete.
Area calculations can produce inaccurate results.
Point-in-polygon and containment checks may fail.
Rendering may show gaps or missing boundary segments.
Downstream geospatial workflows may generate incorrect results.

Recommended Actions
===================

1. Identify all tiles containing geometry for the target administrative entity.
2. Download the administrative geometry from each relevant tile.
3. Collect all geometry fragments belonging to the same administrative unit.
4. Merge or union the geometry parts using an appropriate geometry-processing library.
5. Validate the resulting geometry before performing spatial analysis or visualization.

For customers requiring a practical implementation example, a Java sample demonstrates how to efficiently download administrative topology fragments and combine them into a single geometry representation. The sample project is available at:

Java Sample Repository

Expected vs. Unexpected Behavior
================================

Expected Behavior

Administrative geometries may be distributed across multiple Map Attributes tiles.
Multiple geometry records may represent a single administrative unit.
Geometry merging is required for complete boundary reconstruction.

Unexpected Behavior

Missing geometry fragments after successfully downloading all relevant tiles.
Invalid topology after correct geometry collection and processing.
Administrative entities that cannot be reconstructed despite having complete source data.

Current Relevance
=================

This guidance remains applicable to tile-based administrative geometry retrieval workflows where boundary data is distributed across multiple map tiles. Customers should verify the currently supported HERE platform products, layers, and documentation for implementation details.

Keywords / Tags
===============

HERE Map Attributes API, administrative boundary, admin area, country polygon, county shape, state boundary, geometry merge, topology union, map tiles, spatial operations, GIS processing, polygon reconstruction, administrative layer, boundary geometry, REST API