What is on the client, what is on the server

[tordans]

Hey, I read the docs and examples but I am still not quite sure which parts of this project are client side and which are server side…

I am hoping that this might all be client side with a model that is downloaded. Is that the case?

[sabman]

Hi @tordans thanks for trying out. Yes that's correct it runs client side. However there's nothing stopping you using it server-side as there's no particular dependency on the DOM. Checkout the quick-start see below. For examples of without ReactJS checkout the tests they have examples that run via the CLI.

Client Side:

curl -L https://github.com/decision-labs/geoai.js/archive/refs/heads/main.zip -o repo.zip
unzip repo.zip "geoai.js-main/examples/01-quickstart/*"
mkdir -p examples
mv geoai.js-main/examples/01-quickstart examples/
rm -rf geoai.js-main repo.zip

cd examples/01-quickstart
pnpm i
pnpm start

PS. Feel free to ping me if there's something specific you are hoping to achieve we are keen to learn how people want to use the lib. https://cal.com/geobase

[sabman]

I just did some more testing seems the we don't have a commonjs module in our build output. We need to still add that, so I think the backend imports via require maybe broken in the 1.0.0-rc.4 release. We'll fix that shortly. We need to add this back to our package.json

      "require": "./geoai.cjs"

[tordans]

Client only is great. For now I am just looking to understand the potential, especially for OSM. Something client only, integrated in one of the mobile editors would be very interesting. However the use case for mapping is still now fleshed out in terms of quality and workflow. Maybe the solar panel would be a use case…

[sabman]

Agree! Added a use case discussion too #109