Asynchronous API that imports a list of reference images to specified product sets based on a list of image information. The google.longrunning.Operation API can be used to keep track of the progress and results of the request. Operation.metadata contains BatchOperationMetadata. (progress) Operation.response contains ImportProductSetsResponse. (results) The input source of this method is a csv file on Google Cloud Storage. For the format of the csv file please see ImportProductSetsGcsSource.csv_file_uri.
Scopes
You will need authorization for at least one of the following scopes to make a valid call:
- https://www.googleapis.com/auth/cloud-platform
 - https://www.googleapis.com/auth/cloud-vision
 
If unset, the scope for this method defaults to https://www.googleapis.com/auth/cloud-platform.
You can set the scope for this method like this: vision1 --scope <scope> projects locations-product-sets-import ...
Required Scalar Argument
- <parent> (string)
- Required. The project in which the ProductSets should be imported. Format is 
projects/PROJECT_ID/locations/LOC_ID. 
 - Required. The project in which the ProductSets should be imported. Format is 
 
Required Request Value
The request value is a data-structure with various fields. Each field may be a simple scalar or another data-structure. In the latter case it is advised to set the field-cursor to the data-structure's field to specify values more concisely.
For example, a structure like this:
ImportProductSetsRequest:
  input-config:
    gcs-source:
      csv-file-uri: string
can be set completely with the following arguments which are assumed to be executed in the given order. Note how the cursor position is adjusted to the respective structures, allowing simple field names to be used most of the time.
-r .input-config.gcs-source csv-file-uri=eos- The Google Cloud Storage URI of the input csv file. The URI must start with 
gs://. The format of the input csv file should be one image per line. In each line, there are 8 columns. 1. image-uri 2. image-id 3. product-set-id 4. product-id 5. product-category 6. product-display-name 7. labels 8. bounding-poly Theimage-uri,product-set-id,product-id, andproduct-categorycolumns are required. All other columns are optional. If theProductSetorProductspecified by theproduct-set-idandproduct-idvalues does not exist, then the system will create a newProductSetorProductfor the image. In this case, theproduct-display-namecolumn refers to display_name, theproduct-categorycolumn refers to product_category, and thelabelscolumn refers to product_labels. Theimage-idcolumn is optional but must be unique if provided. If it is empty, the system will automatically assign a unique id to the image. Theproduct-display-namecolumn is optional. If it is empty, the system sets the display_name field for the product to a space (" "). You can update thedisplay_namelater by using the API. If aProductwith the specifiedproduct-idalready exists, then the system ignores theproduct-display-name,product-category, andlabelscolumns. Thelabelscolumn (optional) is a line containing a list of comma-separated key-value pairs, in the following format: "key_1=value_1,key_2=value_2,...,key_n=value_n" Thebounding-polycolumn (optional) identifies one region of interest from the image in the same manner asCreateReferenceImage. If you do not specify thebounding-polycolumn, then the system will try to detect regions of interest automatically. At most onebounding-polycolumn is allowed per line. If the image contains multiple regions of interest, add a line to the CSV file that includes the same product information, and thebounding-polyvalues for each region of interest. Thebounding-polycolumn must contain an even number of comma-separated numbers, in the format "p1_x,p1_y,p2_x,p2_y,...,pn_x,pn_y". Use non-negative integers for absolute bounding polygons, and float values in [0, 1] for normalized bounding polygons. The system will resize the image if the image resolution is too large to process (larger than 20MP). 
- The Google Cloud Storage URI of the input csv file. The URI must start with 
 
About Cursors
The cursor position is key to comfortably set complex nested structures. The following rules apply:
- The cursor position is always set relative to the current one, unless the field name starts with the 
.character. Fields can be nested such as in-r f.s.o. - The cursor position is set relative to the top-level structure if it starts with 
., e.g.-r .s.s - You can also set nested fields without setting the cursor explicitly. For example, to set a value relative to the current cursor position, you would specify 
-r struct.sub_struct=bar. - You can move the cursor one level up by using 
... Each additional.moves it up one additional level. E.g....would go three levels up. 
Optional Output Flags
The method's return value a JSON encoded structure, which will be written to standard output by default.
- -o out
- out specifies the destination to which to write the server's result to.
  It will be a JSON-encoded structure.
  The destination may be 
-to indicate standard output, or a filepath that is to contain the received bytes. If unset, it defaults to standard output. 
 - out specifies the destination to which to write the server's result to.
  It will be a JSON-encoded structure.
  The destination may be 
 
Optional General Properties
The following properties can configure any call, and are not specific to this method.
- 
-p $-xgafv=string
- V1 error format.
 
 - 
-p access-token=string
- OAuth access token.
 
 - 
-p alt=string
- Data format for response.
 
 - 
-p callback=string
- JSONP
 
 - 
-p fields=string
- Selector specifying which fields to include in a partial response.
 
 - 
-p key=string
- API key. Your API key identifies your project and provides you with API access, quota, and reports. Required unless you provide an OAuth 2.0 token.
 
 - 
-p oauth-token=string
- OAuth 2.0 token for the current user.
 
 - 
-p pretty-print=boolean
- Returns response with indentations and line breaks.
 
 - 
-p quota-user=string
- Available to use for quota purposes for server-side applications. Can be any arbitrary string assigned to a user, but should not exceed 40 characters.
 
 - 
-p upload-type=string
- Legacy upload protocol for media (e.g. "media", "multipart").
 
 - 
-p upload-protocol=string
- Upload protocol for media (e.g. "raw", "multipart").