Update README.md

README.md

@@ -18,7 +18,7 @@
 * If you are answering a question that requires persistence, your choices in order of likelihood that they will run for the assessor, are: a complete docker[-compose] or vagrant setup, a flat file, a sqlite database, a postgres or mongodb connection string you provide the facility to easily configure and setup scripts for (along with documentation), anything else (extremely high risk the assessor will not be able to run it).
 
 ## Level of Effort Guidelines:
-* Each problem is designed to take an experienced developer around an hour to prepare a program, tests, and setup documentation/assets; however, everyone is different and your mileage may vary.
+* Each problem is designed to take an experienced developer around 1-2 hours to prepare a program, tests, and setup documentation/assets; however, everyone is different and your mileage may vary.
 * Our team fully embraces open source technologies and frameworks for a number of reasons, not the least of which is that you can solve problems faster with them. We highly recommend you use appropriate frameworks wherever possible to solve and deploy solutions to your selected problems.
 * Some problems may have specific presentation requirements, such as a frontend interface in a web browser. If the presentation requirements do not match your skillset and desired role, pick a different question. If there are no specific presentation requirements you can discern, a command line or RESTful API interface is likely a perfectly acceptable solution (so long as you include documentation on how to use it).
 * Assume any text or strings mentioned may contain unicode characters.
@@ -31,7 +31,7 @@ Software development at mySidewalk is a collaborative endeavor and engineers her
 ## Problems:
 * The user has a file that is made up of short (less than 1000 character) strings, each on a different line (assume any common character or character combination that means a newline to someone might be used interchangeably in this file). Most of these strings will be preceded by numbers, i.e. “2 Steaks”, “10 Chicken Wings”, “343GuiltySparks”. Accept the file from the user and return them a file with the same items sorted first by the numeric value of any leading number (2 < 10 < 343) and then alphabetically for the rest of the string.
 * The user wants a responsive web interface to see a particular comment from the mySidewalk engagement comments API. Load the comment with ID 100 (https://mysidewalk.com/api/engagement/v1/comments/100.json) from the API, redirect the window’s location to a path that represents a human friendly portion of the comment, and display the comment in a device response and visually pleasing manner.
-* [COMING SOON] The user wants to visualize the following geojson layers [urls] together on a map along with a chart of [attribute we want to visualize] in an interactive manner.
+* The user wants to visualize the following geojson layers ([1](https://github.com/mysidewalk/interview/blob/master/assets/kc-neighborhoods.json), [2](https://github.com/mysidewalk/interview/blob/master/assets/kc-tracts.json)) together on a map along with a chart of their commuter population attributes in an interactive manner.
 * The user wishes to securely store secret messages for later reading. The user needs to create an account consisting of at least a username and password (the password should be stored securely; not, for example, in plaintext or a reversible hash). After authenticating the user can submit a secret message (large amount of text to be stored securely; not, for example, in plaintext but by necessity in an encryption / hash that is reversible for later display) or see the most recently submitted secret message in plaintext.
 * The user wishes to submit “reviews” consisting of a location/business name and a text body tied to a location which may be either a plaintext address or a geographic point described by a latitude and longitude pair (whatever projection you prefer). If the “review” is submitted using an address, geocode this address to a point. Persist these “reviews” and allow the user to submit a bounding which for which to return/display all current “reviews” which fall within this bounding box. Your solution should be able to return results in a timely manner even when querying thousands of reviews.