Left examples have the keyword "literalgeometry" on the OEBP.

As a default, it is assumed on the OEBP that submitted examples are imperfect drawings. A problem about circles may only feature what are approximately circles in its examples. Thus, most solutions to Bongard Problems have the implicit caveat "...if shapes in drawings are parsed as what they most intuitively approximate." In literalgeometry problems, this caveat is dropped; the solution is based on the literal geometry of the drawings used as examples, including all subtle imperfections.

Bitmaps can only hold so much information, so even in literalgeometry Problems it is not expected that the solver will take into account pixelation of images. (Problems in which pixelation is relevant are usually assigned the world "bmp" on the OEBP.) In literalgeometry Problems having to do with smooth curves and lines using pixelated images such as .png, .gif, .bmp, and .jpg files, it is only necessary that the pixelated images offer the best possible approximation of the underlying shape given their resolutions.

Regardless of whether in literalgeometry Problems or not, .svg scalable vector graphics files are always assumed to be parsed as their literal geometry. Do not upload .svg files with imperfections, unless the BP solution is explicitly about those imperfections.

Just because a Problem involves small details does not make it "literalgeometry." It is possible for a Problem to involve small imperfections, but still be about the intuitive parsings of drawings rather than the literal geometry in the drawings, e.g. BP148 or BP119.

See BP508 for more discussion of this.

Left examples have the keyword "literalgeometry" on the OEBP.

As a default, it is assumed on the OEBP that submitted examples are imperfect drawings. A problem about circles may only feature what are approximately circles in its examples. Thus, most solutions to Bongard Problems have the implicit caveat "...if shapes in drawings are parsed as what they most intuitively approximate." In literalgeometry problems, this caveat is dropped; the solution is based on the literal geometry of the drawings used as examples, including all subtle imperfections.

Bitmaps can only hold so much information, so even in literalgeometry Problems it is not expected that the solver will take into account pixelation of images. (Problems in which pixelation is relevant are usually assigned the world "bmp" on the OEBP.) In literalgeometry Problems having to do with smooth curves and lines using pixelated images such as .png, .gif, .bmp, and .jpg files, it is only necessary that the pixelated images offer the best possible approximation of the underlying shape given their resolutions.

Regardless of whether in literalgeometry Problems or not, .svg scalable vector graphics files are always assumed to be parsed as their literal geometry. Do not upload .svg files with imperfections, unless the BP solution is explicitly about those imperfections.

Just because a Problem involves small details does not make it about "literalgeometry." It is possible for a Problem to involve small imperfections, but still be about the intuitive parsings of drawings rather than the literal geometry in the drawings, e.g. BP148 or BP119.

See BP508 for more discussion of this.

Left examples have the keyword "literalgeometry" on the OEBP.

As a default, it is assumed on the OEBP that submitted examples are imperfect drawings. A problem about circles may only feature what are approximately circles in its examples. Thus, most solutions to Bongard Problems have the implicit caveat "...if shapes in drawings are parsed as what they most intuitively approximate." In literalgeometry problems, this caveat is dropped; the solution is based on the literal geometry of the drawings used as examples, including all subtle imperfections.

Bitmaps can only hold so much information, so even in literalgeometry Problems it is not expected that the solver will take into account pixellation of images. (Problems in which pixellation is relevant are usually assigned the world "bmp" on the OEBP.) In literalgeometry Problems having to do with smooth curves and lines using pixellated images such as .png, .gif, .bmp, and .jpg files, it is only necessary that the pixellated images offer the best possible approximation of the underlying shape given their resolutions.

Regardless of whether in literalgeometry Problems or not, .svg scalable vector graphics files are always assumed to be parsed as their literal geometry. Do not upload .svg files with imperfections, unless the BP solution is explicitly about those imperfections.

Just because a Problem involves small details does not make it about "literalgeometry." It is possible for a Problem to involve small imperfections, but still be about the intuitive parsings of drawings rather than the literal geometry in the drawings, e.g. BP148 or BP119.

See BP508 for more discussion of this.

Left examples have the keyword "literalgeometry" on the OEBP.

As a default, it is assumed on the OEBP that submitted examples are imperfect drawings. A problem about circles may only feature what are approximately circles in its examples. Thus, most solutions to Bongard Problems have the implicit caveat "...if shapes in drawings are parsed as what they most intuitively approximate." In literalgeometry problems, this caveat is dropped; the solution is based on the literal geometry of the drawings used as examples, including all subtle imperfections.

