usgs-wim / nwis-mapper Goto Github PK

View Code? Open in Web Editor NEW

4.0 6.0 1.0 60.66 MB

USGS NWIS Mapper (Mapper interface for USGS NWIS Waterdata)

Home Page: https://maps.waterdata.usgs.gov

License: Other

Python 9.09% HTML 62.46% JavaScript 17.89% CSS 10.07% Shell 0.24% Roff 0.25%

usgs nwis mapper waterdata

nwis-mapper's Introduction

Server setup

1. Deploy instance on AWS

current system specs

m3.large
8GB attached volume
ubuntu server 14.04 LTS

2. Set up server

copy server setup script from github

wget https://raw.githubusercontent.com/USGS-WiM/nwis-mapper/master/server-config/server-setup.sh --no-check-certificate

run server setup script

sudo sh server-setup.sh

copy keys for SSL (HTTPS)

sudo cp [path to key]/server.crt /etc/ssl/certs/server.crt
sudo cp [path to key]/server.key /etc/ssl/private/server.key
sudo cp [path to key]/DigiCertCA.crt /etc/ssl/certs/DigiCertCA.crt

restart apache

sudo service apache2 restart

the nwis mapper application should now be running @ localhost

Generate new NWIS mapper tile cache

required software

ESRI ArcGIS Desktop ~10.3.1
Python 2.7
Python Pillow image library
AWS CLI

1. Run script to pull NWIS sites from USGS waterservices (tile-creation/1_getNWISSites.py)

python generateTileCache.py

takes about 3 hours minutes to run
queries NWIS site service for sites, adds them to a fileGDB
fileGDB feature classes are referenced within MXDs for each site type
this is a wrapper script that generates an ESRI tile cache, cleans it up then converts to TMS tiles
output can be uploaded directly to s3

2. Upload to amazon S3 (tile-creation/3_updateS3Bucket.py)

check to make sure paths are correct

python updateS3Bucket.py

takes about 8 minutes to run
loops over each folder in tile cache location, recursively deletes from s3 bucket then re-uploads new cache

nwis-mapper's People

Contributors

Stargazers

Watchers

Forkers

dkyancey

nwis-mapper's Issues

"Active/Inactive" designations for sites

The Active/Inactive designated for Water Data information is unreliable. For users that view the NWIS mapper by viewing the results of a search, create an alert that says:

"Search results in NWIS mapper are using a deprecated active/inactive designation method. To view this area with the current active/inactive information click here."

Show this alert upon initial load of the interface from a search.
"click here" will open the NWIS mapper in a new tab with the extent matching the one they are navigating from. If possible, pass the applicable layers as well so it's immediately clear which sites are active/inactive.

Old bookmarked “show sites on map” URLs broke with HTTPS switch

Mapper reports “there was a problem with the request.”
Example:

http://maps.waterdata.usgs.gov/mapper/nwisquery.html?URL=http://waterdata.usgs.gov/usa/nwis/measurements?huc2_cd=04&huc2_cd=07&huc2_cd=09&format=sitefile_output&sort_key=site_no&sitefile_output_format=xml&column_name=agency_cd&column_name=site_no&column_name=station_nm&begin_date=2017-03-23&end_date=2017-04-06&set_logscale_y=1&channel_html_info=0&date_format=YYYY-MM-DD&channel_rdb_info=0&rdb_compression=file&list_of_search_criteria=huc2_cd&column_name=site_tp_cd&column_name=dec_lat_va&column_name=dec_long_va&column_name=agency_use_cd

Changing the embedded UTL=http to URL=https makes this work just fine.

Search by site number broken in Water Alert interface

Issue traced to different headers passed in the two different interfaces (NWIS Mapper and NWIS Mapper for Water Alert).

NWIS Mapper Vulnerabilities 2018712

From Aaron:

USGS ITSOT scanned our applications today and found a few vulnerabilities. For the most part I have remediated them, except for the following which is better handled by the development team:
broken links
This is just an "informational" item and not a true vulnerability, but since the list of broken links is quite long I thought you might want to clean it up.

WMA Analytics adjustments

Update client code for both clients
Ensure vizlab has read access
submit pull request with updates

WMA suggests combining the Analytics IDs for NWIS Mapper and NWIS Mapper-Water Alert. Details below:

if there are multiple pieces to a project, they could all be under a single ID (UA-XXXXX), but then filtered views could be created for each piece based on the URLs, in addition to the default view that includes everything. That way they can easily be looked at together or separately. Views are what the analytics dashboard keys on.

You can just make a pull request with changes to this yaml file: https://github.com/USGS-VIZLAB/internal-analytics/blob/master/data/gaTable.yaml#L779 with whatever new IDs and views the dashboard should use for those applications. Also, make sure our service account ([email protected]) has read access to the new views.

Implement http to https redirect

Large Screens Bounding Box Queries

On large displays, a user (from a zoom level too large) can create a bounding box that 'breaks' the water services query.

When Water Services rejects the too-large query, show an alert to the user that says:

"Please zoom in or select a smaller area."