Context Sensitive Solutions (CSS) is a theoretical and practical approach to transportation decision-making and design that takes into consideration the communities and lands which streets, roads, and highways pass through ("the context").
| Property | Value |
| dbpedia-owl:thumbnail
| |
| dbpprop:abstract
|
- Context Sensitive Solutions (CSS) is a theoretical and practical approach to transportation decision-making and design that takes into consideration the communities and lands which streets, roads, and highways pass through ("the context"). The term is closely related to but distinguishable from Context Sensitive Design in that it asserts that all decisions in transportation planning, project development, operations and maintenance should be responsive to the context in which these activities occur, not simply the design process. CSS seeks to balance the need to move vehicles efficiently and safely with other desirable outcomes, including historic preservation, environmental sustainability, and the creation of vital public spaces. In transit projects, CSS generally refers to context sensitive planning, design and development around transit stations, also known as Transit Oriented Development (TOD).
|
| dbpprop:hasPhotoCollection
| |
| dbpprop:quotationProperty
|
- As agreed upon by participants of the Thinking Beyond the Pavement Conference, 1998
- The CSS Process: Characteristics of the Process That Yield Excellence
"The Characteristics of the Process that will Yield Excellence in Transportation Design" are:
Communication with all stakeholders is open, honest, early, and continuous.
A multidisciplinary team is established early, with disciplines based on the needs of the specific project, and with the inclusion of the public.
A full range of stakeholders is involved with transportation officials in the scoping phase (the period before design is begun when the scope of the project is agreed upon). The purposes of the project are clearly defined, and consensus on the scope is forged before proceeding.
The highway development process is tailored to meet the circumstances. This process should examine multiple alternatives that will result in a consensus of approach methods.
A commitment to the process from top agency officials and local leaders is secured.
The public involvement process, which includes informal meetings, is tailored to the project.
The landscape, the community, and valued resources are understood before engineering design is started. A full range of tools for communication about project alternatives is used (e.g., visualization).
- The CSS Product: Qualities of Excellence in Transportation Design
The "Qualities that Characterize Excellence in Transportation Design" - that is, of the physical end product of the CSS process – are:
The project satisfies the purpose and needs as agreed to by a full range of stakeholders.
This agreement is forged in the earliest phase of the project and amended as warranted as the project develops.
The project is a safe facility for both the user and the community.
The project is in harmony with the community, and it preserves environmental, scenic, aesthetic, historic, and natural resource values of the area, i.e., exhibits context sensitive design.
The project exceeds the expectations of both designers and stakeholders and achieves a level of excellence in people's minds.
The project involves efficient and effective use of the resources (time, budget, community) of all involved parties.
The project is designed and built with minimal disruption to the community.
The project is seen as having added lasting value to the community.
|
| dbpprop:reference
| |
| dbpprop:wikiPageUsesTemplate
| |
| rdf:type
| |
| rdfs:comment
|
- Context Sensitive Solutions (CSS) is a theoretical and practical approach to transportation decision-making and design that takes into consideration the communities and lands which streets, roads, and highways pass through ("the context").
|
| rdfs:label
|
- Context Sensitive Solutions
|
| owl:sameAs
| |
| skos:subject
| |
| foaf:depiction
| |
| foaf:page
| |
| is dbpprop:disambiguates
of | |
| is dbpprop:redirect
of | |
| is owl:sameAs
of | |