Graphhopper web has been extended on the client and the server side as follows:

1. on the client side, A dropdown listbox has been added to the webpage that allows the user to select preferred weighting; i.e fastest, shortest.
 2. on the server side, Based on available sensor data for each city, appropriate config file is read (by checking the opened city map). This information is sent to the client, and the weighting dropdown list is amended accordingly with available sensors weighting options; e.g. least_noisy
3. On the client side, the URL query is amended to include weighting (its value is taken from the value selected by the user), and vehicle, which is read from config.properties.
4. On the client side, If the user entered the query directly from the URL, e.g. (http://localhost:9000/?point=Tallaght&point=Blackrock&vehicle=car&weighting=shortest&locale=en-US), the params values from the query are propagated to corresponding DOM elements, and routing is done!