Possible remedies could be additional training if the issue is area-specific, additional resources if the issue is city-wide. Causes could be things such as an aging vehicle fleet or area population growth. Council district data should be reviewed to determine if this is a city-wide trend or if this is occurring in specific areas. Missed collections is experiencing a significant increase since 2019 and is still trending upwards. Further analysis is required to see if locations of the occurrences are repetitive or clustered. Since 2019, illegal dumping has been the most popular service request in the City of San Diego. In 2020, service requests dipped significantly in April which correlates with the start of COVID-19 restrictions, and peeked in October. District data should be verified to see if spikes could possibly occur in more popular tourist areas. In 2019, service requests peeked in July and August. Toggle heat map (layer) and markers layer (lat, lon) of get it done requestsĬonclusions Number of Service Requests By Year.Drop down selector to filter data more granularly.Length in days to close a service request on average per category.Summary of open/closed service requests in date range.Show volume of service requests over time.Categories - type of service request over time and by location / council district.Service request counts - Most volume category Get-It-Done requests.If the City had historical data to confirm this assumption, the City could take a pro-active approach and request that the scooter service vendors increase their collection efforts during those times, thereby reducing the number of service requests, the amount of resources the City would otherwise have to dedicate, and last but not least: reduce the nuisance factor for the public. For instance, during tourist season or while large conventions are in town, it is possible that mobile service requests for scooters spike. The dashboard is a monitoring tool for City Leadership allowing for further investigation, remedying or use a pro-active approach as appropriate for the issue. The dashboard can assist City Leadership in quickly identifying problem areas or problem periods, such as holidays, tourist season, etc. Ongoing for the life of the app Importance: Service request volumes by type by council district Decision timing:.Ěverage response time from open to closed.Service request volume by period, type, council district.Strategic/Operational – identify problem-areas, monitor and gage effectiveness of the Get-It-Done program overall and by Council district, using: Under src, modify the config_sample.py file by renaming it to config.py and after mongo_conn=, pasting the link that we have provided to you in the comments with the submissionįrom VScode, open pages/index.html with live server Under pages/static/js, create a config.js file that contains this line: The following instructions for running the app are provided in the order in which they should be done: Thanks.City of San Diego Get it Done Dashboard Project Team git-it-on INSTRUCTIONS FOR RUNNING THE APP We've released update 6.3.2 to the app today - please let us know if this improves this issue. If you can email us more details at we'd be happy to investigate further with our development team. Thanks in advance for considering my suggestion. Or just an option to turn on, or off, the automatic location feature, maybe? A simple request for an address or other description of where an issue is would work. I would ask that this function be fixed, or just removed from the app. I don’t know if anyone else has mentioned this problem, but it is very irritating especially when the exact location is important to the issue being reported. It could be just a dozen feet, 100 feet off. I use the SD Get It Done app occasionally, and appreciate that you offer it to us, but one very frustrating issue it has, is that it always seems to automatically change the address/location of the issue being reported, and almost without fail, that automatically “corrected” location is wrong. Auto location feature is often inaccurate
0 Comments
Leave a Reply. |