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

Questions to be addressed #1

Open
jordansread opened this issue Sep 19, 2017 · 3 comments
Open

Questions to be addressed #1

jordansread opened this issue Sep 19, 2017 · 3 comments

Comments

@jordansread
Copy link

jordansread commented Sep 19, 2017

  1. Do we have adequate flood stage info? If not, can we use > 90% (and explain that in plain english) we do
  2. what geographic info are we including for reference? big cities/capital, county equivalent
  3. use custom (higher res) PR shapefile? where from? give appropriate credit
  4. make sure we link to the appropriate WSC in the text
  5. precip data is more raw than NOAA stage IV. What QAQC (if any) do we apply?
  6. which "experiences" are supported? Possibilities: landscape, portrait, portrait-mobile, ...others?
  7. how to animate scenes w/o dogging the mobile browser? As simple as using requestAnimationFrame instead of setTimeout for animation in JS? Do we need to animate raster instead of svg for precip?
  8. export a high-value (and high-res) gif as product, or based on screen capture?
@jiwalker-usgs
Copy link
Contributor

I looked at requestAnimationFrame over the weekend, it is definitely doable to switch to that, it may result in missing some frames but will provide a constant speed across devices.

@mbucknell
Copy link

Other benefits of requestAnimationFrame it stops when the user switches to a different tab, so won't dog the device's CPU when not visible.

@dblodgett-usgs
Copy link
Contributor

dblodgett-usgs commented Sep 19, 2017

  1. We DO have flood stage data. "Action", "Flood", "Moderate", and "Major".
  2. I found precip that is the NOAA Stage IV, not GDP accessible, but it'll work.

jordansread pushed a commit that referenced this issue Sep 21, 2017
adding gage_nils indicator for blocking out nil values
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants