Programming Team Report

Transcription

1 Programming Team Report George Carpeni, Chetan Naratain, James Tate, Will Peng (and John Valentino) 1

2 1 Summary of Process 1.1 Project Process Figure 1: Project Process Schematic 2

3 1. Students look up and find county data including schools, transportation stations, businesses, entertainment. Students estimate patrons per day and revenue depending on type of placemark and obtain corresponding lattitutes and longitutes (e.g. school, residence, business) Students submit county data in specified CSV format (see appendix) 2. The programming team checks the data for duplicated entries, proper geocodes, and correct formatting The programming team manipulates the data with excel macros to convert it to a database format The programming team loads the data into a MySQL database The programming team converts the data into KML format with a python script 3. Students determine optimal location of stations by looking at tripends served Students place interchanges and guide-way to satisfy trip demands 4. Students compute trip distributions Students assess economic feasibility of network 5. Students write final report 3

4 *Over the course of these steps, especially as the county groups do their tasks, there is a feedback loop where the county groups find glitches in the tools and the programming group 4

5 2 Features and Their Details 2.1 Last year s features Displayed county placemarks from KML file on a per-county basis Could add/delete Stations Interchanges Shapepoints Could compute guideway lengths as well as the number of stations and interchanges Included some functions for computing productions and attractions and population density information, but these functions referred to nonexistent code and were subsequently modified or removed. 2.2 Added and Changed Features 1. Data Input Standardized the data input format by giving students a format specification Created a python script and an excel macro to convert the input data to Google KML and MySQL data tables, respectively. 5

6 New Placemark types, graphics, and data fields. Education, Recreation, Work, Home, and Transportation as main types. Subtype capability for each field. (e.g. Work could be factory, finance, shopping) Ability to track additional distinct trip types for each placemark. Default type for each field. (e.g. Home has residents, etc.) Secondary Types (e.g. Distinguish between faculty and students in a school) Patrons per day for all types of locations. 2. Real-Time Trip Calculation Added the ability for users to see the number of trips served within a quarter mile square, which was a vital part of being able to adequately construct a network. 3. Station Trip Distributions Calculation Added a server-side program to compute the number of trips served by each independent station in the network. It also outputs the specific placemark locations served by each stations, the total 6

7 number of trips served by the network, and the total number of trips possible (by each type) for the county. 4. Custom Station Loading and Saving In addition to being able to load and save a default station file for each county, users are able to define custom station files so that they can build multiple custom networks, save them in separate files, and compute trip information for each separate network. 5. Interface Improved aesthetic presentation There is a new design logo for the web app The presentation is more intuitive New icons for Add a station Add an interchange Add a shapepoint Add a line A tooltip below the icons guide the user, for example telling them what to do in order to add a line, and the icons add visual cues to make the process of building a PRT network as streamlined as possible for the user. 7

8 Improved map display The size of the map is now optimized to fit within standardsized 1024x768 screen resolution. Will help the end user from running into scrolling issues when adding stations and other functions. The map now has a static position with respect to the rest of the page when the user scrolls. This allows the user to scroll to use different functions and view trip information without having the page refresh the Google Earth map (which can be time- and processor cycle- consuming, especially given the large amount of data being handled by the app) 8

9 3 Functional Diagram of System Figure 2: Project Process Schematic 1. Student Input Data CSV Files: Each student submits a sample file data file, generated in excel subject to a format (See Appendix A.) 9

10 2. Data Objects Placemark KML - A KML file storing the graphical representation of placemarks to be used by the google earth plugin. (There is one placemark KML file per county). Placemark Database - An SQL database that stores the latitude, longitude, type, and description of each placemark. SQL is preferred to files for faster access to large numbers of records, particularly in instances where the trip data has to be calculated multiple times per second, such as in the case of the real-time trip update display. Station KML - KML files containing stations generated by members of each county using the placemark tools and written data. 3. Server Side Programs TripCounter - Given latitude and longitude coordinates from the mouse, this program returns the number of trips that would be served by a station in that area. StationStats - Given data from the client interface, this program leads to a description of each station in the network, explains which placemarks it serves, and computes overall trip statistics for the network by type. Save.PHP - Writes submitted station data to a file on the server. 10

