The point heat layer is a subcomponent of the basic flat map. It supports independent styles and data configurations, including the size, color, blur degree, longitude, and latitude of thermal points. It can use thermal points to represent point data information on geographic locations. This topic describes the meaning of each configuration items of the point heat layer.
Click Point Thermal Layer below Component Management. In the configuration panel, configure the style and data of the Point Thermal Layer.
Note If Point Thermal Layer is not displayed in the Component Management section, you have not added the Point Thermal Layer component. For more information, see Map container (v1.x version).
Parameter
- Search for Configurations: In the right-side panel of Canvas Editor, click the Settings tab, and click Search for Configurations in the upper-right corner. Enter the required configuration item in the search box, and click the search icon to quickly locate the configuration item. Fuzzy match is supported. For more information, see Search for asset configurations.
- Layer Transparency: the transparency of the point heat layer.
- Start Transparency: the transparency of the start position (center) of the heat layer.
- Radius: the radius of the point heat layer.
- Blur: the fuzziness of the point heat layer.
- Ribbon: The color of the thermal point from the outer ring to the inner ring. Color 1 is the color of the outermost ring, and Color 5 is the color of the innermost ring. Please refer to the color picker instructions for modification.
The metadata of the filtering table.
You can download the sample JSON code in the preceding figure.
Field | Description |
---|---|
lat | Latitude of the point heat layer |
lng | Longitude of the point heat layer |
value | Optional. The weight of the point heat layer. |
Parameter | Description |
---|---|
Controlled Mode | If you turn on the switch, data is not requested when a widget is initialized. Data requests are triggered only based on callback IDs or the method configured in Blueprint Editor. If you turn off the switch, data requests are automatically triggered. By default, the switch is turned off. |
Auto Data Request | After you select the Auto Data Request check box, you can enable dynamic polling, and manually specify the polling interval. If you do not select this check box, data is not automatically requested. You must manually refresh the page to request data or use Blueprint Editor or callback ID events to trigger data requests. |
Data Source | In the right-side panel of Canvas Editor, click the Data tab. Click Set next to Static Data. In the Configure Datasource panel, select a data source from the Data Source Type drop-down list. Enter code for data query in the code editor, click Preview Data Response to preview the response of the data source, and then view the response. For more information, see Configure asset data. |
Data Filter | If you select the Data Filter check box, you can convert the data structure, filter data, and perform simple calculations. If you click the plus sign (+) next to Add Filter, you can configure the script for the data filter in the editor that appears. For more information, see Use the data filter. |
Data Response Result | The response to a data request. If the data source changes, you can click the icon next to Data Response Result to view the data response in real time. |
Interaction
This widget does not support interaction events.
Configure interactions in Blueprint Editor
- In Canvas Editor, click the icon next to Point Thermal Layer in the Basic Flat Map widget.
- Click the icon in the upper-left corner of the page.
- In Blueprint Editor, click the Point Heating Layer component in the Import Nodes pane. You can view the parameters of the Point Heating Layer component on the canvas.
- Event
When the Hotspot Data Interface Request is Completed: The event is thrown after the Hotspot Data Interface request is returned and processed by the filter. The event also throws the processed JSON data. For more information, see Example data.
- Policy Action
Action Description Request Hotspot Data Interface This action is performed to request the server data again. The data sent by an upstream data processing node or layer node is used as a parameter. For example, if the API data source is http://api.test
and the data transferred to the request thermal point data interface is{ id: '1'}
, the final request interface ishttp://api.test?id=1
.Import thermal point data interface After data of a widget is processed in accordance with its drawing format, the widget is imported for redrawing. You do not need to request server data again. For specific data, see Data. Display A widget is shown without the need to specify parameters. Hide A widget is hidden without the need to specify parameters.
- Event