GeoJSON

Skill level
2 Previously Proficient

At FlyteComm, we used the GeoJSON protocol extensively to communicated map information from our servers. I have not used it since. We mostly used it to make the product more appealing to government customers that insisted on the use of standards and direct access to our servers rather than using the Flash client provided. Since the servers were required to provide GeoJSON, my Flash map client used it too.

Experiences using this skill are shown below:



FlyteComm map clients

Designed and implemented complex, real-time, universal map display applications in Adobe Flash for the web and CocoaTouch for the Apple iPad that yielded a significant increase in revenue and helped achieve financial independence for the company (according to the President/CEO, Maurice Bailey).

Re-engineered the Flash Viewer Map Plug-in

The redesigned map plug-in solved a long-standing problem with the old map plug-in that was actually a port of some old code written by someone else. The new plug-in required a lot less memory, was a lot less buggy and it could show dozens of different base maps from multiple map tile servers. All of this could be configured without touching any code (unlike route-me and OpenLayers). The map type selected in this screenshot was  the USGS topo map. The pushpin labels were draggable and individually displayable.

Added 200+ NOAA Weather overlays to Universal Flash Viewer

Updated Flash Viewer to support the WMS (Web Mapping Services) supported by NOAA’s weather servers complete with tile image stretching to approximate image warping from the Geographic to World Pseudo Mercator (used within the Flash Viewer). Had the Viewer talking to 24 NOAA weather servers supporting more than 200 weather overlays (including storm tracks, fires, floods, radar, and so on) with full visibility control working in just over a week (on a rush schedule) to show to the FAA. Also added GeoJSON support for NOAA aviation weather.