Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
W wiki
  • Project overview
    • Project overview
    • Details
    • Activity
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
Collapse sidebar
  • pub
  • wiki
  • Wiki
  • d2s_spec_keyvalue_mapping

d2s_spec_keyvalue_mapping · Changes

Page history
Update d2s_spec_keyvalue_mapping authored Sep 28, 2018 by Michael Bauroth's avatar Michael Bauroth
Hide whitespace changes
Inline Side-by-side
Showing with 10 additions and 2 deletions
+10 -2
  • d2s_spec_keyvalue_mapping.md d2s_spec_keyvalue_mapping.md +10 -2
  • No files found.
d2s_spec_keyvalue_mapping.md
View page @ 84e9ec0d
...@@ -3,11 +3,19 @@ ...@@ -3,11 +3,19 @@
## Introduction ## Introduction
Devices send key-value data in the format described [here](https://git.falcom.de/pub/wiki/wikis/d2s_spec_sfal_dataframe). Devices send key-value data in the format described [here](https://git.falcom.de/pub/wiki/wikis/d2s_spec_sfal_dataframe).
comes in as typeless key-value pairs. These data, even if following some special format definitions, come in in a typeless form.
Visualization of these data in the frontend To visualize these data in the frontend, one of the key features of the mapping engine is to define the underlying format of the incoming data, e.g. key1="1.23" would suggest the type DOUBLE as the mapping type inside a mapping definition. Attaching a human readable name is another benefit from the mapping. So properly named in the mapping definition a key as e.g. _temp could be mapped to a more readable form as temperature.
The most interesting feature comes in with the description of an optional formula, which can convert any incoming values and formats on-the-fly to more meaningful values. The underlying framework used for these calculations is [mXparser](http://mathparser.org/). D2Sphere uses a more or less the complete subset out of these features, even that some format restrictions come into place.
## Specification ## Specification
- The outgoing key can be named differently from the incoming one, e.g. _accl_x vs. formula $[N(0)]_accl$ * 10;
## Restrictions
Even if the incoming value (or parts of it in case of a vecotr) can be used more than once inside the same formula, there is currently no support for different incoming values inside one formula!
## Examples ## Examples
``` ```
......
Clone repository
  • AVL Filesystem
  • BOLERO40_GNSS_improvement
  • BOLERO40_improvement_of_the_GNSS_performance
  • NFC_commands,_event,_dynamic_variable
  • Promotion_Kit_Settings
  • Workbench Mac Installation Readme
  • avl_aes_key_handling
  • avl_ble
  • avl_blueid
  • avl_config_commented_1
  • avl_ecodrive
  • avl_feature_list
  • avl_frp_main
  • avl_fw_update
  • avl_premium_feature_cpc
View All Pages