Street Sweeper Tracker Site

[harmanTheCarMan]

Description

As anyone who has a car and parks on the street, it is terrible to receive a parking ticket due to street sweeping times. Especially since the street sweeper may or may not show up but the traffic ticket person definitely will make it.

Basic use flow:

1. Type address (or use current location using GPS)
2. Press enter
3. Show list of 10 nearby streets with sweeping times
4. Update map with today's and tomorrow's street sweeping streets highlighted in red on map
5. Notify whether or not it is clear to park on current street.
6. Show nearby areas where street sweeping is not happening soon (within next 24 hours)
7. Show parking garages or other unrestricted forms of parking nearby to park easily

   Context

This goal helps the public avoid parking in street sweeping areas and search for better non-restricted parking spaces nearby to park instead.

Specifications

• [ ] Be able to search for an address or use my current location to show street sweeping times
• [ ] Show list of 10 nearby streets with sweeping times
• [ ] Notify whether or not it is clear to park on current street
• [ ] Show nearby street where sweeping is not happening within next 24 hours in GREEN on map
• [ ] Show nearby street where sweeping is happening within next 24 hours in RED on map
• [ ] Show parking garages or other unrestricted forms of parking nearby to park easily
• [ ] Mobile friendly (usable + responsive)
• [ ] Save favorite locations to track (Home, work,...)

  Quality Rubric

• [ ] Tested - All specs passing
• [ ] Documented - Contains instructions for a user to set up app locally or how to use website
• [ ] Functional - Project runs in localhost or on heroku
• [ ] Structured - Directory structure allows new developers to quickly find and add files
• [ ] Clearly Named - Functions, variables, files, CSS classes and ids
• [ ] Abstracted - Small, single-responsibility functions leveraged for encapsulation & reusability
• [ ] Git Logged - Readable and clean with clear, complete, professional commit messages
• [ ] Not Commented - Unless truly necessary. No dead code, console.logs, fits/xits

  Stack

• [ ] ES6 JS for writing overall app
• [ ] Pug to easily write html
• [ ] Node is a JS runtime environment inside of the command line.
• [ ] Nodemon to reload server as soon as any code changes occur.
• [ ] Google Maps API or another navigation tool to pin streets and info bubbles and put up map as background
• [ ] Spot Hero, Parkmobile or other Parking App data (if API or data available) to easily find and reserve paid parking spots
• [ ] Bootstrap to make webpage mobile responsive
• [ ] TDD ex: mocha or jasmine
• [ ] Heroku for hosting the app
• [ ] Perhaps use Open Oakland data for information about streets in Oakland, CA home of the original Learner's Guild.

  Required

Do not remove these specs - they are required for all goals.

• [ ] The artifact produced is properly licensed, preferably with the MIT license.

---

This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.

[tannerwelsh]

@harmanisdeep nice idea! This would be a lot of fun to work on.

To help people get a better sense of what the finished product would look like, could you add some content to the description about what information would be available? You could even structure it as a set of steps:

1. Type address
2. Press enter
3. Show list of 10 nearby streets with sweeping times
4. Update map with today's street sweeping streets highlighted

Or something along those lines.

[harmanTheCarMan]

@tannerwelsh Thanks for your comment, I updated the goal. Take a look and see if I implemented your suggestion well. 👍

[shereefb]

@harmanisdeep your specs don't match your description. For example, there's no spec for finding parking spaces.

Also, give more information for reviewers to figure out what quality look like. Is it about test coverage? Is it about not using frameworks? Is it about the UI look and feel?

For example, you can create a quality rubric like this: UI/UX: 100 Test Coverage: 100 Good file organization: 50 Good variable and function names: 50 Code is object oriented: 75

I

[tannerwelsh]

Made some minor edits, otherwise this is good to go. Removing draft label.

[harmanTheCarMan]

@tannerwelsh: edited further with links and all kinds of fun. How's it looking now? I think this goal is all ready for voting.

@shereefb: I added a quality rubric, not sure percentages to assign to each quality spec. though.

[tannerwelsh]

Looks good @harmanlearns - thanks!