Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support Earthquake-Place searches #276

Open
ThomasThelen opened this issue May 24, 2022 · 0 comments
Open

Support Earthquake-Place searches #276

ThomasThelen opened this issue May 24, 2022 · 0 comments
Assignees
Labels
bug Something isn't working
Milestone

Comments

@ThomasThelen
Copy link
Member

ThomasThelen commented May 24, 2022

Right now, earthquakes have two pieces of geographic information:

  1. A point geometry (via hasGeometry)
  2. A connection to the country that it took place in (via locatedIn)

At the moment, we don't support searching for earthquakes within any of our place facets (ZIP, FIPS, National Weather Zone, County, etc). I think part of the reason for this is that we never defined how the facets should work when earthquakes are selected.

There's a slight differentiation in the semantics between the earthquake's geometry and other hazards like fires. In the case of earthquakes, the geometry specifies the starting location and there isn't additional information about where it occurred (other than the country). Fires on the other hand have geometries that specify the geographic extent.

I think that we should make the place facets available to this hazard type by using the point geometry to locate earthquakes in a given area.

**Example 1 **

  1. User clicks the Earthquake facet
  2. User enters 93105 as a zip code
  3. User sees all earthquakes that originated from 93105

**Example 2 **

  1. User clicks the Earthquake facet
  2. User enters 01 FIPS code
  3. User doesn't see any earthquakes because none started in that FIPS area-even though some earthquakes may have effected it
@ThomasThelen ThomasThelen added this to the 2.0.1 milestone Dec 3, 2022
@ThomasThelen ThomasThelen modified the milestones: 2.0.1, 2.0.2, 2.0.3 Jun 5, 2023
@ThomasThelen ThomasThelen added the bug Something isn't working label Jun 13, 2023
@ThomasThelen ThomasThelen self-assigned this Jun 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants