StreetWise can use ESRI ArcGIS shapefile set for the hydrants as the georeferenced data points for its tablet hydrant display. This shapefile set should be able to be exported from the ESRI enterprise or hosted application packages. We often obtain these directly from a city/county GIS department or from the water utility company directly. The shapefile set will include an attribute tablet that may already contain information that is useful for the responders, such as main size, flow rating, outlet sizes, etc. We can use this to populate the hydrant text pop-up.
If you are using Emergency Reporting RMS, we can very simply export your hydrant information directly out of ER and into StreetWise. Remember that the location accuracy will only be as good as the quality of the latitude and longitude coordinates in ER. If you have not populated the latitude and longitude in ER, then the file will not be able to be used for mapping in StreetWise and you’ll be better off working with option in the paragraph above.
The same may hold true for users of Firehouse RMS, though not all users have access to the full suite of exporting capability. If you are using Firehouse Cloud, you will need to determine what optional software components you might need to enable export of the hydrant data. Exporting records from Firehouse Cloud edition is not necessarily a standard feature. If you are using the non-hosted enterprise version, you can create a hydrant data export using the Custom Query feature and we can assist, if necessary.
If you have data, but not latitude and longitude coordinates, stored in your RMS database that is not included in the GIS attribute table (i.e. flow test results), these can be joined to the GIS attribute table for use in the interactive display labels, but only if there is a common identifier field. So, for instance, if you include the utility company’s hydrant ID number in the RMS data records and that ID number is also present in the GIS shapefile table, we can easily perform a join to put those two data tables together. If there is not a common identifier field, it can be quite a bit trickier, but not necessarily impossible. In such a case, we would want to examine the data before determining whether, or how, it could be joined.