The flying line layer is a subcomponent of the basic flat map. It supports independent styles and data configurations. It can represent OD data between two points in a geographic location in the form of flying lines. It can be used to display the associated information between the two places, such as logistics and transactions. This topic describes the configuration items of the flying routes layer.

Click Flying Routes Layer under Components. The Settings tab of Flying Routes Layer appears.
Note If Components does not contain Flying Routes Layer, add the Flying Routes 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.
  • Flying Out Frequency: the frequency at which the flying line flies out. Unit: number of lines per frame.
  • Flight Rate: the speed of the flight. Valid values: 1 to 10.
  • Path Points: the number of constituent points of the flying route. Valid values: 100 to 400.
  • Flying Route Length: the length of the flying route. Valid values: 10 to 120.
  • Altitude Scale: the altitude scale of the flying route. Valid values: 0.5 to 5.
  • Flying Route Style
    • Color of Start Point: the color of the start point of the flying line. For more information, see color picker description.
    • End Color: the end color of the flying line.
    • Flare Color: the flare color of the flight.
    • Flying Route: the thickness of the flying route. Valid values: 0.01 to 10.
    • Flare Size: the size of the flying flare. Valid values: 0.01 to 20.
    • Flying Route Gradient: the color interpolation of the first and last flying routes. Valid values: 0.01 to 10.
    • Bubble Color: the color of flying route bubbles.
    • Bubble Radius: the radius of the air bubble. Valid values: 0 to 30.
    • Bubble Rate: the rate at which air bubbles fly. Valid values: 0.1 to 1.

The metadata of the filtering table.

Sample code in the preceding figure:

[
  {
    "from": "116.85059,31.69078",
    "to": "118.69629,36.20882"
  },
  {
    "from": "120.89355,37.09024",
    "to": "116.93848,31.61597"
  },
  {
    "from": "121.28906,29.34388",
    "to": "117.20215,31.12820"
  },
  {
    "from": "118.16895,31.57854",
    "to": "119.79492,32.47270"
  },
  {
    "from": "116.76270,33.35806",
    "to": "116.49902,38.95941"
  },
  {
    "from": "116.41113,30.93992",
    "to": "114.78516,26.58853"
  },
  {
    "from": "115.83984,32.13841",
    "to": "97.47070,37.54458"
  },
  {
    "from": "116.27930,32.36140",
    "to": "114.08203,36.27971"
  },
  {
    "from": "103.66699,25.79989",
    "to": "116.05957,31.54109"
  },
  {
    "from": "112.14844,24.40714",
    "to": "116.71875,33.21112"
  },
  {
    "from": "116.93848,31.65338",
    "to": "118.34473,26.62782"
  },
  {
    "from": "90.70313,42.26105",
    "to": "116.23535,32.32428"
  },
  {
    "from": "116.41113,30.82678",
    "to": "114.87305,36.94989"
  },
  {
    "from": "116.45508,30.78904",
    "to": "118.91602,28.57487"
  },
  {
    "from": "116.01562,40.07807",
    "to": "116.71875,31.69078"
  },
  {
    "from": "116.71875,31.72817",
    "to": "108.45703,40.24599"
  },
  {
    "from": "117.99316,40.84706",
    "to": "116.85059,31.69078"
  },
  {
    "from": "118.30078,36.56260",
    "to": "117.24609,40.97990"
  },
  {
    "from": "119.35547,26.86328",
    "to": "120.41016,32.28713"
  },
  {
    "from": "113.07129,31.42866",
    "to": "106.04004,31.31610"
  },
  {
    "from": "116.85059,31.31610",
    "to": "110.43457,32.76880"
  }
]
Table 1. Description
FieldDescription
fromThe start longitude and latitude of a flying route. Separate the longitude and latitude with a comma (,).
toThe end longitude and latitude of a flying route. Separate the longitude and latitude with a comma (,).
Table 2. Parameters
ParameterDescription
Controlled ModeIf 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 RequestAfter 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 SourceIn 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 FilterIf 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 ResultThe response to a data request. If the data source changes, you can click the Refresh icon 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

  1. In Canvas Editor, click the Add to Blueprint Editor icon on the right side of Flying Route Layer in the sub-widget list of Basic Flat Map.
  2. Click the Blueprint Editor icon icon in the upper-left corner of the page.
  3. In the blueprint editor, click Flying Routes Layer in the Added Nodes pane. You can configure parameters of the flying routes layer on the canvas.
    • Event

      When the data interface request is completed: The event is thrown after the 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
      ActionDescription
      Request Data InterfaceThis 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 passed to the request data interface is { id: '1'}, the final request interface is http://api.test?id=1.
      Import dataAfter 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.
      DisplayA widget is shown without the need to specify parameters.
      HideA widget is hidden without the need to specify parameters.