Deployment guide: First, implement stored procedures on Microsoft SQL Server to connect to your APIs listed in HW4. Create a database to store stored procedures (DatabaseMaker.sql). Insert data into the database with another stored procedure. (DatabaseMaker.sql).Copy & paste pages from HW4 and HW5 files respectively into Microsoft Virtual Studio. Run HW4 and 5 simultaneously. If you run into errors, refer to Joshua Meadows' GitHub repository, MIST 353 TravelSite2.
The home page welcomes the user and shifts the homeowner's attention to a link that greets them with a dropdown menu. The homeowner can choose whichever city they desire to get the weather forecast for that location. A table is prompted after selection, which gives them the cityID and the WeatherForecast. This data comes from my APIs completed for HW4. (Skylar)
Prompts used: write javascript code for a razor page that asks the user to enter a city id from a dropdown list
Curtis' / Natural Disaster's displayed and able to be filtered by City, Add a natural disaster, and Privacy Policy Razor Pages
Displays all disasters in the database sorted by CityID and allows them to be filtered by CityID
Lets a user add a disaster by entering CityID NDDate NDType
Makes it clear any information entered on the AddDisaster page is stored, and that we track nothing else.
Supposed to pull the api data from the SQL server to give the user a table of instances where that city got different Forecasts, and what they were originally predicted to be. Was supposed to have the same menu Skylar had for her getForecast but use it differently to keep the feel and structure of the website the same, using the dropdown menu, but i couldn't quite get the API to connect and display on the page. Input was supposed to be the CID from the dropdown used in the URL to take the user to a table with that CID and display every instance that CID was used in.
Lets a user add an instance of a forecast and an actual temp by entering CID, FCTemp ATemp.
Recorded Lectures, ChatGPT when encountering errors, Used Skylar's GetCityData and changed the return value to give a different result from what her page did.
I am writing code to display different Forecasts in different cities in a table format. The Variables are CID, FCTemp, ATemp. I am also trying to retrieve the data from an API. How would I go about doing this?
If you're moving to a completely new area or considering it there's information that isn't listed on zillow you may want to know. You might want to know how often certain natural disasters occur, tornadoes, earthquakes, and hurricanes espcially are important. So every time a disaster is declared in a city (or soon to be) in the database the type of disaster and the date it occured should be recorded. A couple retiring to a town in Florida or Maryland, where I'm from, hurricanes are a regular thing, although only some get a declared disasters state of emergency. Beyond this, whenever you move to a new area you have to learn the weather patterns, we all know the apps aren't perfect. I always assume Morgantown will be colder than any app says, but how would I have known that before I came without talking to anyone who had lived here? Another part of our app stores the weather forecasts and what the weather really was to gauge the accuracy of weather forecasts in the city.
##For Future Developers The next feature to implement is the ability to search cities by zip code and pull all the data automatically so as any city in the country or ideally world can be searched for and have its information viewed. The database is fairly straightforward and has almost no relationships (with the exception of everything to city) only 10 cities are currently implemented and the addition of more should be a priority. Temporarily the addDisaster page should be behind some sort of security wall so not just anyone can enter a disaster, with only 10 cities the developers can maintain updating that table. When the number of cities is expanded, the weather forecast and natural disaster history should be pulled automatically as discussed before. Having a unique id for every city in the country or world is unrealistic, so since we've prioritized United States data, a zip code would be a easy to use but accurate substitute for city and state that should be fairly easy to implement later. The code bases are not unified despite a lot of trying, sorry, good luck. (Curtis)