You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Work on the concurrency ADR showed that we can get significant improvements in file size by using a Protobuffer based file format - I used an outdated version of geobuf to do this - we'll be forking that in #1141 as topobuf
Notes
We changed from JSON -> the v8 serialization format in #1099, which should be able to serve as a template for this PR
AC:
Update process-geojson and the backend server code to use topobuf instead of v8.serialize / v8.deserialize
Update serialize-topojson to be able to read v8 files and write topobuf files
Use the updated serialize-topojson script to make new .pbf files for every region in:
Staging
Production
scripts/load-dev-data
The text was updated successfully, but these errors were encountered:
File size is much much smaller with topobuf, but that is about the only thing it has going for us.
Probably worth looking into topobuf further for potentially sending TopoJSON to the browser due to the much smaller file size, but ultimately I think we should stick with the current serialization method.
Context
Work on the concurrency ADR showed that we can get significant improvements in file size by using a Protobuffer based file format - I used an outdated version of
geobuf
to do this - we'll be forking that in #1141 astopobuf
Notes
We changed from JSON -> the
v8
serialization format in #1099, which should be able to serve as a template for this PRAC:
process-geojson
and the backend server code to usetopobuf
instead ofv8.serialize
/v8.deserialize
serialize-topojson
to be able to readv8
files and writetopobuf
filesserialize-topojson
script to make new.pbf
files for every region in:scripts/load-dev-data
The text was updated successfully, but these errors were encountered: