Wacky default Geographic scope
This must be an Engine issue, but some % of the default models appear to be defaulting to national-level geographies rather than World, even though world would be more logical. Possible solution is enforcing geo rules at outset and having those developed, or possibly always starting with World and then having relative scales to that (anchored to that)
Log in to comment and vote
Comments2
Cassie Borish
Oct 30, 2025
@seth.sheldon Can you confirm that this is a science team issue and not a dev team issue?
seth.sheldon
Oct 30, 2025
Yep, confirmed! That’s on the engine model generation side