Add range_label with unit conversion to isochrone output at the service level
See original GitHub issuehello!
Right now, when isochrones are created, they don’t contain a categorical column to symbolize by unless used inside of the isolines_layer
helper which does this conversion and legend creation for the user behind the scenes.
Request
This ticket is to request that we add the categorical attribute range_label
and the unit conversion at the service level so even if this dataset is exported and used with a different mapping library or with different styling that we still provide the pieces needed to create a proper map.
Current blockers
The problem with the not having these fields is that if a user wants to create a map outside of a helper or use a different one, without the range_label
column they won’t be able to easily do that. The reason is because even if they do something like an equal interval classification (since there is the numeric data_range
column), the legend, no matter which type you use, won’t be correct, not to mention that they would have to know VL to construct the proper ramp and/or create a new string field that converts the ranges to categories and also the conversion.
Here are some visual examples of this blocker:
![Screen Shot 2019-11-07 at 11 34 13 AM](https://user-images.githubusercontent.com/1566273/68418537-a88ecc00-0155-11ea-832b-66f00c978ec2.png)
![Screen Shot 2019-11-07 at 11 33 53 AM](https://user-images.githubusercontent.com/1566273/68418558-afb5da00-0155-11ea-9089-97cbe28915ca.png)
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (5 by maintainers)
Let’s update the geojson file (to include the label column) and then close this.
Done, added in the drive directory, in both csv and geojson format 👍