It would be nice to have a separate supported RTree implementation without the GeoJSON stuff that can be used for general use cases, and additionally a rtree-geojson.js extension or something like this.
I don't see any reason to have them combined if this is going to become a standard RTree JS implementation.
It would be nice to have a separate supported RTree implementation without the GeoJSON stuff that can be used for general use cases, and additionally a
rtree-geojson.jsextension or something like this.I don't see any reason to have them combined if this is going to become a standard RTree JS implementation.