Be able to use a column for ranges in AOIs

SB ticket

Currently, isodistance functions can only accept an array of fixed values as range. The same range is used for every row:

SELECT (
  cdb_isodistance(
    the_geom, 
    'walk', 
    ARRAY[300, 600, 900]::integer[])
  ).the_geom 
FROM untitled_table_1

That query returns three different isolines at 300, 600 and 900 seconds for each row.

It would be nice if we could use a column as range parameter, so each point could have a different range value and therefore produce a unique isoline:

SELECT (
  cdb_isodistance(
    the_geom, 
    'walk', 
    string_to_array(range,',')::integer[])
  ).the_geom 
FROM untitled_table_1

If we had this feature, the query above would take the string in range (which should be something like 300,600,900), create an integer array from it and use the values to request isolines with a varying range.

It currently fails with:

Error in SQL query: cdb_dataservices_client._cdb_isodistance(6): [cartodb_user_a6f0d0fe-xxxx-xxxx-xxxx-22b0010fe409_db] REMOTE ERROR: spiexceptions.ExternalRoutineException: spiexceptions.ExternalRoutineException: Exception: Error trying to get mapzen isolines.

[urbanphes]

Thanks for the feedback, mates!

I’ve been working on a second approach.

• I’ve changed the texts that @arianaescobar suggested.
• Now the decision is taken when the user is on radius selection:
  • “Manual” with the slider we have now
  • “Column” selecting a column in the table

Here is the InVision project: https://invis.io/SPCR7ERJY

[urbanphes]

Close and promote ¿?