Make API compliant with NSS standard

[GovInTrenches]

(LOWER PRIORITY - POST EVENT)

The Red Cross uses a National Shelter System that's fairly common - however the data standard is fairly huge. I don't know if there's a way to make the API 100% compliant but where we can we should try to match the standard.

Here's the guide https://nss.communityos.org/local/os125/posting_area//documents/NSS%20Documents%20v%203.1/NSS_UserGuide.pdf

[greggish]

So, AFAIK the NSS is a closed system. I think this is a manual for data entry within NSS, not for structuring data for exchange. NSS only seems to output shelter information plain-text, although i'm told their data also goes to ESRI.

Open Referral's format is intended to enable interoperability between systems like this, the Shelter API, 2-1-1, etc.

(During/after Irma, we did connect with the Harvey Needs team, who seemed to agree that the API should evolve to adopt this schema. Though I don't think they continued to work on the project in the end.)

We're now talking with folks at the Red Cross about whether this can be useful to them in their next cycle of development; they seemed pleased to hear our protocol exists. Relatedly, the other disaster response system managed by the Red Cross is the Coordinated Assistance Network, and the vendor for that product also has indicated their interest in adopting Open Referral's API protocols.

If we're able to get open protocol adoption on the agenda for the next iteration of this tool, it could help facilitate all of the similar movement above. I'd be happy to answer any questions.

[miklb]

We are now set up to import directly from the FEMAOpenShelters feed provided by Red Cross. Is that the same endpont @GovInTrenches ?

See #55

[miklb]

I think this dovetails into the discussion going on in Slack. Do we shift to adjust our schema and API to be more compatible with upstream like the FEMAOpenShelters from Red Cross.