max-mapper / max-mapper/geojson2rtree
slows down after about 100K inserts
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 9
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
to reproduce, convert ftp://ftp02.portlandoregon.gov/CivicApps/Building_Footprints_pdx.zip to geojson:
ogr2ogr -f GeoJSON -t_srs crs:84 buildings_pdx.geojson Building_Footprints_pdx/PortlandBuildings\\Building_Footprints_pdx.shp
then do geojson2rtree buildings_pdx.geojson and watch it slow down at around 100K
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue with the provided ogr2ogr conversion and the geojson2rtree buildings_pdx.geojson command. Start at the geojson2rtree entry point and inspect what happens as processing reaches about 100K inserts. Done means the same dataset no longer shows the reported slowdown.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100