Syncing my work for the day. I'll pick this up tomorrow. Things left to do:
[ ] Sorting
[ ] Having a way to specify which data columns to pull out from the geojson properties object.
Anything else?
@mojodna on that last point, this is just naively taking the first geojson feature from filteredFeatures that has a properties property, and using the keys from that property to determine the table headers. I think it makes sense to pass some sort of configuration, at the very least determining which properties to pick. Otherwise for anything more complicated the table becomes useless.
If we want to avoid passing configuration, an alternative would some UI that lets you control which columns to show. Open to other suggestions as well.
Syncing my work for the day. I'll pick this up tomorrow. Things left to do:
Anything else?
@mojodna on that last point, this is just naively taking the first geojson feature from
filteredFeaturesthat has apropertiesproperty, and using the keys from that property to determine the table headers. I think it makes sense to pass some sort of configuration, at the very least determining which properties to pick. Otherwise for anything more complicated the table becomes useless.If we want to avoid passing configuration, an alternative would some UI that lets you control which columns to show. Open to other suggestions as well.