I had a number of technical issues when working on this lab. The Google Maps API in particular
gave me issues. I am not a fan of how it organizes things and found it difficult to make anything
beyond superficial changes to examples given. I feel like I would have had fewer issues if I had
started with the Leaflet or Mapbox APIs. I personally would avoid it for anything beyond simple maps.
I had a few issues with the Esri API as well, but far fewer despite it being more complex
code (most of the complexity looks be more of a wrapper). It is reasonably easy to work with and
seems to be more flexible as well. I liked their documentation more too. I would use this API again.
One final thought: it was harder to find real time KML and geoJSON data than I thought it would be. It
looks like a lot of places are going away from KML in favor of other formats for one. Most "live" data
either required a subscription or didn't allow CORS, which is why I ended up sticking with the
earthquake data for 4.2. This makes sense in hindsight though, as if it's being hosted on local
infrastructure, an unexpected spike in usage could cripple servers, and if it's being hosted by
AWS, for example, that unexpected spike could result in unexpected costs as things scale up to handle it.