shapely==2.0a1 alongside GeoPandas? Would be nice to start using some of the new features from shapely v2 but currently clashes with GeoPandas. I see there is a pull request geopandas/geopandas#2275 working on this, so maybe this will be released into a prerelease at some point in the near-ish future?
Hey guys, quick question about runtime performance improvement for pygeos:
is it possible to store pygeos objects, such as Polygons, as memory-mapped files? Given that I have bunch of planes growing throughout simulation, but not every part of polygon is accessed or written at each time step, it would be great if it can be mapped to memory, such as numpy memory mapped arrays...
But opening a multi-processing of a GEOS object is possible right? There is a way to pass the Polygon instance between different processes? Do I need to define that explicitly?
Between different processes you will have to actually copy (serialize/deserialize) the object, you can't share such a python object between processes. You can do that in multithreading though (we do that in dask-geopandas)
But opening a multi-processing of a GEOS object is possible right? There is a way to pass the Polygon instance between different processes? Do I need to define that explicitly?
Between different processes you will have to actually copy (serialize/deserialize) the object, you can't share such a python object between processes. You can do that in multithreading though (we do that in dask-geopandas)
Once you share the copy, you would have to merge the final version of all parallel processed polygons together?
But opening a multi-processing of a GEOS object is possible right? There is a way to pass the Polygon instance between different processes? Do I need to define that explicitly?
Between different processes you will have to actually copy (serialize/deserialize) the object, you can't share such a python object between processes. You can do that in multithreading though (we do that in dask-geopandas)
Following up on this one, can I use Dask-Geopandas or Geopandas to do operations that are done in pygeos? such as polygon.intersect(), polygon.union_all() ?
And if I use Geopands to check the element-wise intersection between a list of polygons and another geometry, is this faster than using list comprehension to check those intersections?
You don't need cython if you install pygeos from pip or conda but you do need it if you want to install from source.
Following up on this one, can I use Dask-Geopandas or Geopandas to do operations that are done in pygeos? such as polygon.intersect(), polygon.union_all() ?
Yes, if you have pygeos installed, it is automatically used under the hood to do all these. Not that the unary_union is the name for union_all in geopandas.
And if I use Geopands to check the element-wise intersection between a list of polygons and another geometry, is this faster than using list comprehension to check those intersections?
Yes, much faster as it is using vectorized approach of pygeos.
2 replies
I'm trying to create all the ci envs on a vagrant box, all work except
(base) vagrant@gpd:~$ mamba env update -q -n 38-pd11-defaults -f /home/vagrant/geopandas/ci/envs/38-pd11-defaults.yaml
Encountered problems while solving:
- nothing provides gdal 1.11.4 needed by fiona-1.6.3-np110py27_0Is there a different approach to creating these envs that works for all?
I'm trying to create all the ci envs on a vagrant box, all work except
(base) vagrant@gpd:~$ mamba env update -q -n 38-pd11-defaults -f /home/vagrant/geopandas/ci/envs/38-pd11-defaults.yaml Encountered problems while solving: - nothing provides gdal 1.11.4 needed by fiona-1.6.3-np110py27_0Is there a different approach to creating these envs that works for all?
FYI using mambaforge instead of miniconda resolves
A reminder that we have a scheduled GeoPandas community meeting today Thursday, November 24 at 17:00 UTC.
Tentative agenda and notes (feel free to add points ahead of the meeting): https://hackmd.io/pq8MqmtxTFqqaiayFuuEYQ
Link to the Zoom meeting: https://us06web.zoom.us/j/88360697466?pwd=ZXlxSXd6WWI2bEoxS2ZzbjZSa3d5Zz09
As always, we welcome not only the geopandas collaborators but everyone willing to spend some time talking about GeoPandas (and related packages) and its future. Also, feel free to join as observers only.