I removed a test so that I can investigate properly from #816 for ST_ReducePrecision for geography (which bigquery calls ST_SnapToGrid). We might also want to investigate naming them the same thing (but also investigate the specifics of the difference between ST_SnapToGrid and ST_ReducePrecision in PostGIS...I think snaptogrid is faster but maybe doesn't do validity checking in the same way).
# Linestring: component collapses because the endpoints snap together
pytest.param(
"LINESTRING (0.01 0.02, 0.03 0.04)",
1.0,
"LINESTRING EMPTY",
id="linestring_collapse",
),
BigQuery gives POINT (0 0) here, which keep the collapsed component
I removed a test so that I can investigate properly from #816 for ST_ReducePrecision for geography (which bigquery calls ST_SnapToGrid). We might also want to investigate naming them the same thing (but also investigate the specifics of the difference between ST_SnapToGrid and ST_ReducePrecision in PostGIS...I think snaptogrid is faster but maybe doesn't do validity checking in the same way).
BigQuery gives
POINT (0 0)here, which keep the collapsed component