Use geoarrow-js from npm, not from the fork

[gadomski]

Right now we're on a fork:

stac-map/package.json

Line 44 in 960a61c

"@geoarrow/geoarrow-js": "github:smohiudd/geoarrow-js#feature/wkb",

We should use a released version, and if the functionality we need isn't in a released version, we should add it.

[sandrahoang686]

Okay took a look at this in the work on PR #241. The functionality existing on this current feature branch (wkb parsing) exists in this PR here.

Looks like its not yet merged in and i'm unsure of the blockers (cc @kylebarron & @smohiudd ?). But when pulling this branch down kyle/wkb and running an npm run build and then doing a yarn link locally with the work in my PR - it looks like it was able to run as expected. So I dont think we need any code changes other than waiting for that geoarrow PR to merge and then we should be able to update the version without having to do much code change ??

[kylebarron]

I think that PR is pretty far from being a generic WKB parser. It would need a bunch more tests, and it currently supports only a very limited set of geometry types. I think requirements to merge are at least supporting single-typed and single-dimension sequences of primitive geometries.

I don't have time to work on that in the near future I don't think. If the existing branch works for your use cases, you can vendor that code from the branch here.

Do you only need to support points? Or all types of WKB?

[gadomski]

I don't have time to work on that in the near future I don't think. If the existing branch works for your use cases, you can vendor that code from the branch here.

Yeah, we're just going straight from the commit right now, which is fine for prototype/demo purposes. No problem at all on not having the time, this isn't required for any client work ATM.

Do you only need to support points? Or all types of WKB?

For a generic parquet->duckdb viewer, we'd want all GeoJSON geometry types.