It would be preferable for this to run with a streaming JSON parser, though this would be quite a lot more difficult, especially because actual streaming JSON parsers are very rare. But still, it would allow running this with the important tracing information, but avoiding the overhead of generating an ast on top of the GeoJSON output.
It would be preferable for this to run with a streaming JSON parser, though this would be quite a lot more difficult, especially because actual streaming JSON parsers are very rare. But still, it would allow running this with the important tracing information, but avoiding the overhead of generating an ast on top of the GeoJSON output.