You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, thanks for the library! It's very helpful for reducing the size of GeoJSONs.
I was curious if there was a way for me to add/remove features from an existing Topology.
In my use case, I am converting a few hundred GeoJSON features to a Topology every X minutes per my cron job cadence. The number of features varies and when the number gets higher, the process gets a lot slower.
However, a large percent of these features would be the same from run to run.
So I was curious if it would be feasible to add a way to add or remove features to an existing Topology (which i could cache between runs) and it would be less compute intensive than recomputing with all of the features.
The text was updated successfully, but these errors were encountered:
Very interesting question! And very useful feature request. I think the first step would be to find out if there is any existing literature on this topic. Do you know some of this?
Hi, thanks for the library! It's very helpful for reducing the size of GeoJSONs.
I was curious if there was a way for me to add/remove features from an existing Topology.
In my use case, I am converting a few hundred GeoJSON features to a Topology every X minutes per my cron job cadence. The number of features varies and when the number gets higher, the process gets a lot slower.
However, a large percent of these features would be the same from run to run.
So I was curious if it would be feasible to add a way to add or remove features to an existing Topology (which i could cache between runs) and it would be less compute intensive than recomputing with all of the features.
The text was updated successfully, but these errors were encountered: