Many of these features are too large

Pretty much every officialized set of features has a mix of some that are okay in size and some that are just way too large, breaking the sense of scale with BAR units. Deleting the offending objects3d items without adjusting which ones the feature config is searching for produces infolog errors, so this is a rather manual process of inspecting which ones are too large in Springboard, removing the objects, and editing the config until no errors are produced on map load.

Start by reviewing the officialized feature sets and their feature configurations, then inspect the oversized objects3d items in Springboard. Remove offending objects and update the corresponding configuration entries, checking map loads for infolog errors. Done means the feature sets have a consistent BAR scale and load without those errors.

Written by the indexing model from the issue text.