BigQuery scripts to import/export GeoParquet files #113
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
alasarr
commented
Jun 14, 2022
| @@ -6,12 +6,14 @@ authors = [] | |||
| license = "MIT" | |||
|
|
|||
| [tool.poetry.dependencies] | |||
| python = "^3.8" | |||
| python = ">=3.8,<3.11" | |||
There was a problem hiding this comment.
Google BigQuery requires this
kylebarron
reviewed
Jun 14, 2022
|
|
||
| if mode.upper() == 'FOLDER': | ||
| # We need to export to multiple files, because a single file might hit bigquery limits (UDF out of memory). https://cloud.google.com/bigquery/docs/loading-data-cloud-storage-parquet | ||
| pq.write_to_dataset(arrow_table, root_path=output, partition_cols=['__partition__'], compression=compression) |
There was a problem hiding this comment.
We should still have a discussion on best practices for partitioned datasets. #79 Specifically around whether the _metadata file is required/suggested/etc.
There was a problem hiding this comment.
Good point, will follow the conversation there
kylebarron
reviewed
Jun 14, 2022
kylebarron
reviewed
Jun 14, 2022
| pyarrow = "^7.0.0" | ||
| geopandas = "^0.10.2" | ||
| pygeos = "^0.12.0" | ||
| pandas = "^1.4.2" | ||
| click = "^8.1.2" | ||
| google-cloud-bigquery = "^3.2.0" | ||
| db-dtypes = "^1.0.2" |
There was a problem hiding this comment.
Is this used? It doesn't appear to be imported
There was a problem hiding this comment.
I added it because google-cloud-bigquery complained about it by asking to install it, so I did
|
Closing this, as we'll move it over to https://github.com/geoparquet/bigquery-converter and keep the main geoparquet repo more focused on the spec. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR allows:
It doesn't aim to be a production-ready solution, in the future, it will be supported natively by BigQuery. However, in the meantime, it provides a way to work with GeoParquet and BigQuery.
Convert a SQL query to parquet:
poetry run python bigquery_to_parquet.py \ --input-query "SELECT * FROM carto-do-public-data.carto.geography_usa_blockgroup_2019" \ --primary-column geom \ --output geography_usa_blockgroup_2019Upload a parquet file or folder to BigQuery:
poetry run python parquet_to_bigquery.py \ --input geography_usa_blockgroup_2019 \ --output "cartodb-gcp-backend-data-team.alasarr.geography_usa_blockgroup_2019"I've extracted to a global module some of the code generated at #87