Skyler Young

I agree with @MikeThacker1, this makes sense, but also raises some questions about the nature of taxonomies. Coming from the 211 space, I naturally want to reserve `taxonomy_term` for taxonomies...

Two related lessons my team has learned from client (211) data sets: 1. Aside from the `status` method described above, they also have a "weight" field. In the data is...

I would particularly be in favor of adding GeoJSON support to `service_area`, so that we explicitly expect and know where to store shape data.

I agree that `extent` is a necessary supplement to `uri`. In Hawaii, for example, the service areas for their 211 are quite intuitively organized according to custom shapes that don't...

It's a small thing, but can we use more descriptive key than `extent`? This is always`geospatial` `shape` data is it not? On Tue, Feb 22, 2022 at 10:29 AM Skyler...

It's not really worth messing up your systems, I think. I'll recant my suggestion to rename `extent`. Yes, those darned GeoJSON files can get huge. A great deal of my...

@MikeThacker1 @devinbalkind This issue took on a new dimension for me today. When using DBT to transform data into HSDS in BigQuery, BigQuery started nesting the entire `service_area` table inside...

Hi Mike, Calling this out because it's such a perfect example: ...you need a way of knowing if the URI supports the content type you want. That's exactly the type...

Just noticed these same issues when defining the schema for one of our apps. @devinbalkind can we add this to 2.1, or is it already in there?

I just left a comment along these lines here: https://github.com/openreferral/specification/issues/221 In our search engine for Washington 211, we added an `emergency_info` field that gets displayed at the top of records....