Several packages define ECS geo fields at root level. e.g. aws, azure.

ECS dictates that geo fields should be nested - https://www.elastic.co/guide/en/ecs/current/ecs-geo.html#_field_reuse_10. and newer package validations will fail with these fields defined at root level.

Any of these fields should be moved to the appropriate nested field, and eventually removed. This raises the age-old conversation of 'how do we deprecate and remove fields from packages' - to which we still don't have an answer. Perhaps now it's time to figure it out.

Packages with known root level geo fields:

• aws
• azure