Maps From APIs - Serving Maps From Other Sources

Google Maps and Keyhole Markup Language

Google has given us the ability to plot, display and share interactive route maps, location information, photographic Street Level imagery and many more features. Around these features we can apply a Google API that will display our route maps or any of the above geospatial data, on websites and mobile apps.

The maps below are rendered with a sharing of information between the Google Maps server and the server on which the route files are held.

The Page is called KMZS denoting the fact that KMZ files, created and exported as KMZ - a Google Maps file format, from an Open Source route planning website www.GPSies.com. Several Way points were added to the track created, clicking on a route or a waypoint will reveal details about its nature and the source of the information.

A KMZ file is compressed, containing the KML file of the same name. Driven by the Javascript in this HTML Page Header instructs Google how to render the route accurately on the map. The data is all geospatially defined and aligned and hence renders exactly on the basemap.

Driving and Cycling Routes On the Island

Pub Drive #1
Lifeboat Museum #2
Short Cycle Route #3
To The Bull & Porter #4

What Are APIs?

In computer programming, an application programming interface (API) is a set of routines, protocols, and tools for building software and applications.

An API expresses a software component in terms of its operations, inputs, outputs, and underlying types, defining functionalities that are independent of their respective implementations, which allows definitions and implementations to vary without compromising the interface.

A good API makes it easier to develop a program by providing all the building blocks, which are then put together by the programmer.

CSS From APIs

In some instances it is possible to experience a conflict of css commands. On this particular page on the website, a conflict, as yet unresolved, has occurred between css comands built into the site's core css file and css scripts called for by the Google API, causing the page's footer to be displaced to the right.