I feel like the analysis step should return recommended options, which the encoder should consume.
If someone has a huge dataset with known precision and dimension (for example, because they just generated it), they should be able to skip the analysis phase (for performance reasons).
This could even be a feature, in that someone could use geobuf.encode(obj, {precision:4, dimensions:2}) to simplify their coordinates (also see #96 (comment)).
Additionally, if the offered precision can not be handled by the encoder, then one could fallback to things like JSON.stringify. An actual use-case for this can be found in maplibre/maplibre-gl-js#106 (comment).
I feel like the analysis step should return recommended options, which the encoder should consume.
If someone has a huge dataset with known precision and dimension (for example, because they just generated it), they should be able to skip the analysis phase (for performance reasons).
This could even be a feature, in that someone could use
geobuf.encode(obj, {precision:4, dimensions:2})to simplify their coordinates (also see #96 (comment)).Additionally, if the offered precision can not be handled by the encoder, then one could fallback to things like
JSON.stringify. An actual use-case for this can be found in maplibre/maplibre-gl-js#106 (comment).