Zones optionality brakes geo aggregation

[artem-vereshchaka]

Config example (for Madrid):
{ "boundary": [ -3.978424072265625, 40.20509926855807, -3.40576171875, 40.66188943992171 ], "center": [-3.68865966796875,40.42081487986971], "zoom": 12.75, "privacyMinimum": 3, "lost": 5, "summary": { "Unique Vehicles": true, "Active Vehicles": true, "Total Trips": true, "Total Trip Distance": true, "Distance Per Vehicle": true, "Vehicle Utilization": true, "Trips Per Active Vehicle": true, "Avg Trip Distance": true, "Avg Trip Duration": true }, "providers": { *** } }

As we can see from the documentation -- 'zones' object is optional in config. In the example config above it is absent.
Here are 3 issues:

1. [minor] Runtime Error on the line with initialization of zones object with empty featureCollection (turf.FeatureCollection() which doesn't exist, should be turf.featureCollection())
2. [minor] For some reason radio button with 'Zones' is there, but should not be (as there are no zones presented)
3. [main] None of aggregations works, except simple table in the beginning, like a number of vehicles, average trips, etc. Each map is empty with any of radio buttons selected.