feat: LineString and MultiLineString types

[EvanHahn]

This adds support for LineString and MultiLineString geometry object types.

[github-actions]

The latest Buf updates on your PR. Results from workflow Buf CI / buf (pull_request).

Build	Format	Lint	Breaking	Updated (UTC)
✅ passed	✅ passed	✅ passed	✅ passed	Dec 9, 2024, 8:28 PM

[gmaclennan]

Looks good apart from a consistency question. For better-or-worse we omit lengths for Polygons and MultiPolygons when there is only one ring / polygon (see

comapeo-geometry/src/index.ts

Line 156 in f259310

lengths = lengths.length === 0 ? [rawCoords.length / 2] : lengths

). This was carried over from GeoBuf. I think it's probably over-optimization (and we did remove some of these optimizations from GeoBuf when we made this implementation, but we did not remove that one). However given that is how we encode/decode Polygon and MultiPolygon, I think maybe for consistency we should do the same for MultiLine (it's not necessary for Line). Does that make sense? Open to push back!

[EvanHahn]

I think maybe for consistency we should do the same for MultiLine (it's not necessary for Line). Does that make sense? Open to push back!

Done in e8c1dc1. Tried to match what Geobuf does in this case. I also added some additional fixtures in cab67c0 to improve my confidence that this works.