-
Notifications
You must be signed in to change notification settings - Fork 128
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TypeError : cell_to_boundary() got an unexpected keyword argument 'geo_json' #380
Comments
Could you give an example of the behavior you're expecting? Also, this is for v3.7. You may want to try the new v4.0: |
when I use the function I try to pass it explicitly the assignment of a value to the geo_json argurment but it does not like when i do that. the example is What I expect to do: useGeoJsonFormat = True
cell_value = '827507fffffffff'
h3.cell_to_boundary(cell_value, geo_json=useGeoJsonFormat) This thows the error in the title What I end up having to do that works and is a work around useGeoJsonFormat = True
cell_value = '827507fffffffff'
h3.cell_to_boundary(cell_value, useGeoJsonFormat) |
Looking through the source code, myself, I'm not sure that EDIT: I don't see it in the Cython, either, though I didn't expect it there; more that it'd be at a higher level restructuring it's output. EDIT2: I did a local check of the repo and there's only one place where the string
So I think this feature was accidentally dropped during the rewrite for H3 4.0 vs 3.x. @tomrussell-willdan I would say if you need this feature, at the moment you should use h3-py's 3.7.x release, calling |
thanks. I think for now we will stick on 4.0 and just flip the output ourselves. So is the plan to continue having arguements for geo_json conformity and it was just accidently not included or is the plan to not continue supporting it those arguements? |
cell_to_boundary() not accepting direct assingment of arguement for unpacking.
![image](https://private-user-images.githubusercontent.com/94702949/339446603-722ea6b2-5838-48f3-b0c0-ceb13cbc37c9.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjA3NDE5NzAsIm5iZiI6MTcyMDc0MTY3MCwicGF0aCI6Ii85NDcwMjk0OS8zMzk0NDY2MDMtNzIyZWE2YjItNTgzOC00OGYzLWIwYzAtY2ViMTNjYmMzN2M5LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MTElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzExVDIzNDc1MFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTQxODIzYWFkYjE1NjlkZGVhN2FhMTczOGRjM2EyZGYzYjU4NDlkYjEwZGFiODczYjBhNThjNmU2ODdiM2JiOWUmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.7BmobjKP85-qGqgWieq8fgxm4N_xxzq61MY_tX7bHhI)
The text was updated successfully, but these errors were encountered: