On August 10th, EPA held a nationwide webinar on the lead and copper rule revisions (LCRR). Included was the data schema that should be followed. ESRI's solution looks close but is not the same. While the EPA does NOT require the exact schema be used, I think it would be a very good idea to. Please consider matching the EPA data schema in the solution. The schema presented is attached to this idea, or can be found on EPA's Lead and Copper page including a recording of the August 10th presentation. In the spreadsheet, the schema is on tab "Detailed Inventory". Since this is mandatory for every water provider with reporting deadlines, time is of the essence. Thanks.
Also attached is a comparison of the EPA documentation template with a comparison of schema from the ESRI L&C service line inventory Solution. The columns are the fields in the EPA template, and the rows represent the matching (or missing) ESRI field.
A Green cell indicates a matching cell in the ESRI schema (along with the field alias). A Red cell indicates no match in the ESRI schema, and a yellow cell indicates a sort-of match, where domain values or field intent don’t quite line up with the format the EPA recommends.
We are releasing an update to the Lead Service Line Inventory solution in November that will incorporate EPA's suggested schema into the solution. The schema changes will be minimal.
We are also exploring adding additional reporting capabilities to the solution to make it easier to populate the EPA template directly from ArcGIS as a means to report back your inventory to regulatory agencies.
Thanks for providing the comparison matrix.
@HowardCrothersHi Howard. Cleveland Water is looking to deploy. Any update on a release date or v2.0 docs? Thanks!
@xander Development work is complete, we are doing final testing and working on the updated documentation now. The update will ship with the November 2022 ArcGIS Solutions release, anticipate week of the November 16th.
@xander Absolutely, I'll send you an email and we can set up a time.
@HowardCrothers I would love to get a preview of the new schema as well, we are just starting our inventory and would love to make sure we are using the most up to date solution. Also the reporting capabilities would be very useful as well. Thanks!
@HowardCrothers ditto on the new schema, please.
@KadinBaird41 & @ChrisMiller_AK - sure we can give a preview. Can you message me your emails so we can setup something up?
@HowardCrothers I wish it was that easy...either our admin hasn't enabled the settings to allow PMs or I'm too stupid to find a way to send you a PM. Don't worry about it. Our management just decided to go with the GEC solution. Thanks for getting back to me.
@HowardCrothers I don't know if you have recieved my direct message, it's not showing up in my private conversations, but I am still interested in getting a look at the new schema.
Enhancement is now available in November 2022 release:
Lead Service Line Inventory
Release notes
Could we possibly just get a FGDB schema for download to use with ArcGIS Pro 2.9 or earlier? I'm still weary to make the jump to ArcGIS Pro 3, and I still have team members using ArcMap as it is...
@HowardCrothers @AyanPalit Hi Howard and Ayan,
Is there an ETA for when the updated Lead Service Line solution will be available ArcGIS Enterprise 10.9.1??
@imansbburg If you need a FGDB schema of the latest update to the solution you can just deploy the solution again to ArcGIS Online and export the service to an FGDB. Exporting the service to an FGDB happens through ArcGIS Online and isn't Pro version specific.
@jakemathis We can't make Version 3.0 of the Lead Service Line Inventory solution available on ArcGIS Enterprise 10.9.1. Version 3.0 is using some capabilities that are only available in Enterprise 11.0 and beyond.
@HowardCrothers Thanks for the information Howard.
Thank you. I did end up deploying the solution in AGOL because I was so curious to look at the feature service schema and setup. The deployment requirements said that ArcGIS Pro 3 was required, but I'm using 2.9.1....but am I understanding correctly there is no true restriction on Pro versions and only for Enterprise?
@imansbburg The Pro project that is deployed with Version 3.0 of the solution was created in Pro 3.0 and tested for Pro 3.0. So if you want to use the out of the box deployed Pro project you need Pro 3.x. Since that solution is just using Pro as a desktop client to edit feature services from ArcGIS Online (or Portal with Enterprise) the web apps, mobile apps, and feature services will all still function as expected. You can also create your own custom Pro project that consumes the V3.0 services in Pro 2.9.1.
I exported the service line feature layer to a GDB to add the fields to my existing layer schema. However the pick list/domain values do not come across. Is this an option or a limitation?
Hi Stacey,
I couldn't replicate your issue. My export includes the domains and dropdown values. I took the following steps:
Thanks @AlexKabak. I did use an enterprise geodatabase. I did find the domains, but they were not applied to the fields, so I only had to go through and add them. An extra step, but better than building from scratch. Thanks!
Faça login para publicar, seguir conteúdo e mais. Novo aqui? Registre-se gratuitamente.
