The problem
Fifty-four plants are legally designated noxious weeds in Nevada. They crowd out forage, drink the water, feed wildfire and push out wildlife. The program's records, its project history and its species knowledge lived in separate places, and none of them were somewhere a rancher, a county crew or a legislator could simply open.
What we built
One site with four doors, three for everyone and one for partners.
- What we're fighting. Every listed species with photos, identification tips and a live map of where it has been reported, with Nevada's Category A, B and C classification explained. Report a sighting in two clicks.
- Why it matters. The story of what is at risk, told with the real data: water, farms and ranches, wildfire, wildlife, recreation, and the cost of waiting.
- How Nevada is winning. Federally and state-funded weed projects across the state, with acres treated, who paid for what, and results on the map.
- Partner dashboard. Behind a password, guided lenses for the people doing the management: spread corridors, coordination gaps, water at risk, drought and habitat.
How it works
Live sightings, no copy of the data
The weed map reads the EDDMapS feature service straight from the browser, so what a visitor sees is what the program's records say right now. Nothing has to be re-exported when the data changes.
Species pages that need no JavaScript to read
Every species profile is pre-rendered as plain HTML from the program's own spreadsheet, so the staff who know the plants edit a workbook and the site rebuilds from it. A profile loads instantly and reads on a phone at the edge of a field.
Static, so there is nothing to patch
The whole site is a folder of static files on a plain web host: no server code, no database, no content system to keep updated. We host it, with the certificate, backups and monitoring handled.
What it changed
The public can identify a weed, see where it has been found and understand why it matters without a login or a licence. Partners get the analysis views that used to take a GIS analyst to produce, in a workspace built around the questions they actually ask.