Map Large API - Faster Google Maps and ArcGIS Maps
MapLarge offers an API to embed interactive maps on your website, blog or news story. Web
editors can save months of development time. Installation only requires a few
lines of code.
The MapLarge API consists of three components:
- 1. User Data or our Curated Data Sets
- 2. The MapLarge Geo Processing and Mapping Engine
- 3. A JavaScript and Flex API to request map tiles and interactive content
Data Upload
Users can upload both point and polygon data. An example would be a list of customer
locations and their revenues. Once uploaded, a user could view zip codes shaded
by the customer revenues within each zip code. Administrators can update the data
as often as they wish.
Real Time Automated Imports
Data can be added to the system on the fly and viewed instantly, either by users or by automated processes.
Geo Processing and Mapping Engine
The MapLarge API only requires a data set with locations and values. Once uploaded
the API can dynamically perform point-in-polygon tests and math functions on the
values included within a polygon. Continuing the previous example: the Geo Processor
can determine the sum, average, minimum and maximum values of customer revenues
within a zip code.
The Mapping Engine will then create the interactive tiles with polygons and points
color shaded and sized according to the values requested by the user. Multiple users
can each request their own unique queries of the data.
Interactive Tile Request API
The MapLarge API supports tile requests from standard Google Maps, Bing Maps and
ESRI Flex implementations. We also support stand alone URL requests for other
applications.
URL Request Format
The Map Large API returns interactive tiles and data when it
receives a simple REST query. A typical query will include the tile requested
and the layer to display. What follows is a brief explanation of the core
functions. Many additional functions are available.
HTTP Driven, Restful API
The map large API is a scalable http service hosted in the cloud. Most api implementations rely on a client library that abstract away
the concatenation of url request parameters but you always have the option to construct your own client to use the API in a low level fashion to meet your own needs.
Example: http://api.maplarge.com/Tile/Tile?
x=1&y=3&z=3&layer=geo~dot|data~AllGeocodedFinal
This URL requests a tile by x,y,z coordinates in the
Web Mercator format used by Google Maps, ESRI Flex, Bing Maps, and
other providers. The origin tile (0,0) begins at the top left corner of the map.
X represents the Tile position counting up as you move right from the Origin, Y
represents the Tile position counting up as you move down from the origin, and Z
represents the zoom level. Zoom level
0 is the least detailed level where 1 tile represents the entire world. For performance reasons level 20 is the maximum
zoom level, but higher levels of detail can be supported on request.
Layer Parameter - Geographical Visualization & Data Set
Example: http://api.maplarge.com/Tile/Tile?x=1&y=3&z=3&
layer=geo~dot|data~AllGeocodedFinal
The layer parameter of a tile query string is a required component. The
Layer Parameter includes the option to choose which data set the layer will
display. It also includes the option to select the visualization of the data,
either dots or shaded polygons on the map.
Geography:The two geography options are "dot
" (example: 'geo~dot') and
"poly"
(example: 'geo~poly~county'). Selecting dot simply renders dots and selecting poly
renders polygons with associated attributes and optional dynamic point totals for
points within the polygon that meet all query/filter requirements. Any ESRI / ArcGIS
Shapefile
can be used to render polygons that can be associated with any other point set
and filtered on the fly. Additionally, Country, State, County, Zip, CensusTract,
SchoolDiscrict, Congressional District, and CensusBlock Group shapefiles and
demographics are all available for use in conjunction with any custom polygon import.
Data:Data is the point file that will be drawn as dots or polygons on the
map tiles. The first parameter is the name of the uploaded data file without
the file extension
and the second (optional) parameter is the name of the field for chlorepeth (spectrum)
style shading.
Shader Parameter - Color & Design Options for Polygons & Points
The optional shader parameter describes how the points or shapes on the map are
to be drawn. If no shader is provided red dots with black borders are rendered.
Dot: - Size, FillColor, BorderWidth, BorderColor To use a single dot style
for all points use this method.
External Image: url To use an external image hosted on your server use this
method
Interval: colors, values, sizes, text To create a shaded spectrum of colors,
sizes, opacity and labels use this method.
Filter Parameter - Queries the Data Set
Filters work dynamically against underlying point sets to restrict the points shown
on a map or to restrict the points aggregated withing the polygons of a shape layer.
Applying a filter to a shape layer allows users to instantly see totals by geography.
For a working example see
here
String: Contains, ContainsOR, Equals, NotEqual: Filter string values
Number: Equals, NotEqual, Less, Greater
: Filter numeric values
Older MapLarge API v3 Examples: