1. Web Development Web development never ends: 1.Find out what the stakeholders need (sponsors, users, etc.) 2.Investigate available technology 3.Plan the project 4.Build/update the web site 5.Test functionality in all browsers 6.Release the site 7.Monitor and maintain 8.Go to 1.

2. Technical Issues Keeping a web site available Maintaining a server Getting “hacked” Performance problems

3. Bottom Line If your web site is not available: –You don’t exist!

4. What is a web server? Has a “hard IP”. –An IP address that never changes Runs “web server” software –Typically IIS or Apache Typically: –Is in a “rack” in a protected space that is: Is environmentally controlled (air conditioned) Has “conditioned” power (a UPS) –Has redundant components

5. Maintaining a server You can “rent” space on a server –DropBox offers a “Public” folder A server costs from $500 to $100,000 –Don’t listen to what the manufacturers tell you what you need! Talk to other developers. It costs $100 to $200 per month to have someone “host” your server. In theory, you could have a server at your house but it is not recommended

6. Software Keep the server as simple as possible –Complexity = more failures Limit access Do required updates There are web site that will monitor your server and email you if it goes down

7. Getting Hacked Common Types: –SQL Injection –“Stealing Bandwidth” –Web Server breach –Uploading viruses –Denial of server

8. SQL Injection In a query string, enter: –“Query; DELETE FROM ‘ ’” –Deletes the entire contents of the table Can also steal info from DB Easy to protect from: –Check for single quotes and replace them with two single quotes –Don’t allow “delete from” in a query –Don’t allow sensitive information in your database

9. Stealing Bandwidth Someone breaks into your server and puts a bunch of data there. Then, they make you their download site Causes a massive spike in bandwidth which you have to pay for! Preventing: –Don’t have FTP sites –Keep web software up to date –Make sure your ISP monitors for them

10. Web Server Breach An HTML steam that breaks your web server and then takes over your server. Used to steal band width and corrupt your server’s contents Preventing: –These are rare and can only be prevented by the web server software provider –Keep web server software up to date

11. Uploading Viruses User’s upload a file that than runs a program or “sleeps” until users download it to their computer –Allows others to get you to distributed viruses! Don’t allow “scripts” to be uploaded. This includes: –“xls”, “doc”, “ppt” files!

12. Denial of Server A web service is written that calls your web site over and over again to “bring it down”. IIS can crash with these Preventing: –Don’t attract attention If you do, get a lot of servers –Block abusive users –Education and only allow reasonable web service calls

13. Reality Getting hacked today is rare –Twice in last 6 years (never in last 4) Keep the OS and web software up to date Don’t let a lot of folks edit the contents of your server Keep an eye on it Other problems (like performance) will be bigger.

14. GIS Web Sites GIS web sites “go bad” because of: –Poor user design –Poor performance New issues: –Scripting performance –Database performance –Geospatial data access

15. Scripting Performance Use a “modern” language Make sure there is minimal recursion –Functions calling functions –Scripts calling scripts –Including files that include the same files Find the “bottlenecks” and fix them Don’t use ArcGIS (you’re not allowed to in a server environment anyway).

16. Database Performance Don’t use MS-Access or MySQL Use indexes (search trees) Minimize string searches –Index if needed Minimize hierarchical queries Do performance analysis on key queries and add redundant data if needed

17. Geospatial Issues Pixels.vs geographic systems Cartesian vs. tiles Tiled data Transfer speeds

18. -180 180 90 -90 Width in Pixels Height in Pixels

19. 10,000,000 meters 6,600,000 meters UTM, Zone 10

20. 0,0 Positive X Positive Y Pixels Easting, Northing Positive X Negative Y Geospatial Coordinates

21. Raster Pyramids Problem: –Rasters can be huge! –The Internet is slow Analysis: –Users can only view about 1000 x 1000 pixels at time –Options: Large area at low resolution Small area at high resolution Solution: –Create a “pyramid” of tiles and only transfer the tiles that are needed

22. Raster Pyramid

23. 0,0 256,256 Zoom Level 0

24. 0,0 512,512 Zoom Level 1 0 1 1 0 Columns Rows

25. 0,0 512,512 Zoom Level 1 0 1 1 0 Columns Rows

26. 0,0 512,512 Zoom Level 1 0 1 1 0 Columns Rows

27. Zoom LevelPixel WidthNum Columns Size (Pixels)Num Tiles 12561 655361 25122 2621444 310244 104857616 420488 419430464 5409616 16777216256 6819232 671088641024 71638464 2684354564096 832768128 107374182416384 965536256 429496729665536 10131072512 17179869184262144 112621441024 687194767361048576 125242882048 2.74878E+114194304 1310485764096 1.09951E+1216777216 1420971528192 4.39805E+1267108864 15419430416384 1.75922E+13268435456 16838860832768 7.03687E+131073741824 171.7E+0765536 2.81475E+144294967296 183.4E+07131072 1.1259E+1517179869184 196.7E+07262144 4.5036E+1568719476736 Sum:6.0048E+1591625968981

28. Vector Pyramids Vector data is getting later –Millions of points –Complex, global polygons Vector Pyramids are coming –Each tile contains GeoJSON data for that tile