11 4. Client Side Functions Adding Functions - AddStation(); AddInterchange(); AddShapepoint(); AddLine() SaveStations() - Uses an HTTP POST request to submit the station data in memory to SAVE.PHP so that it can be written to a file on the server side. LoadStations() - Loads station data from the default files for a particular station, based on the station selected in a drop-down box in the user interface. LoadCustomStation() - Load station data fro a file in a textbox in the user interface. This gives users the flexibility of creating smaller sub networks or exploring different designs. ComputerTripInformation() - Makes a request to the Station- Stats program and sends the current station data. 5. Web Page PRT.tml Uses CSS, Javascript, Ajax, and DHTML to generate work environment without need to reload page icons implementation uses client-side code to enable tooltips on mouse rollovers, changing of icons when user clicks them, 11

12 and display of instructions for various functions (all without having to reload page) 12

13 4 Improvements For Next Year 4.1 Program Improvements Structural Improvements To be filled in Features to Add To be filled in 4.2 Logistical Improvements To be filled in by John 13

14 5 Appendix A Specified CSV File Format: Example Format in CSV COUNTY,LocID,Type,SubType,Name,Lat,Long,People,Visitors,Area,Revenue 1,1,3,,James Stock Trading Company, , ,30,10,6400, ,2,3,,Princeton University, , ,1400,3,12300,0 Fields County The county number, based on the NJ FIPS code which can be found at the below link. Most data for counties probably uses this format. of counties in New Jersey Should be stored as an integer (e.g. 1, 21) LocID (Long Integer) A unique NUMERICAL INTEGER ID assigned to each unique location in your lsit. There should only be one entry of a number per county, but there may be duplicates across counties. 14

15 Should be stored as an integer between 1 and 2 32, ascending order from 1 or labeling census blocks by block number wouldn t hurt. Type (Short Integer) A short integer used to tell the program which kind of location this entry pertains to. The type will set the display icon and the interpretation of the population number. Types are: 1. Residential 2. Education 3. Business 4. Recreation Subtype (Short Integer) Unused for the time being. In future classes, this may be used to further differentiate icons, such as to separate banks from grocery stores or kindergarten from a university. Should be a blank column Name (String) 15

16 The name/description of the item that will show up on the Goggle Map. Try to make it user friendly. For census housing blocks, label as Census (YYYY) Block #NNNN (for example Census (2000) Block #4931) Should contain no more than 32 alphanumeric characters; no commas, no punctuation. Latitude and Longitude (Separate Fields; Floating Point.) The latitude/longitude of the centroid point of the location in question, or some equivalent. Permanents/ People (Integer) The meaning will vary by type, but this essentially is a simplified way of dealing with the number of employees, residents, or students at a location. Depending on type the description of the field is: (1 Should be stored as a decimal number of degrees to a reasonable precision. Residential) : How many people live in this zone? (2 Education ) : How many students are served and how many faculty? (3 - Business ) : How many employees? Transients / Customers / Visitors (Integer) 16

17 For future use, the goal here is to be able to differentiate between permanent people (e.g. employees at Hoagie Haven) and total amount of traffic. This will also vary by type, but for recreation and education it can be thought of as 0 for not, for commercial it can be thought of in terms of Patrons Per Day This should be an integer between 1 and 2 32 Area (Long Integer) If available, the approximate area of the location in square feet; which is what NJ uses in its census data. I would almost prefer square miles, but for businesses and school that may not cut it. This should be an Revenue (Long Integer) If a business, total amount of revenue/sales. If Unknown, leave blank. Do not include commas or $ symbols. 17