Feedback to CHSRA

Many thanks to all those who contributed to the post Suggestions for the CHSRA Web Site over the Easter weekend. Below is my summary of the feedback, plus some suggestions of my own. An unsolicited copy has been sent to CHSRA.

1. The Authority should think of its web site as the primary means of detailed communication with the general public. Print, radio and TV media appearances should be used to plug the URL and increase traffic.
   
2. In its current form, the site does little to support the current phase of the project, i.e. securing funding while implementing multiple simultaneous project-level EIR/EIS processes. The Authority needs to move beyond advocacy of the general idea of HSR to documentation of specific business processes.
   
3. Overall project status: milestones achieved, upcoming milestones, timeline (at high level). Special focus on funding, including e.g. list of components expected to be eligible for federal stimulus funding.
   
4. Count-down to start of construction and start of operations. Count-up of miles of tracks laid, funding secured and dollars spent to date.
   
5. Revamp of library section: much smaller documents (= faster downloads) with embedded hyperlinks/references. Design for web, not hardcopy. Slice and dice existing PDF tomes to support project-level EIR/EIS and fundraising. Relegate versions that include discussions of options already discarded to an archive.
   
6. Each project-level EIR/EIS process should have its own section on the web site. Desired resources are:
   
   
   
   • info on consulting firm hired for the segment
     
   • process status: milestones achieved, upcoming milestones, timeline (at segment level)
     
   • timely announcements of scoping meetings
     
   • explanation of project-level EIR/EIS process in general (link)
     
   • CHSRA's obligations regarding comments received (link)
     
   • options for how to comment (link unless segment-specific)
     
   • summary of reasons why segment is part of the preferred route
     
   • geographic scope of the segment
     
   • description of right of way ownership & easements (+ link to docs)
     
   • description of other rail services in or near ROW, associated constraints
     
   • description and scale drawings (cross-section + elevation with human figures/other structures for reference) of implementation used for cost estimation
     
   • summary of reasons for choosing that implementation as a starting point
     
   • electronic copies of comments already received during the comment period
     
   
   
7. Glossary explaining technical terms like "retained fill", "embankment", "cut and fill", "aerial" etc. to the layman using drawings (cross-sections, elevations with human figure for scale reference). General discussion of pros and cons during and after construction (esp. underground options). Cost per mile for relevant precedents.
   
8. Scientific sound recordings of actual HSR trains at various distances (up to 1/2 mile) and speeds (up to 200mph), for various track elevations, in open countryside vs. urban area, with and without noise mitigation etc.
   
9. Addition of realistic soundscapes (incl. other sources like road traffic) to NC3D animations
   
10. Reference material on/links to: grade crossing safety, hardened vs. separated grade crossings, bells & horns, diesel locomotive emissions, overhead catenary system parameters and safety, relevant noise & vibration metrics
    
11. Reference material on the concepts of eminent domain, reverse condemnation. Articulation of CHSRA policy incl. stage/conditions in project-level EIR/EIS process that will prompt a decision on this.
    
12. Summary of project history to date, archive of superseded documents (clearly marked as such on background of each page)
    
13. Avoid the use of HTML frames and Javascript links to ensure all documents, videos etc. can be referenced via an easily obtained permanent URL. Put link to Google Map of route at top of routes page, enable references that preserve pan and zoom values.
    
14. Consider using Google Sketchup for 3D sketches of possible implementations. Publish recurring model elements (tracks, trains, OCS, earthworks/concrete structures, generic houses, generic cars & trucks, generic trees, surface textures incl. climbing plants etc.)