paleolimbot commented on issue #180:
URL: https://github.com/apache/sedona-db/issues/180#issuecomment-3581912331
There are a few potentially useful things we can do here. First, we could
formalize the script we use to generate the one file (this would probably be a
good time to also split up everything so we have one markdown file per
function. I just found this out but apparently it's available from the
information schema:
```python
import sedona.db
sd = sedona.db.connect()
sd.sql("""
SELECT DISTINCT routine_name
FROM information_schema.routines
WHERE routine_type = 'FUNCTION' AND routine_name LIKE 'st%'
ORDER BY routine_name
""").show()
#> ┌────────────────┐
#> │ routine_name │
#> │ utf8 │
#> ╞════════════════╡
#> │ st_analyze_agg │
#> ├╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┤
#> │ st_area │
#> ├╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┤
#> │ st_asbinary │
#> ├╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┤
```
I think after we do that generation we might want to have the individual
markdown files be the canonical documentation for that function. We can make
them `.qmd` files and use Quarto to execute them (among other things, this
would let us include plot output in the results so we could visualize some of
these functions!).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
