v4.10

What's Changed

• csv page #250 by @sboivinsystra
• cropped trip id name show on hover in side panel #414 by @sboivinsystra
• Step function choice #343 by @sboivinsystra
• PT and road field choice as a config json #413 by @sboivinsystra
• read locally imported png #415 by @sboivinsystra
• upload Style.json in front end #418 by @sboivinsystra
• "raster layers" now build with preset #420 by @sboivinsystra
• Hex color field usable in result layer #424 by @sboivinsystra
• .lock file will lock scenario #426 by @sboivinsystra
• fix color sclale and width #419 #425 by @sboivinsystra
• OD_names is now a default attribute for ODs #422 by @sboivinsystra
• bug fixes and optimization

Description

1) CSV page

New csv page. all csv in inputs and outputs are displayed here.
Sorting values available.

2) Raster layer

The preset saved in the Result page are now available to display on the main map.
You can then show the population Density while editing (for example)

3) Result Maps

You can now color layers based on a category (string field)
Also, if a properties contain Hex colors (#2a57a1 for example), it will be used.
Color scale were fixed (bug in log and sqrt). some were added. and the width is now also using the selected scale.

4) Field Choice

in the root dir of a project. you can add "attributesChoices.json" This gives choices for PT attributes and/or road.
ex:

{
    "pt":{
       
    },
    "road":{
       "oneway":[
          "0",
          "1"
       ],
       "cycleway":[
          "yes",
          "no",
          "shared"
       ],
       "cycleway_reverse":[
          "yes",
          "no",
          "shared"
       ],
       "highway":[
          "motorway",
         "residential"
       ]
    }
 }

4) Step function Choice (backend)

In the step function definition, you can now add a Choice.

"Choice": {
      "Type": "Choice",
      "Choices": [
        {
          "Variable": "$.choice",
          "StringEquals": "comparision",
          "Next": "STEP 2"
        }
      ],
      "Default": "STEP 1"
    },

You can have more than 2 choices. The quendi front-end will automaticaly fetch all the choices and gives a choice un the Run page Stepper.

You can customize the parameters for each Choices with the "model" key. it is set to "default" if none is provided.

[
   {
      "info": "Default model",
      "model": "default"
   },
   {
      "info": "comparision model",
      "model": "comparision"
   },
   {
      "category": "general",
      "model": "default",
      "params": [
         {
            "text": "param 1",
            "value": 500,
            "type": "Number",
            "units": "unit",
            "hint": "hint 1",
            "rules": [
               "required"
            ],
            "name": "param 1"
         }
      ]
   },
   {
      "category": "general",
      "model": "comparision",
      "params": [
         {
            "text": "param comparision",
            "value": 500,
            "type": "Number",
            "units": "unit",
            "hint": "hint for this param",
            "rules": [
               "required"
            ],
            "name": "param comparision"
         }
      ]
   }
]

Finally, for a parameters needing a list of scenario (comparing scenarios for example). The special key "items": "$scenarios", can be used to fetch the list of scenario in the front-end and display them as chocies.

{
      "category": "general",
      "model": "comparision",
      "params": [
         {
            "text": "scenarios",
            "value": [],
            "type": "String",
            "items": "$scenarios",
            "hint": "Scenarios à comparer",
            "rules": [
               "required"
            ],
            "name": "scenarios"
         }
      ]
   }

For example. here we have Default or Result

5) .lock to lock a scenario

simply add a .lock empty file at the root dir of a scenario to lock it in the front end.

Full Changelog: v4.9.1...v4.10