Status Update

What about a header (or a footer?) with basic file statistics?

This would be the difference between "Procesed xxxx K features and (84%). It would not be that hard to implement, would just need to define what our header would look like, a parsable JSON object that could have arbitrary arguments and either exist or not, would be ideal.

Output files should also have a header or footer describing themselves. Since the files are on the order of 40 - 50 GB for countries, it'd be great to have the ability to not have to parse the file to learn about it.

Furthermore, if it was just a json object with a `"geometry":null` attribute, tippecanoe would even print it out for you as a geometry error when it started building tiles... free debugging!

No source files or tests are named. Start by locating the code that writes the country-sized output files and determine how a JSON header or footer could describe input and output statistics; done means the metadata format and placement are defined and output files expose their statistics without being fully parsed.

Written by the indexing model from the issue text.