![]() name:right:* - The localized name to be shown on the right side of the border.name:left:* - The localized name to be shown on the left side of the border.If no data is available basing on the language code, might be compiled from English/Latin transliteration of existing language representations. name:en - The name to call the feature in English.name:* - The name to call the feature in a localized language indicated by its language code. ![]() Localized Name Properties ( common-optional) As a result, the country of Greece would use something like: kind : country Language variants are identified by an ISO 639-1 two-letter language code and, optionally, ISO 15924 four-letter script code for example, en for English and zh-Hant for Traditional Chinese. HERE includes all language variants of the name:* values to enable full internationalization when available. This means that for that particular location, if you are using local languages to render your map, you should label the left side of the border with "Қазақстан" and the right side with "Россия". In this case, the country labels in the boundaries layer would include something like: kind : country The example below illustrates the usage of the left and right properties. This allows the labeled polygon's text to appear inside that polygon consistently. For example, for features in the boundaries layer, instead of name, the properties name:left and name:right are used for oriented labeling on the appropriate side of the boundary line. There are some layers in which the name property is considered optional. name:right - The name to be shown on the right side of the border.name:left - The name to be shown on the left side of the border.name:short - For example, CA for California.This definition supports several additional name-related properties ( optional): name - Generally the name the locals call the feature, in the local language script.Most features in a vector tile include a basic name property in the common list of properties, such as: Often used to "decorate" features already selected for display.optional - These are properties of a specific, less important kind, or generally present across kinds, but only in exceptional cases.Fundamental properties like population.Lightly transformed interoperable properties based on original data values.common-optional - These are meant to be part of a common set but may not be present because they aren't relevant or because we don't have the data (primarily feature properties, but could also be layers).Fundamental properties like name (including localized names) that are included in almost every feature.Special bits that make vector tile content interoperable, including kind, kind_detail, landuse_kind, min_zoom, and sort_rank.Core properties needed for display and labeling of features:.Establishes basic selection of features and their arrangement into specific named layers.common - These layers, properties, and kinds are generally available across all features in a response.However, for some regions of the world within the core layer parameter (for example, Japan), this property is present, and the property value indicates the data source provider. Assume that the value is unless stated otherwise. The property source is generally omitted in all tiles. For more information, see Required Copyright Notice. ![]() The HERE Vector Tile API uses data from HERE. Need help displaying vector tiles in a map? Here are several examples using the HERE Vector Tile API to style in your favorite graphics library including HERE Maps API for JavaScript, Mapbox, and Tangram. The HERE Vector Tile API uses the same structure as the original layer definition to make it easier to find the changes, and follows the same SEMANTIC VERSIONING statement as originally formulated by Tilezen. The sections below include all the information necessary to understand the layer structure. Some optional properties have been removed from the HERE Vector Tile API to better align the layer structure with the HERE Vector Tile API own data and processing logic. Specifically, all mandatory properties and all must-have values are still included. The HERE Vector Tile API has some changes and simplifications on top of that layer definition, but all these changes are backwards compatible and comply with the specification. The data in the HERE Vector Tile API is organized in layers according to the definitions specified by the Tilezen open-source project started by Mapzen.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |