Crash Magic ArcGIS Server Requirements for GIS-based Features

Crash Magic ArcGIS Server Requirements for GIS-based Features

Created
Last Updated
byadmin
Print
Issue

This article describes the ArcGIS Server requirements for street centerline, geocode/locator and print services, including samples of expected REST API request URLs and JSON responses. These services are required for Crash Magic GIS-based features to work.

Explanation
For Crash Magic GIS-based features to work, we require three publicly available REST services hosted from your ArcGIS Server (ArcGIS Online and other providers are not currently supported):
  • Map Service with street centerline data
  • Geocode Service based on same data set as street centerline map service.
  • Print Service (required if you are hosting an instance of Crash Magic internal to your agency)
Street Centerline Map Service Requirements
  • Street centerline data available as one or more layers.
  • Capable of an Identify operation (a “feature service” does not support Identify).
  • Dynamic, not tiled.
  • In addition to the required input parameters, we also require: f, sr, layers, returnGeometry.
  • Preferred spatial reference in an appropriate local projected coordinate system (not 3857).
  • Must be capable of returning segment geometry (polylines). The SpatialReference return parameter must indicate the coordinate reference system of the returned segment data.
  • Returned attributes must include full street name (and city or municipality as a separate attribute, if map service covers more than a single city or municipality).
  • Centerlines must break at intersection crossings.
Geocode Service Requirements
  • Able to geocode an intersection (e.g., W Main Ave & Elm St).
  • Able to geocode an address (e.g., 123 Main Street). This is only required when crash data references locations by address.
  • Capable of a findAddressCandidates operation.
  • Primary input fields (one or both acceptable):
    • Single line input
    • Street or Address (and City, if data set includes more than one city or municipality)
  • Additional required input fields: outFields, outSR
  • Preferred spatial reference in an appropriate local projected coordinate system (not 3857).
  • Preferred intersection connector: &
  • Geocoded points should be placed on the corresponding street center line(s) from the Map Service.
  • Returned data must include SpatialReference, and Candidates list, each candidate including address, location, score and attributes. The SpatialReference return parameter must indicate the coordinate reference system of the returned location data.
  • Candidate attributes should include an ‘Addr_type’ with possible values: address, streetaddress, intersection, or streetint.
  • For agencies, such as counties, that encompass multiple cities and unincorporated areas that may have similar street names, the locator must be capable of accepting a qualifier such as city name to assure a successful result.
  • For larger agencies (such as an MPO, COG or state DOT) that encompass multiple incorporated cities and counties, the locator must be capable of accepting necessary qualifiers to be able to return the proper locations.

Print Service Requirements

  • Provide an “Export Web Map Task” endpoint.
  • Required input fields: Web_Map_as_JSON, Format, Layout_Template, f.
  • Web_Map_as_JSON field must accept the format outlined in the Export Web Map Specification (see ESRI documentation link below).
Solution
Examples and documentation for each required service type are available below:
Street Centerline Map Service

Intersection and Address Geocode Service

Print Service
Was this article helpful?
0 out Of 5 Stars
5 Stars 0%
4 Stars 0%
3 Stars 0%
2 Stars 0%
1 Stars 0%
How can we improve this article?
How Can We Improve This Article?