Symbioquine

> Would the more recent WFS/OGC help with querying & returning certain attributes along with the GeoJSON as well? That is one of the gripes I have about our current...

*I've edited this issue's title/comments `%s/sidebar/side panel/` for consistency with the naming in the code/readme.*

I'm not totally convinced it it would be preferable, but in theory another way this could work would be allowing both/multiple polygons to be selected with the edit tool and...

Thanks for opening this @jgaehring! This stuff should definitely work more smoothly - or at the very least be clear about which use-cases are supported. `npm run dev` from the...

> I believe #117 made this possible, and `window.farmOS` is only used when `main.js` gets included (correct me if I'm wrong @symbioquine!)... That's definitely the intention... though I think it...

I'm just catching up here... > FYI, I'm getting the same issue with `MapInstanceManager`. Here's what I tried: > > ```js > import MapInstanceManager from '@farmos.org/farmos-map'; > import geotraceCtrl from...

I'm not sure it's great for them to have the same name (the code directory and the css file), but it is also surprising behavior IMHO for the import to...

> inferring `../../styles.js` from `../../styles` Actually, it's inferring `../../styles/index.js`. > it would break, in accordance w/ the ECMAScript spec that all modern implementations follow) How imports are resolved isn't specified...

To be clear, I'm not necessarily arguing against the strategy of transpiling the farmOS-map source code to ESM/CJS versions. However, I do think that there are some details we should...

It's worth noting that I've addressed part of this issue with the [farmOS-map 2.x changes](https://github.com/farmOS/farmOS-map/issues/115) to introduce a `namedBehaviors` namespace where behaviors can be registered without automatically adding them to...