This is pretty great. After banging my head over the weird state of python + GIS for the past month and a half, this feels very welcome. Also, is it down for anyone else? As soon as I tried uploading a file, it became unresponsive..
Introducing Kepler.gl, an Open-Source Geospatial Toolbox
11–20 of 24 posts
Re: Introducing Kepler.gl, an Open-Source Geospatial Toolbox
#12I'd love to chat with some of the Uber engineers who worked on this. I'm a Redux maintainer, and I'm always eager to hear feedback from people who are building serious applications with Redux.
Re: Introducing Kepler.gl, an Open-Source Geospatial Toolbox
#13Sweet, it's all built with React and Redux! And there's some _very_ hefty reducer logic in there. I'd love to chat with some of the Uber engineers who worked on this. I'm a Redux maintainer, and I'm always eager to hear feedback from people who are building serious applications with Redux.
Re: Introducing Kepler.gl, an Open-Source Geospatial Toolbox
#14Sweet, it's all built with React and Redux! And there's some _very_ hefty reducer logic in there. I'd love to chat with some of the Uber engineers who worked on this. I'm a Redux maintainer, and I'm always eager to hear feedback from people who are building serious applications with Redux.
That would make it me, I’m surprised people already start noticing the reducer logic in there. Better get the docs out soon :)
Only looked through the code for a few minutes, but a couple things I noticed:
- You've got an interesting wrapper around `connect()`, which includes something called `withLocalSelector()`. Can you clarify what that does, and what the other use cases are for wrapping up `connect()` ? I think I also see some other assorted selector functions being used as well.
- The couple reducer files I looked at are pretty large (several hundred LOC), and appear to be working with state that's nested 3-5 levels deep. A good portion of that appears to be normalized, per our recommendations. Have you run into any particular issues managing state that's nested that way? Have you considered any approaches for simplifying some of that logic, such as "reducer composition" (delegating the work of updating more nested state to their own reducer functions), or using an immutable update library such as Immer?
Also, the blog post talks a lot about the dataset sizes that you're dealing with. Any particular performance issues you've run into, and if so, how have you dealt with those?
Finally, any particular pain points you've experienced? Any things we can do to improve the docs (like better teaching certain patterns), or issues you'd like to see officially recommended solutions for?
If you'd like to chat about this in more detail, feel free to ping me @acemarke over in the Reactiflux chat channels on Discord.
Re: Introducing Kepler.gl, an Open-Source Geospatial Toolbox
#15This is pretty great. After banging my head over the weird state of python + GIS for the past month and a half, this feels very welcome. Also, is it down for anyone else? As soon as I tried uploading a file, it became unresponsive..
Re: Introducing Kepler.gl, an Open-Source Geospatial Toolbox
#16This is pretty great. After banging my head over the weird state of python + GIS for the past month and a half, this feels very welcome. Also, is it down for anyone else? As soon as I tried uploading a file, it became unresponsive..
Re: Introducing Kepler.gl, an Open-Source Geospatial Toolbox
#17Re: Introducing Kepler.gl, an Open-Source Geospatial Toolbox
#18Re: Introducing Kepler.gl, an Open-Source Geospatial Toolbox
#19This is pretty great. After banging my head over the weird state of python + GIS for the past month and a half, this feels very welcome. Also, is it down for anyone else? As soon as I tried uploading a file, it became unresponsive..
The demo looks like it's all client side. How big is your geojson?
Re: Introducing Kepler.gl, an Open-Source Geospatial Toolbox
#20Sweet, it's all built with React and Redux! And there's some _very_ hefty reducer logic in there. I'd love to chat with some of the Uber engineers who worked on this. I'm a Redux maintainer, and I'm always eager to hear feedback from people who are building serious applications with Redux.
That would make it me, I’m surprised people already start noticing the reducer logic in there. Better get the docs out soon :)