pub fn extract_georeferencing_with_index(
content: &[u8],
entity_index: &Arc<EntityIndex>,
) -> Option<Georeferencing>Expand description
extract_georeferencing, reusing an index the caller already holds.
The extractor resolves its references by id, so this pass genuinely needs an index; what it does not need is a second one. A caller that has already scanned the file (the geometry pipeline holds one for its whole run) was paying a full extra scan to build a map it had in hand.
entity_index must have been built from this same content. Given that, the
result is identical to the wrapper’s.