For me a 1.5MB DWG gets expanded to about 21MB of JSON, which is about a 1300% increase in storage requirements!

Luckily I can trash the JSON when I'm done but the storage requirements is quite the increase.

A wild guess would be the JSON keys being repeated "long_strings" does the most damage.

Is the filesize a concern for this project? I'm guessing probably not
JSON file sizes
This is a GitHub Issue
repo:libredwg
owner:LibreDWG
Title : JSON file sizes
Issue date:

--- start body ---
For me a 1.5MB DWG gets expanded to about 21MB of JSON, which is about a 1300% increase in storage requirements!

Luckily I can trash the JSON when I'm done but the storage requirements is quite the increase.

A wild guess would be the JSON keys being repeated "long_strings" does the most damage.

Is the filesize a concern for this project? I'm guessing probably not
--- end body ---
