Error in ramp with column name 'length'
See original GitHub issueAs reported internally by @andy-esch an unexpected error is thrown when styling some lines with a ramp using a column named length.
The error is:
> RangeError: invalid array length
This comes, for example, from a column in a SQL made with ST_Length(the_geom::geography) as length
and then using ramp($length, sunset)
in the viz. Using other column name works fine.
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Real-Time Connect Error exceeding column name length
Using Real-Time Connect 5.1.0 with a MySQL database, I am using the RTI_REAL_TIME_CONNECT.xml configuration file to create subscriptions.
Read more >Error: Redefinition of field | Looker - Google Cloud
You have accidentally named two fields with the same name in the same view. This could be: Two dimensions with the same name;...
Read more >Table mysql/innodb_index_stats has length mismatch in the ...
The overall system might have crashed and screwed up a core mysql DB table. Saw the same “…has length mismatch in the column...
Read more >Chapter 3 Heatmap Annotations | ComplexHeatmap ...
If the matrix has no column name, the name of the annotation is still used, but drawn in the middle of the annotation....
Read more >Guidelines for Spacing Between Freeway Ramps
Project Title: Guidelines for Ramp Terminal Spacing for Freeways ... in England, minimum deceleration and acceleration length for freeway conditions, ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hey @VictorVelarde, we have another issue seen first in CartoDB/cartoframes#533 that looks similar to what’s above.
Fixed in #1410. It will be ready in the next patch release