ArcGIS REST Services Directory Login
JSON | SOAP

Water_Utility_Network/Water_Service_Connections (FeatureServer)

View In:   ArcGIS Online Map Viewer

View Footprint In:   ArcGIS Online Map Viewer

Service Description: <div style='text-align:Left;'><div><div><p><span style='font-weight:bold;'>Purpose: </span><span>Displays water service connection locations and attribute information. Water Service Connections usually are not shown at scales smaller than 1:2,400. In some cases even at 1:100 scale, meter symbols will overlap one another. This is partly due to automated methods for creating meter features at the ends of laterals, particularly based on automated methods for creating laterals off of mains. Ideally meter features are located as precisely as possible relative to their real-world locations—in practice this is expensive without using GPS, which doesn’t deal with the lateral locations. </span></p><p><span style='font-weight:bold;'>Intended Use: </span><span>Currently used for location and analysis purpose in the Water Distribution Viewer, mobile apps, Modeling, Dashboards and other Public Utility apps. In most web maps meters, are not the focus and therefore are not labeled—in a meter management map labels would be necessary.</span></p><p><span style='font-weight:bold;'>Department: </span><span>Public Utilities Department - Water Distribution Division and Customer Service Division.</span></p><p><span style='font-weight:bold;'>Data Source: </span><span>Referenced feature service on Enterprise portal</span></p><p><span style='font-weight:bold;'>How was the Data Manipulated: </span><span>Originally data was added to GIS from CIS records (See notes section below)</span></p><p><span style='font-weight:bold;'>How the Data is Modified: </span><span>Using the GIS_PREMISE_ID_VIEW for Oracle CIS database. GPS Specialists can join the by the premise-ID field and edit records (if needed) to ensure the feature class is synchronized CIS. Also the water service connections features can be overlaid with the parcel layer to acquire a PCN number and compare that to the view PCN and generate a list of premise-id, CIS PCN, GIS, PCN fields so CIS staff can update CIS records. </span></p><p><span><span>CIS Program Interface with PAPA: Donna Andrews is the primary user of an update program that interfaces with PAPA Water_UVIEW table. The program joins CIS records to the Water_UVIEW table by the PCN number and updates owner and service address in CIS. IF the PCN number is CIS no longer exists that record will not join rendering the process useless for updating that record. A review of CIS PCN's should be performed at scheduled intervals by GIS Specialist and provided to CIS so they can update the CIS PCN value.</span></span></p><p><span style='font-weight:bold;'>Update Frequency: </span><span>An scheduled maintenance should be established between Customer Service and GIS Management and documented in a department SLA.</span></p><p><span style='font-weight:bold;'>Notes: </span><span>February - July 2014: Purpose: Getting all S/P from CC&amp;B into GIS</span></p><p><span style='font-weight:bold;'>Process: </span><span>A spreadsheet was generated from CC&amp;B application with all existing Premises ID's, parcel numbers and service address: 1.Premise ID (AccountID field) from existing features were updated after join by Address. 2.Premise ID records that didn't joined were located manually or geocoded to the nearest location possible based on Address and PCN information. Site Address Point Feature Class (FC), Location ID FC and Owner Parcel FC, Road Centerline FC, CC&amp;B information and Engineering meter installation plans were used as reference. Most of these need to be GPS located; they are not all representative of the meter actual location. (Ex.Features located based on Site Address Point and Location ID are in the center of the property)</span></p><p><span style='font-weight:bold;'>July 2012: </span><span>2005-2006 and again in 2010 large sections of the Cities meters were changed out (approx.. 21,143) and as of July 2012 have been loaded into this Feature Class. CIS Premise points without X/Y coordinates (not part of the change out) are represented by a geocoded location based on addresses and not representative of the meters actual location. Also added are (some 11,000more) meters which will be GPS located at a later date. </span></p><p><span>It appears that the third party GPS located meters are generally within approximately 15 ft (in most cases) of what is true. The plan is to have these points placed more accurately in the future using more precise GPS tools with a Public Utility GPS crew.</span></p><p><span style='font-weight:bold;'>Aug 2010: </span><span>The layer features were originally mapped based on a join with the CIS Premise ID numbers; then joined with the City of WPB address point’s feature class to assign each meter to a spatial location.</span></p><p><span /></p></div></div></div>

All Layers and Tables

Has Versioned Data: true

MaxRecordCount: 2000

Supported Query Formats: JSON

Supports Query Data Elements: true

Layers: Description: Are not shown at scales smaller than 1:2,400. In some cases even at 1:100 scale, meter symbols will overlap one another. This is partly due to automated methods for creating meter features at the ends of laterals, particularly based on automated methods for creating laterals off of mains. Ideally meter features are located as precisely as possible relative to their real-world locations—in practice this is expensive without using GPS, which doesn’t deal with the lateral locations. In this map, meters, are not the focus and therefore are not labeled—in a meter management map labels would be necessary.

Service Item Id: a046d8870d9b4c64acd0e2ccc33fb388

Copyright Text: City of West Palm Beach - GIS

Spatial Reference: 2881  (2881)  LatestVCSWkid(0)


Initial Extent: Full Extent: Units: esriFeet

Document Info: Enable Z Defaults: false

Supports ApplyEdits With Global Ids: false

Support True Curves : true

Only Allow TrueCurve Updates By TrueCurveClients : true

Supports Return Service Edits Option : true

Supports Dynamic Layers: false

Child Resources:   Info   Query Data Elements   Relationships

Supported Operations:   Query   Query Contingent Values   QueryDomains   Extract Changes