Location information

Every service request that is submitted through Open311 requires a location, which can be given either as an address or a latitude and longitude. The Open311 configuration gives you several options for how to handle this information.

Addresses

An Open311 service request can include an address in the address_string field or an address ID in the address_id field. Address strings are saved in comments on the service request, but you have two options for handling address IDs, as defined in the Address Id Mapping attribute.

  • If you set the Address Id Mapping to ADDRESSKEY, the ID represents an Infor Public Sector address key. The request location will be set by entering the address key in the ADDRKEY column.
  • If you set the Address Id Mapping to GISFEATUREKEY, the ID represents the key of an address feature in your GIS. In this case Open311 will get the associated Infor Public Sector address key from the GIS. The address key is then entered in the ADDRKEY column.

You can also use a Match Address formula to set the address.

See Workflow formulas.

Latitude and longitude

The service request location can also be given as a latitude and longitude. Typically the Open311 app sets the latitude and longitude using the mobile device's GPS. The GeoReport specification defines WGS84 as the standard projection, so you may need to convert these values to the coordinate system that your agency uses.

To convert the latitude and longitude, add a Coordinates node to the Global Settings node in the Open311 configuration. The Spatial Reference attribute of this node specifies the coordinate system that the agency uses. The Translate Type attribute indicates how the latitude and longitude will be translated.

  • If the Translate Type is set to NONE, the coordinates aren't translated. NONE is the default.
  • If the Translate Type is set to SERVICE, an ESRI geometry service is used to translate the coordinates. The service URL is given in the Service attribute.
  • If the Translate Type is set to LOCAL, Open311 handles the translation locally using the DotSpatial API. (A copy of dotspatial.projections.dll is distributed with Open311 for Infor Public Sector.) The proj4j attribute specifies the Proj4 string to use for the translation. Additional information can be found at these sites: