Libraries and Dependencies
AKA What's keeping this thing afloat?
Last updated
Was this helpful?
AKA What's keeping this thing afloat?
Last updated
Was this helpful?
WebGeoDa uses , a server-side rendering JavaScript framework by Vercel.
Our geospatial engine (and namesake) is Dr Xun Li and Dr Luc Anselin's , a WebAssembly-based geospatial analysis module. By default, it's accessed in a WebWorker, aka a separate thread, meaning your interface is free for interaction while Geospatial analysis is going on.
By default, mapping is done using with layered on top. In the future, additional map components may be available.
In the works 👀
State management is done with /. Redux is a classic, and a good fit here given the frequent state updates, partial state access, and potentially high cost of re-rendering the map. Our built-in actions use just a reducer and inline-actions, rather than an additional actions file:
There are numerous UI toolkits available in the React ecosystem, like , , , and others.
Our provided UI toolkit focuses on simple, vanilla HTML and CSS focused components and high accessibility. So, we base our interactive components on , a highly accessible foundation for React-based design systems and , a simple CSS-based column layout tool.
We use to call and manage our WebWorkers. It's lovely.