feat(query): implement ST_GEOMFROMGEOHASH

[kkk25641463]

I hereby agree to the terms of the CLA available at: https://docs.databend.com/dev/policies/cla/

Summary

feat: Implement st_geompointfromgeohash()
Currently the precision only implement within 12 digits. And I found that ST_GEOMFROMGEOHASH() returned value is geojson type.
I'm not sure whether we should implement subtypes with geometry type like number type or decimal type? And output can be choose with subtypes like ewkb、ewkt、geojson, otherwise i have to check types by alot of match case in display logic.

            ScalarRef::Geometry(s) => {
                let ewkb = Ewkb(s.to_vec());
                let value = match ewkb.to_ewkt(ewkb.srid()) {
                    Ok(ewkt) => ewkt,
                    Err(_) => GeoJson(std::str::from_utf8(s).unwrap()).to_json().unwrap(),
                };
                write!(f, "'{value:?}'")

see alse try_to_ geometry.

Tests

• Unit Test
• Logic Test
• Benchmark Test
• No Test - Explain why

Type of change

• Bug Fix (non-breaking change which fixes an issue)
• New Feature (non-breaking change which adds functionality)
• Breaking Change (fix or feature that could cause existing functionality not to work as expected)
• Documentation Update
• Refactoring
• Performance Improvement
• Other (please describe):

[kkk25641463]

@ariesdevil help me to check plz.

[sundy-li]

Currently the precision only implement within 12 digits

Can we add another register ST_GEOMFROMGEOHASH( <geohash> [, <precision> ] ) in this pr ?

seems it's limited by geohash crate.

[sundy-li]

I'm not sure whether we should implement subtypes with geometry type like number type or decimal type?

That's a little complicated, we do not decide to address that.

[kkk25641463]

Currently the precision only implement within 12 digits

Can we add another register ST_GEOMFROMGEOHASH( <geohash> [, <precision> ] ) in this pr ?

seems it's limited by geohash crate.

The pr depends on geohash algorithm which only support less than 12 precision and is not maintenance by maintainer. Algorithms that support arbitrary precision require rewriting most of code in geohash decode_bbox() function which are break changes. And 12 bit accuracy can meet most geo application needs.
I can add ST_GEOMFROMGEOHASH( <geohash> [, <precision> ] ) define first

[kkk25641463]

I'm not sure whether we should implement subtypes with geometry type like number type or decimal type?

That's a little complicated, we do not decide to address that.

Is this the reason of the work to maintain the geozero library?

[sundy-li]

geozIs this the reason of the work to maintain the geozero library?ero

Part of, another consideration is that we don't want to introduce too much datatypes in DataType