Desired Functions

We've decided to stop working on our demo system at this point and start thinking about the desired functions that can improve our system, because we are going to continue this project in next quarter and possibly into summer.

Here is the desired function at this point:

1. The Admin Page with Handling Ambiguities

Create the admin page that has an access to the database of the each parking lot status and handle the ambiguities that are created by computer vision detection system.

2. The Registered User with Caller ID

First, get the user registered by caller Id and store the preferred parking lot.
Then, give the user an option by pressing 0 to immediately access the information of the preferred parking lot.

3. SMS Base

Create an option to send a text message containing the parking information to the user who registered his or her cell phone number.

4. More Type of Spots

Find a way to handle V(visitor)spots and meter spaces later on.

5. Parking Lots Outside the Main Campus

Find a way to help the user who park outside the campus such as East Parking Lot.

6. GPS Information

Find a way to help the user who has no idea about where the specific parking lot is located. In the future, sending an information to the GPS in car will help a lot.

7. Improvement for Visitors

Now this system is intended for the experienced user who comes to UCSD everyday. The system will also have to account for the visitor who has never come to the UCSD.

8. iPhone Application

iPhone Application will help the user check out all of the nearest parking status.

Serge just suggested to do a literature review on academic or commercial systems for parking space vacancy alerting. It will help us brainstorming for the better functions.

Here are the links provided by Serge. Hopefully we can come up with more functions for the final presentation.

http://www.nytimes.com/2008/07/12/business/12newpark.html

http://www.sfgate.com/cgi-bin/article.cgi?f=/c/a/2008/04/14/MNTO104818.DTL

http://scialert.net/asci/ascidetail.php?doi=itj.0000.7667.7667&kw=

http://www.scialert.net/qredirect.php?doi=itj.0000.7665.7665&linkid=pdf

http://www.parkwhiz.com/about/releases/3-23-2007.php

http://www.edmunds.com/insideline/do/News/articleId=118824

http://www.mlive.com/news/ann-arbor/index.ssf/2009/01/use_your_cell_phone_parking_gee.html

Updated Demo

We've integrated JAVA code into the XML file by transforming JAVA code into JSP file. Now that JSP file is the simulator that create the random parking status. We also updated our demo system using the simulator.

Now the user can call 303 - 800 - 2532.

He or she can press 1 or say the name of the location to navigate through the menu.

Touch Tone

Press 1 for touch tone

"Press 1 for Warren, Press 2 for Revelle................."

Press 1 for Warren

"Press 1 for Calit2, 2 for Warren Lecture Hall....."

Press 1 for Calit2

"2A Spots 3B Spots and 5 S Spots are available..."

Then, go back to top menu

Voice Recog Menu

Say "Calit2" or "Warren Lecture Hall"

"5A Spots 7B Spots and 2 S Spots are available..."

Meeting with Ganz

We have been working on accessing a text file to get information of available A,B, and S spaces. After meeting with Ganz last wednesday, we modified our voiceXML menu to be as simple as possible and tried to write a JAVA code that could read the refreshed data. We first wrote a Java code that reads a simple table in a text file. Now its modified to read each A,B, and S spots from different places. Ganz is going to help integrating the JAVA code into XML menu we created. We had to spend much more time than expected, because we were not sure how to import other languaes or features into XML files. We trying to read each spot from each location by reading an information from matrix stored is multi dimensional array that looks like a figure below.

Goal for this week:

1. Create a demo system with complete menu that can access a text
file to find out number of available spots.
2. Try to optimize the menu and decide how to handle some exceptions