brapi-java-client/src/main/java/org/brapi/client/v2/modules/phenotype/ImagesApi.java
public ApiResponse<BrAPIImageSingleResponse> imagesImageDbIdPut(String imageDbId, BrAPIImage body) throws ApiException {
        Call call = imagesImageDbIdPutCall(imageDbId, body);
        Type localVarReturnType = new TypeToken<BrAPIImageSingleResponse>(){}.getType();
        return apiClient.execute(call, localVarReturnType);
    }
/**
     * Update an image meta data
     * Update an image meta data object  Implementation Notes  - This call should be paired with &#x27;PUT /images/{imageDbId}/imagecontent&#x27; for full capability  - A server may choose to modify the image meta data object based on the actually image which has been uploaded.   - Image data may be stored in a database or file system. Servers should generate and provide the \&quot;imageURL\&quot; as an absolute path for retrieving the image, wherever it happens to live.   - &#x27;descriptiveOntologyTerm&#x27; can be thought of as Tags for the image. These could be simple descriptive words, or ontology references, or full ontology URI&#x27;s.   - The &#x27;/images&#x27; calls support a GeoJSON object structure for describing their location. The BrAPI spec for GeoJSON only supports two of the possible geometries: Points and Polygons.   - With most images, the Point geometry should be used, and it should indicate the longitude and latitude of the camera.   - For top down images (ie from drones, cranes, etc), the Point geometry may be used to indicate the longitude and latitude of the centroid of the image content, and the Polygon geometry may be used to indicate the border of the image content.
     * @param imageDbId The unique identifier for a image (required)
     * @param body  (optional)

     * @return ApiResponse&lt;ImageSingleResponse&gt;
     * @throws ApiException If fail to call the API, e.g. server error or cannot deserialize the response body
     */
Update an image meta data
Update an image meta data object  Implementation Notes  - This call should be paired with 'PUT /images/{imageDbId}/imagecontent' for full capability  - A server may choose to modify the image meta data object based on the actually image which has been uploaded.   - Image data may be stored in a database or file system. Servers should generate and provide the \"imageURL\" as an absolute path for retrieving the image, wherever it happens to live.   - 'descriptiveOntologyTerm' can be thought of as Tags for the image. These could be simple descriptive words, or ontology references, or full ontology URI's.   - The '/images' calls support a GeoJSON object structure for describing their location. The BrAPI spec for GeoJSON only supports two of the possible geometries: Points and Polygons.   - With most images, the Point geometry should be used, and it should indicate the longitude and latitude of the camera.   - For top down images , the Point geometry may be used to indicate the longitude and latitude of the centroid of the image content, and the Polygon geometry may be used to indicate the border of the image content.
@param imageDbId The unique identifier for a image (required)
@param body  (optional)

@return ApiResponse<ImageSingleResponse>
@throws ApiException If fail to call the API, e.g. server error or cannot deserialize the response body
Update an image meta data Update an image meta data object Implementation Notes - This call should be paired with ' PUT / images / { imageDbId } / imagecontent ' for full capability - A server may choose to modify the image meta data object based on the actually image which has been uploaded . - Image data may be stored in a database or file system . Servers should generate and provide the \ " imageURL \ " as an absolute path for retrieving the image wherever it happens to live . - ' descriptiveOntologyTerm ' can be thought of as Tags for the image . These could be simple descriptive words or ontology references or full ontology URI ' s . - The ' / images ' calls support a GeoJSON object structure for describing their location . The BrAPI spec for GeoJSON only supports two of the possible geometries : Points and Polygons . - With most images the Point geometry should be used and it should indicate the longitude and latitude of the camera . - For top down images the Point geometry may be used to indicate the longitude and latitude of the centroid of the image content and the Polygon geometry may be used to indicate the border of the image content . @param imageDbId The unique identifier for a image ( required ) @param body ( optional ) @return ApiResponse<ImageSingleResponse > @throws ApiException If fail to call the API e . g . server error or cannot deserialize the response body
public ApiResponse<BrAPIImageSingleResponse> imagesImageDbIdPut(String imageDbId, BrAPIImage body) throws ApiException {
        Call call = imagesImageDbIdPutCall(imageDbId, body);
        Type localVarReturnType = new TypeToken<BrAPIImageSingleResponse>(){}.getType();
        return apiClient.execute(call, localVarReturnType);
    }
public ApiResponse < BrAPIImageSingleResponse > imagesImageDbIdPut ( String imageDbId , BrAPIImage body ) throws ApiException { Call call = imagesImageDbIdPutCall ( imageDbId , body ) ; Type localVarReturnType = new TypeToken < BrAPIImageSingleResponse > ( ) { } . getType ( ) ; return apiClient . execute ( call , localVarReturnType ) ; }
Update an image meta data
 Update an image meta data object  Implementation Notes  - This call should be paired with &#x27;PUT /images/{imageDbId}/imagecontent&#x27; for full capability  - A server may choose to modify the image meta data object based on the actually image which has been uploaded.
Update an image meta data Update an image meta data object Implementation Notes - This call should be paired with &#x27 ; PUT / images / { imageDbId } / imagecontent&#x27 ; for full capability - A server may choose to modify the image meta data object based on the actually image which has been uploaded .