So far we’ve looked at the different mapping API’s and then looked at way to store spatial data. Now we are going to put together some come structures and explain when they would make sense to implement.

In the first part of article I talked about the different mapping API options that are commonly used. In this part of the article I will discuss data storage and low cost hosting options. For almost all mapping applications data needs to be stored in one form or another and there are a lot of options out there to help with this.

Recently I was trying to setup Entity Framework for a .NET 4 application on a MySQL database for a GoDaddy site that used shared hosting. In this environment applications have medium trust which can make things very frustrating as applications will work perfectly fine locally but will crash miserably when deployed with security exceptions. After pulling my hair out for several days I finally managed to get everything working smoothly.