Posted on behalf of a customer.
Currently, APIs require the geometry to be explicitly provided as a GeoJSON in the request payload. This forces users to maintain their own geometry storage and ingestion systems, even if those same geometries are already managed within the Planet Feature API. This redundancy increases the risk of geometry mismatch and adds unnecessary overhead to the request size.
We propose allowing the input.bounds.geometry or a new input.features field to accept a Feature or Collection Reference URI. This would allow the API to fetch the geometry directly from a managed collection.
