SpatialStream® Reference Documentation

SpatialStream™ provides a series of programming interfaces to simplify the integration of advanced spatial intelligence into your existing application. This page provides an index to reference documentation for each of the application programming interfaces. If you are looking at SpatialStream® for the first time we recommend that you don't start here, but start with the videos and samples

Client APIs

When to Use: The client application programming interfaces are the key to simplifying the integration with an existing application or building a new application. While the SpatialStream® application developer may use the SpatialStream® REST Services directly, the Client API will save the application developer time, and embeds spatial best practices that have been developed over many years.

The client APIs are specialized to each of the client environments, rather than try to wrap the underlying map control,  SpatialStream® works with the chosen map control. For most application programmers they are already familiar with a particular map control, whether it be Bing Maps or Google or others, and already have existing applications using that map control. So the SpatialStream™ client API minimizes the learning curve by adding new capabilities to existing knowledge, capabilities, and applications.

If you are starting out developing a mapping based application for the first time then learn the basics by browsing the excellent documentation for either Google Maps or Bing Maps, and then come back here to see how to add more advanced spatial capabilities with minimal coding.

REST Services

When to Use: The application programmer wants to call SpatialStream™ services directly from a client application not yet directly supported above, or where server to server calls are required. For example the REST Services can be used to synchronize data, generate a more precise geocode location, determine overlapping geographic features for a current location, generate a map image for use in reports, generate rollups, etc. use the SpatialStream® REST Services documentation.