Investigate openstreetmap for potential use with the accessibility application

[joshi1983]

Investigate openstreetmap. This could include using it client-side using JavaScript pluggins or talking with openstreetmap api's to potentially augment our database or access it on demand.

[joshi1983]

Since the use of OpenStreetMap as a data source was covered by #201, the scope of this issue should be reduced to a client-side mapping alternative to Google Maps. Similar to Google Maps JavaScript API, there should be an OpenStreetMap equivalent.

Since we've already invested plenty effort into Google Maps on the home page, location search page, this issue should be very low priority. The main benefit from this investigation would be to be aware of an alternative to Google Maps in case Google Maps API quotas or pricing become too restrictive for us. It has been free and problem-free so far.

Here are some links I quickly found that may help this issue forward:

• https://stackoverflow.com/questions/925164/openstreetmap-embedding-map-in-webpage-like-google-maps
• http://leafletjs.com/

[joshi1983]

#564 is related to some changes by Google Maps that make this a little more useful but this should still be pretty low priority. Google Maps demands a billing account be associated with the Google Maps API keys. This isn't ideal but Google Maps still looks like the best option we have for client-side mapping.