Initial commit

[alasarr]

On this PR, I've moved the scripts from: opengeospatial/geoparquet#113

I've also added several improvements:

• Remove poetry, I really like poetry as a developer but I think could be an issue for adoption as not all users use poetry.
• Allow overwriting files.
• Update some dependencies.
• CI for testing.
• CI job to upload several tables to gs://geoparquet. I've added US boundaries.

The following files have been created from bigquery and uploaded to geoparquet bucket:

https://storage.googleapis.com/geoparquet/geography_usa_state_2019.parquet
https://storage.googleapis.com/geoparquet/geography_usa_county_2019.parquet
https://storage.googleapis.com/geoparquet/geography_usa_censustract_2019.parquet
https://storage.googleapis.com/geoparquet/geography_usa_zcta5_2019.parquet
https://storage.googleapis.com/geoparquet/geography_usa_blockgroup_2019.parquet

[cholmes]

Looks good, but I'm not a python dev so only am commenting on the readme - put in a minor language edit.

[kylebarron]

• Remove poetry, I really like poetry as a developer but I think could be an issue for adoption as not all users use poetry

It's fine if you don't use poetry here, but just as a general comment, poetry supports PEP 517, so you don't need poetry installed to install a package that uses poetry. pip install . will just work.

[kylebarron]

• Remove poetry, I really like poetry as a developer but I think could be an issue for adoption as not all users use poetry

It's fine if you don't use poetry here, but just as a general comment, poetry supports PEP 517, so you don't need poetry installed to install a package that uses poetry. pip install . will just work.

[alasarr]

It's fine if you don't use poetry here, but just as a general comment, poetry supports PEP 517, so you don't need poetry installed to install a package that uses poetry. pip install . will just work.

No idea about it @kylebarron, thanks for letting me know. I'll add poetry then, if you want to commit that would be great too.