You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/dyn/documentai_v1.projects.locations.processors.html
+2Lines changed: 2 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -697,6 +697,7 @@ <h3>Method Details</h3>
697
697
"nanos": 42, # Number of nano (10^-9) units of the amount. The value must be between -999,999,999 and +999,999,999 inclusive. If `units` is positive, `nanos` must be positive or zero. If `units` is zero, `nanos` can be positive, zero, or negative. If `units` is negative, `nanos` must be negative or zero. For example $-1.75 is represented as `units`=-1 and `nanos`=-750,000,000.
698
698
"units": "A String", # The whole units of the amount. For example if `currencyCode` is `"USD"`, then 1 unit is one US dollar.
699
699
},
700
+
"signatureValue": True or False,
700
701
"text": "A String", # Optional. An optional field to store a normalized string. For some entity types, one of respective `structured_value` fields may also be populated. Also not all the types of `structured_value` will be normalized. For example, some processors may not generate `float` or `integer` normalized text by default. Below are sample formats mapped to structured values. - Money/Currency type (`money_value`) is in the ISO 4217 text format. - Date type (`date_value`) is in the ISO 8601 text format. - Datetime type (`datetime_value`) is in the ISO 8601 text format.
701
702
},
702
703
"pageAnchor": { # Referencing the visual context of the entity in the Document.pages. Page anchors can be cross-page, consist of multiple bounding polygons and optionally reference specific layout element types. # Optional. Represents the provenance of this entity wrt. the location on the page where it was found.
@@ -1738,6 +1739,7 @@ <h3>Method Details</h3>
1738
1739
"nanos": 42, # Number of nano (10^-9) units of the amount. The value must be between -999,999,999 and +999,999,999 inclusive. If `units` is positive, `nanos` must be positive or zero. If `units` is zero, `nanos` can be positive, zero, or negative. If `units` is negative, `nanos` must be negative or zero. For example $-1.75 is represented as `units`=-1 and `nanos`=-750,000,000.
1739
1740
"units": "A String", # The whole units of the amount. For example if `currencyCode` is `"USD"`, then 1 unit is one US dollar.
1740
1741
},
1742
+
"signatureValue": True or False,
1741
1743
"text": "A String", # Optional. An optional field to store a normalized string. For some entity types, one of respective `structured_value` fields may also be populated. Also not all the types of `structured_value` will be normalized. For example, some processors may not generate `float` or `integer` normalized text by default. Below are sample formats mapped to structured values. - Money/Currency type (`money_value`) is in the ISO 4217 text format. - Date type (`date_value`) is in the ISO 8601 text format. - Datetime type (`datetime_value`) is in the ISO 8601 text format.
1742
1744
},
1743
1745
"pageAnchor": { # Referencing the visual context of the entity in the Document.pages. Page anchors can be cross-page, consist of multiple bounding polygons and optionally reference specific layout element types. # Optional. Represents the provenance of this entity wrt. the location on the page where it was found.
Copy file name to clipboardExpand all lines: docs/dyn/documentai_v1.projects.locations.processors.humanReviewConfig.html
+1Lines changed: 1 addition & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -288,6 +288,7 @@ <h3>Method Details</h3>
288
288
"nanos": 42, # Number of nano (10^-9) units of the amount. The value must be between -999,999,999 and +999,999,999 inclusive. If `units` is positive, `nanos` must be positive or zero. If `units` is zero, `nanos` can be positive, zero, or negative. If `units` is negative, `nanos` must be negative or zero. For example $-1.75 is represented as `units`=-1 and `nanos`=-750,000,000.
289
289
"units": "A String", # The whole units of the amount. For example if `currencyCode` is `"USD"`, then 1 unit is one US dollar.
290
290
},
291
+
"signatureValue": True or False,
291
292
"text": "A String", # Optional. An optional field to store a normalized string. For some entity types, one of respective `structured_value` fields may also be populated. Also not all the types of `structured_value` will be normalized. For example, some processors may not generate `float` or `integer` normalized text by default. Below are sample formats mapped to structured values. - Money/Currency type (`money_value`) is in the ISO 4217 text format. - Date type (`date_value`) is in the ISO 8601 text format. - Datetime type (`datetime_value`) is in the ISO 8601 text format.
292
293
},
293
294
"pageAnchor": { # Referencing the visual context of the entity in the Document.pages. Page anchors can be cross-page, consist of multiple bounding polygons and optionally reference specific layout element types. # Optional. Represents the provenance of this entity wrt. the location on the page where it was found.
Copy file name to clipboardExpand all lines: docs/dyn/documentai_v1.projects.locations.processors.processorVersions.html
+2Lines changed: 2 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -791,6 +791,7 @@ <h3>Method Details</h3>
791
791
"nanos": 42, # Number of nano (10^-9) units of the amount. The value must be between -999,999,999 and +999,999,999 inclusive. If `units` is positive, `nanos` must be positive or zero. If `units` is zero, `nanos` can be positive, zero, or negative. If `units` is negative, `nanos` must be negative or zero. For example $-1.75 is represented as `units`=-1 and `nanos`=-750,000,000.
792
792
"units": "A String", # The whole units of the amount. For example if `currencyCode` is `"USD"`, then 1 unit is one US dollar.
793
793
},
794
+
"signatureValue": True or False,
794
795
"text": "A String", # Optional. An optional field to store a normalized string. For some entity types, one of respective `structured_value` fields may also be populated. Also not all the types of `structured_value` will be normalized. For example, some processors may not generate `float` or `integer` normalized text by default. Below are sample formats mapped to structured values. - Money/Currency type (`money_value`) is in the ISO 4217 text format. - Date type (`date_value`) is in the ISO 8601 text format. - Datetime type (`datetime_value`) is in the ISO 8601 text format.
795
796
},
796
797
"pageAnchor": { # Referencing the visual context of the entity in the Document.pages. Page anchors can be cross-page, consist of multiple bounding polygons and optionally reference specific layout element types. # Optional. Represents the provenance of this entity wrt. the location on the page where it was found.
@@ -1832,6 +1833,7 @@ <h3>Method Details</h3>
1832
1833
"nanos": 42, # Number of nano (10^-9) units of the amount. The value must be between -999,999,999 and +999,999,999 inclusive. If `units` is positive, `nanos` must be positive or zero. If `units` is zero, `nanos` can be positive, zero, or negative. If `units` is negative, `nanos` must be negative or zero. For example $-1.75 is represented as `units`=-1 and `nanos`=-750,000,000.
1833
1834
"units": "A String", # The whole units of the amount. For example if `currencyCode` is `"USD"`, then 1 unit is one US dollar.
1834
1835
},
1836
+
"signatureValue": True or False,
1835
1837
"text": "A String", # Optional. An optional field to store a normalized string. For some entity types, one of respective `structured_value` fields may also be populated. Also not all the types of `structured_value` will be normalized. For example, some processors may not generate `float` or `integer` normalized text by default. Below are sample formats mapped to structured values. - Money/Currency type (`money_value`) is in the ISO 4217 text format. - Date type (`date_value`) is in the ISO 8601 text format. - Datetime type (`datetime_value`) is in the ISO 8601 text format.
1836
1838
},
1837
1839
"pageAnchor": { # Referencing the visual context of the entity in the Document.pages. Page anchors can be cross-page, consist of multiple bounding polygons and optionally reference specific layout element types. # Optional. Represents the provenance of this entity wrt. the location on the page where it was found.
Copy file name to clipboardExpand all lines: docs/dyn/documentai_v1beta3.projects.locations.processors.dataset.html
+4Lines changed: 4 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -367,6 +367,9 @@ <h3>Method Details</h3>
367
367
"pageStart": 42, # Page where block starts in the document.
368
368
},
369
369
"tableBlock": { # Represents a table type block. # Block consisting of table content/structure.
370
+
"annotations": { # Represents the annotation of a block or a chunk. # Annotation of the table block.
371
+
"description": "A String", # The description of the content with this annotation.
372
+
},
370
373
"bodyRows": [ # Body rows containing main table content.
371
374
{ # Represents a row in a table.
372
375
"cells": [ # A table row is a list of table cells.
@@ -456,6 +459,7 @@ <h3>Method Details</h3>
456
459
"nanos": 42, # Number of nano (10^-9) units of the amount. The value must be between -999,999,999 and +999,999,999 inclusive. If `units` is positive, `nanos` must be positive or zero. If `units` is zero, `nanos` can be positive, zero, or negative. If `units` is negative, `nanos` must be negative or zero. For example $-1.75 is represented as `units`=-1 and `nanos`=-750,000,000.
457
460
"units": "A String", # The whole units of the amount. For example if `currencyCode` is `"USD"`, then 1 unit is one US dollar.
458
461
},
462
+
"signatureValue": True or False,
459
463
"text": "A String", # Optional. An optional field to store a normalized string. For some entity types, one of respective `structured_value` fields may also be populated. Also not all the types of `structured_value` will be normalized. For example, some processors may not generate `float` or `integer` normalized text by default. Below are sample formats mapped to structured values. - Money/Currency type (`money_value`) is in the ISO 4217 text format. - Date type (`date_value`) is in the ISO 8601 text format. - Datetime type (`datetime_value`) is in the ISO 8601 text format.
460
464
},
461
465
"pageAnchor": { # Referencing the visual context of the entity in the Document.pages. Page anchors can be cross-page, consist of multiple bounding polygons and optionally reference specific layout element types. # Optional. Represents the provenance of this entity wrt. the location on the page where it was found.
Copy file name to clipboardExpand all lines: docs/dyn/documentai_v1beta3.projects.locations.processors.html
+18Lines changed: 18 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -186,7 +186,10 @@ <h3>Method Details</h3>
186
186
"includeAncestorHeadings": True or False, # Optional. Whether or not to include ancestor headings when splitting.
187
187
"semanticChunkingGroupSize": True or False, # Optional. The number of tokens to group together when evaluating semantic similarity. THIS FIELD IS NOT YET USED.
188
188
},
189
+
"enableImageAnnotation": True or False, # Optional. Whether to include image annotations in layout parser response.
190
+
"enableImageExtraction": True or False, # Optional. Whether to extract images in layout parser response.
189
191
"enableLlmLayoutParsing": True or False, # Optional. Whether to refine PDF layout using LLM.
192
+
"enableTableAnnotation": True or False, # Optional. Whether to include table annotations in layout parser response.
190
193
"returnBoundingBoxes": True or False, # Optional. Whether to include bounding boxes in layout parser processor response.
191
194
"returnImages": True or False, # Optional. Whether to include images in layout parser processor response.
192
195
},
@@ -670,6 +673,9 @@ <h3>Method Details</h3>
670
673
"pageStart": 42, # Page where block starts in the document.
671
674
},
672
675
"tableBlock": { # Represents a table type block. # Block consisting of table content/structure.
676
+
"annotations": { # Represents the annotation of a block or a chunk. # Annotation of the table block.
677
+
"description": "A String", # The description of the content with this annotation.
678
+
},
673
679
"bodyRows": [ # Body rows containing main table content.
674
680
{ # Represents a row in a table.
675
681
"cells": [ # A table row is a list of table cells.
@@ -759,6 +765,7 @@ <h3>Method Details</h3>
759
765
"nanos": 42, # Number of nano (10^-9) units of the amount. The value must be between -999,999,999 and +999,999,999 inclusive. If `units` is positive, `nanos` must be positive or zero. If `units` is zero, `nanos` can be positive, zero, or negative. If `units` is negative, `nanos` must be negative or zero. For example $-1.75 is represented as `units`=-1 and `nanos`=-750,000,000.
760
766
"units": "A String", # The whole units of the amount. For example if `currencyCode` is `"USD"`, then 1 unit is one US dollar.
761
767
},
768
+
"signatureValue": True or False,
762
769
"text": "A String", # Optional. An optional field to store a normalized string. For some entity types, one of respective `structured_value` fields may also be populated. Also not all the types of `structured_value` will be normalized. For example, some processors may not generate `float` or `integer` normalized text by default. Below are sample formats mapped to structured values. - Money/Currency type (`money_value`) is in the ISO 4217 text format. - Date type (`date_value`) is in the ISO 8601 text format. - Datetime type (`datetime_value`) is in the ISO 8601 text format.
763
770
},
764
771
"pageAnchor": { # Referencing the visual context of the entity in the Document.pages. Page anchors can be cross-page, consist of multiple bounding polygons and optionally reference specific layout element types. # Optional. Represents the provenance of this entity wrt. the location on the page where it was found.
@@ -1661,6 +1668,9 @@ <h3>Method Details</h3>
1661
1668
"pageStart": 42, # Page where block starts in the document.
1662
1669
},
1663
1670
"tableBlock": { # Represents a table type block. # Block consisting of table content/structure.
1671
+
"annotations": { # Represents the annotation of a block or a chunk. # Annotation of the table block.
1672
+
"description": "A String", # The description of the content with this annotation.
1673
+
},
1664
1674
"bodyRows": [ # Body rows containing main table content.
1665
1675
{ # Represents a row in a table.
1666
1676
"cells": [ # A table row is a list of table cells.
@@ -1750,6 +1760,7 @@ <h3>Method Details</h3>
1750
1760
"nanos": 42, # Number of nano (10^-9) units of the amount. The value must be between -999,999,999 and +999,999,999 inclusive. If `units` is positive, `nanos` must be positive or zero. If `units` is zero, `nanos` can be positive, zero, or negative. If `units` is negative, `nanos` must be negative or zero. For example $-1.75 is represented as `units`=-1 and `nanos`=-750,000,000.
1751
1761
"units": "A String", # The whole units of the amount. For example if `currencyCode` is `"USD"`, then 1 unit is one US dollar.
1752
1762
},
1763
+
"signatureValue": True or False,
1753
1764
"text": "A String", # Optional. An optional field to store a normalized string. For some entity types, one of respective `structured_value` fields may also be populated. Also not all the types of `structured_value` will be normalized. For example, some processors may not generate `float` or `integer` normalized text by default. Below are sample formats mapped to structured values. - Money/Currency type (`money_value`) is in the ISO 4217 text format. - Date type (`date_value`) is in the ISO 8601 text format. - Datetime type (`datetime_value`) is in the ISO 8601 text format.
1754
1765
},
1755
1766
"pageAnchor": { # Referencing the visual context of the entity in the Document.pages. Page anchors can be cross-page, consist of multiple bounding polygons and optionally reference specific layout element types. # Optional. Represents the provenance of this entity wrt. the location on the page where it was found.
@@ -2561,7 +2572,10 @@ <h3>Method Details</h3>
2561
2572
"includeAncestorHeadings": True or False, # Optional. Whether or not to include ancestor headings when splitting.
2562
2573
"semanticChunkingGroupSize": True or False, # Optional. The number of tokens to group together when evaluating semantic similarity. THIS FIELD IS NOT YET USED.
2563
2574
},
2575
+
"enableImageAnnotation": True or False, # Optional. Whether to include image annotations in layout parser response.
2576
+
"enableImageExtraction": True or False, # Optional. Whether to extract images in layout parser response.
2564
2577
"enableLlmLayoutParsing": True or False, # Optional. Whether to refine PDF layout using LLM.
2578
+
"enableTableAnnotation": True or False, # Optional. Whether to include table annotations in layout parser response.
2565
2579
"returnBoundingBoxes": True or False, # Optional. Whether to include bounding boxes in layout parser processor response.
2566
2580
"returnImages": True or False, # Optional. Whether to include images in layout parser processor response.
2567
2581
},
@@ -2753,6 +2767,9 @@ <h3>Method Details</h3>
2753
2767
"pageStart": 42, # Page where block starts in the document.
2754
2768
},
2755
2769
"tableBlock": { # Represents a table type block. # Block consisting of table content/structure.
2770
+
"annotations": { # Represents the annotation of a block or a chunk. # Annotation of the table block.
2771
+
"description": "A String", # The description of the content with this annotation.
2772
+
},
2756
2773
"bodyRows": [ # Body rows containing main table content.
2757
2774
{ # Represents a row in a table.
2758
2775
"cells": [ # A table row is a list of table cells.
@@ -2842,6 +2859,7 @@ <h3>Method Details</h3>
2842
2859
"nanos": 42, # Number of nano (10^-9) units of the amount. The value must be between -999,999,999 and +999,999,999 inclusive. If `units` is positive, `nanos` must be positive or zero. If `units` is zero, `nanos` can be positive, zero, or negative. If `units` is negative, `nanos` must be negative or zero. For example $-1.75 is represented as `units`=-1 and `nanos`=-750,000,000.
2843
2860
"units": "A String", # The whole units of the amount. For example if `currencyCode` is `"USD"`, then 1 unit is one US dollar.
2844
2861
},
2862
+
"signatureValue": True or False,
2845
2863
"text": "A String", # Optional. An optional field to store a normalized string. For some entity types, one of respective `structured_value` fields may also be populated. Also not all the types of `structured_value` will be normalized. For example, some processors may not generate `float` or `integer` normalized text by default. Below are sample formats mapped to structured values. - Money/Currency type (`money_value`) is in the ISO 4217 text format. - Date type (`date_value`) is in the ISO 8601 text format. - Datetime type (`datetime_value`) is in the ISO 8601 text format.
2846
2864
},
2847
2865
"pageAnchor": { # Referencing the visual context of the entity in the Document.pages. Page anchors can be cross-page, consist of multiple bounding polygons and optionally reference specific layout element types. # Optional. Represents the provenance of this entity wrt. the location on the page where it was found.
0 commit comments