Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This feature add hurricane track layers support. I am not aware of any issues regarding this feature, except as listed in issue #71 (as requested by b.blanton).
The new code in files in utils/hurricane (track.js, config.js, and time.js) were originally stolen from the website that uses the MetGet api. The MetGet api is used to retrieve the hurricane track data in GeoJson format. It returns features for the cone of uncertainty, the hurricane track line, and the advisory point locations.
This feature uses a new state variable in map-context called 'hurricaneTrackLayers'. The updates touched a few components, including the new StormLayers component and the ControlPanel and HurricaneList tray.
When a tropical storm adcirc layer is added to the map, the associated hurricane track layers are added automatically and they are removed when the associated adcirc layers are removed.
Please note that we will not be able to actually test this with adcirc storm layers until we can display them with the layer filtering form that Phil is working on. I have tested this feature thus far by faking with synoptic type layers