Way Geometries

Consider... just consider a different schema for a separate rocksdb that holds just node geometry. Perhaps skip the json conversion, and find a new way to store just non-tagged nodes. Ways would then also save their node refs and a third script could be written that performs this lookup in the secondary location db. Possible to have two open rocksdbs at the same time?

The actual stitching together of geometries and versions may then be done in a streaming process at a feature level, once the features were enriched with the node histories; keep it out of memory and do it in parallel :)

No files, tests, or entry points are named. Start by reviewing the existing RocksDB schema and the current geometry, node-reference, and streaming flows; determine whether the proposed separate database and parallel feature-level stitching fit the project. Done would require an agreed design and implementation plan, not just a localized edit.

Written by the indexing model from the issue text.