High memory usage with large number of nodes

Problem/Motivation

If a GeoJson view contains a large number of nodes with WKT data, it is likely to have memory problems when rendering.

e.g. we had a view with ~ 1100 nodes, and encountered the following error:

Allowed memory size of 268435456 bytes exhausted (tried to allocate 36864 bytes) in /var/www/html/docroot/core/lib/Drupal/Core/Cache/CacheTagsChecksumTrait.php on line 131

Steps to reproduce

Proposed resolution

tbc - perhaps some kind of pre-rendering mechanism to avoid needing to calculate all the WKT coordinates?

Remaining tasks

User interface changes

API changes

Data model changes