Bitmaps can only hold so much information, so even in literalgeometry Problems it is not expected that the solver will take into account pixellation of images. (Problems in which pixellation is relevant usually have world "bmp".) In literalgeometry Problems having to do with smooth curves and lines using pixellated images such as .png, .gif, .bmp, and .jpg files, it is only necessary that the pixellated images offer the best possible approximation of the underlying shape given their resolutions.

Regardless of whether in literalgeometry Problems or not, .svg scalable vector graphics files are always assumed to be parsed as their literal geometry. Do not upload .svg files with imperfections, unless the BP solution is explicitly about those imperfections.

Just because a Problem involves small details does not make it about "literalgeometry." It is possible for a Problem to involve small imperfections, but still be about the intuitive parsings of drawings rather than the literal geometry in the drawings, e.g. BP148 or BP119.

See BP508 for more discussion of this.

Many Bongard Problems involving properties of curves (e.g. BP62) really are about the properties of those wiggly, imperfect curves; they qualify as literal geometry problems. On the other hand, Bongard Problems involving, say, polygons, (e.g. BP5) often show only very-closely-approximately-straight lines; they are not literal geometry problems.

Problems with world "bmp" should be literalgeometry Problems.

Problems with world "bmp" (left-BP822) should be literalgeometry Problems.

Left examples have the keyword "literalgeometry" on the OEBP.

As a default, it is assumed on the OEBP that submitted examples are imperfect drawings. A problem about circles may only feature what are approximately circles in its examples. Thus, most solutions to Bongard Problems have the implicit caveat "...if shapes in drawings are parsed as what they most intuitively approximate." In literalgeometry problems, this caveat is dropped; the solution is based on the literal geometry of the drawings used as examples, including all subtle imperfections.

However, regardless of context, .svg scalable vector graphics files are always assumed to be parsed as their literal geometry. Do not upload .svg files with imperfections, unless the BP solution is explicitly about those imperfections.

Just because a Problem involves small details does not make it about "literalgeometry." It is possible for a Problem to involve small imperfections, but still be about the intuitive parsings of drawings rather than the literal geometry in the drawings, e.g. BP148 or BP119.

See BP508 for more discussion of this.

Many Bongard Problems involving properties of curves (e.g. BP62) really are about the properties of those wiggly, imperfect curves; they qualify as literal geometry problems. On the other hand, Bongard Problems involving, say, polygons, (e.g. BP5) often show only very-closely-approximately-straight lines; they are not literal geometry problems.

Left examples have the keyword "literalgeometry" on the OEBP.

As a default, it is assumed on the OEBP that submitted examples are imperfect drawings. A problem about circles may only feature what are approximately circles in its examples. Thus, most solutions to Bongard Problems have the implicit caveat "...if shapes in drawings are parsed as what they most intuitively approximate." In literalgeometry problems, this caveat is not present; the solution is based on the literal geometry of the drawings used as examples, including all subtle imperfections.

However, regardless of context, .svg scalable vector graphics files are always assumed to be parsed as their literal geometry. Do not upload .svg files with imperfections, unless the BP solution is explicitly about those imperfections.

Just because a Problem involves small details does not make it about "literalgeometry." It is possible for a Problem to involve small imperfections, but still be about the intuitive parsings of drawings rather than the literal geometry in the drawings, e.g. BP148 or BP119.

See BP508 for more discussion of this.

Many Bongard Problems involving properties of curves (e.g. BP62) really are about the properties of those wiggly, imperfect curves; they qualify as literal geometry problems. On the other hand, Bongard Problems involving, say, polygons, (e.g. BP5) often use approximate drawings of those polygons; they are not literal geometry problems.

Left examples have the keyword "literalgeometry" on the OEBP.

As a default, it is assumed on the OEBP that submitted examples are imperfect drawings. A problem about circles may only feature what are approximately circles in its examples. Thus, most solutions to Bongard Problems have the implicit caveat "...if shapes in drawings are parsed as what they most intuitively approximate." In literalgeometry problems, this caveat is not present; the solution is based on the literal geometry of the drawings used as examples, including all subtle imperfections.

However, regardless of context, .svg scalable vector graphics files are always assumed to be parsed as their literal geometry. Do not upload .svg files with imperfections, unless the BP solution is explicitly about those imperfections.

Most Bongard Problems involving properties of curves (see BP530) are about the literal geometry of those curves; they qualify as literal geometry problems. On the other hand, Bongard Problems involving, say, polygons, often use approximate drawings of those polygons; they are not literal geometry problems.

Just because a Problem involves small details does not make it about "literalgeometry." It is possible for a Problem to involve small imperfections, but still be about the intuitive parsings of drawings rather than the literal geometry in the drawings, e.g. BP148 or BP119.

See BP508 for more discussion of this.