start geopandas extension #728
Conversation
|
resolves #136 |
|
Keep me in the loop. Happy to do a proper review of this from the geopandas perspective once @kylebarron is happy. |
|
i think this should be ready, though I'm not the best with type hints or google docstrings |
|
Can you check why pre-commit is still failing? You should be able to run it locally with |
|
@martinfleis do you have any comments on this PR? I'd like to get in #753, which in general raises the code quality of the code base, and then ensure that this PR meets that bar as well. |
lonboard/geopandas.py
Outdated
| elevation : Name of column on the dataframe used to extrude each geometry or | ||
| an array-like in the same order as observations. Defaults to None. | ||
| extruded : Whether to extrude geometries using the z-dimension. |
There was a problem hiding this comment.
I probably don't follow here. Shouldn't extruded be automatically True when elevation is provided? Like the two are tied together, no? Or can I use extruded without elevation? What does it extrude on, then, Z coordinate? How?
There was a problem hiding this comment.
i agree this is a little awkward. There's probably no need for the bool, though I was just trying to follow the viz/Layer API which treats them separately. Happy to go with consensus here.
Another small wrinkle is that sometimes in GIS or CAD software (IIRC anyway) 'elevation' sometimes refers to the height beneath the polygon, e.g. so you can drop the extruded poly onto a DEM for things like viewsheds. In that case I want to say this parameter is called 'extrusion_height' or something? No real opinion here, just something to consider in case folks are coming from that world
There was a problem hiding this comment.
i removed the bool so that its turned on automatically if elevation is passed
Co-authored-by: Kyle Barron <[email protected]>
|
I merged #753; would you be able to merge in latest main? |
|
looks like the only remaining failures are from the demo notebook. Could probably fix many of them, but seems a little overkill to add type annotations to some quick functions in an example notebook |
|
fixed annotations in the notebook so im not sure what the lingering failure is |
|
copiolt thinks the failure is a caching issue (apparently), so i'd guess it will pass if re-run on its own |
|
looks like maybe some other parts of the stack are moving at the moment, but let me know if there's anything I can do to help move this forward :) |
to begin review. The notebook at examples/explore should run through and demonstrate functionality. I need to take a look at how you prefer to test against Maps