-
Notifications
You must be signed in to change notification settings - Fork 161
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Community microservice #80
Comments
Ah, I'm interested in helping 👋 this could be fun. You could push all the data into Rbush or create an mbtiles (spatialite? 🤔 ) for static access if you don't want a database. |
Cool @kamicut it would be fun to build this! I discussed this briefly with @mourner last week and he pointed me at which-polygon - this is what I'm using on the iD side. It takes a bunch of geojsons and puts them into an rbush index for fast bbox querying, then does a point-in-polygon test on the results. The up FAQ has some information about what it does, basically wrap the application in a Lambda function and push it to AWS, abstracting away all the scary parts. I am a total n00b at this. My understanding is that AWS Lambda will keep function's execution context around for a little while (it can "freeze" and "thaw" them) in case it gets called again - so I'm assuming that the even though building the index of geojsons is very fast, it wouldn't have to happen every time we call the service. |
I've used I also like the approach of datasette with |
@kamicut at this point I wouldn't worry about serializing the index — it's too cheap to calculate and the original data is too small (just 150kb uncompressed). We can reconsider when we need to scale significantly. |
I will also try to add this to my "tool" : https://community.osm.be/ :) |
stale |
We could experiment putting this community index behind a simple microservice so that any requestor can ask "what are the communities around this lat/long point" and get back an answer.
I've been wanting to play around with up for a while and that might be a fun use of the technology. (It's free up until we hit 1 million requests per month).
cc @mikelmaron
The text was updated successfully, but these errors were encountered: