Henrikki Tenkanen

@bramson Thanks for sharing your ideas! 👍 Being able to export networkx graph as GeoJSON is certainly a good idea. However, I think that the correct place for implementing such...

@bramson Yes, supporting the export of geospatial network from nx is definitely something that should be implemented. It can be decided later what will be the final home for that...

Hmm, this sounds weird. A pbf of that size should fit to the memory if you have 16GB RAM. I assume you don't have anything else running at the same...

The nodes, ways and relations are indeed parsed with the `osm._read_pbf()` method ~~but that is not typically the point when the memory is consumed the most (the numpy arrays are...

Yes, unfortunately due to the logic how pyrosm now reads everything into memory at a first step, is not a good solution. There is discussion about this topic in many...

@majkshkurti Which operating system you are working with? If on Unix, adding more Swap memory can help a little bit this issue: https://linuxize.com/post/how-to-add-swap-space-on-ubuntu-20-04/

Hmm, okay there is actually a significant different between the memory usage of pyrosm v0.5.3 vs the current version. With `pyrosm==0.5.3` parsing e.g. the mittelfranken PBF can be done with...

Ah, yes sure, with Docker it can indeed be tricky to do any tricks with swap memory. I already did a bit of improvements (in #151) which helped to bring...

@grndng : Hi thanks for raising this issue! This is most likely due to an updated version of pygeos/shapely, and these changes have not yet been accounted for in pyrosm....

Thanks guys for reporting. Will take a look at this after first getting more urgent maintenance related issues fixed.