CCTV Manager is nu beschikbaar! Ontvang het nieuwste van ArcGIS Solutions for Water<\/A>.<\/SPAN><\/PRE><\/P>In de loop der jaren hebben we veel waardevolle feedback ontvangen over de CCTV Processor<\/A> oplossing. Als u niet bekend bent met deze oplossing, is het een geoprocessing tool voor ArcMap die NASSCO PACP standaard versie 6 gesloten circuit rioolvideo-inspectiegegevens importeert. De Inspecties en Conditietabellen worden omgezet in punten voor elke observatie en lijnen voor het hoofdonderdeel dat is onderzocht. De observatiebeelden of foto's worden ook geladen als bijlagen, waardoor het gemakkelijk is om de gegevens als een service te publiceren en iedereen in uw organisatie toegang te geven tot de CCTV-gegevens. Deze oplossing ontsluit eenvoudigweg de schat aan informatie die tijdens CCTV-onderzoeken wordt vastgelegd.<\/SPAN><\/P><\/P>Vanwege gebruikersverzoeken om andere importtypes en de nieuwe PACP v7 te ondersteunen, wisten we dat het tijd was om CCTV Processor te verbeteren.<\/SPAN><\/P><\/P>1:<\/STRONG><\/SPAN> Overstappen van Model Builder naar een Python Toolbox: <\/STRONG><\/SPAN>Model Builder is geweldig om een complex proces te definiëren, we hebben een snellere, gemakkelijker te gebruiken en stabielere tool gebouwd met behulp van een <\/SPAN>Python Toolbox<\/A>. <\/P><\/P><\/P>2: Ontworpen voor ArcGIS Pro:<\/STRONG><\/SPAN> Om de aankomende Utility Network naast gegevens die worden weergegeven in een Geometric Network te ondersteunen, hebben we CCTV Processor gemigreerd naar ArcGIS Pro. Dit stelde ons ook in staat om de code te stroomlijnen, waardoor deze sneller en betrouwbaarder werd.<\/SPAN><\/P> <\/SPAN><\/P>3: Oplossing van BUG-000104129:<\/STRONG><\/SPAN> De huidige tool werkt uitstekend voor observatiepunten op een pijp uit meerdere onderzoeken, maar we hadden één probleem dat moeilijk op te lossen was in de huidige versie. Als een pijp meer dan eens werd onderzocht, maakten we slechts één inspectielijnsegment aan. De nieuwe versie heeft deze bug opgelost.<\/SPAN><\/P> <\/SPAN><\/P>4: Ondersteuning voor meerdere invoerschema's:<\/STRONG><\/SPAN> De update stelt ons in staat meer dan alleen PACP v6.0.4 versiegegevens te ondersteunen. U krijgt nu de optie om PACP v6.0.4, PACP v7.0.7 en Custom te selecteren. Het selecteren van een van beide PACP-opties vult automatisch de rest van de parameters van de tool in. Als u Custom selecteert, moet u deze parameters aan uw invoer koppelen. Er is nu een optie om extra schema's toe te voegen aan de lijst met opties. We zullen dit proces bij release toelichten of als u het wilt proberen, plaats dan een reactie en wij zullen instructies geven.<\/SPAN><\/P><\/P><\/P><\/P><\/P>We hopen dat u de nieuwe versie leuk vindt. Dit is slechts de eerste preview. We hebben nog niet alle functies overgezet, zoals berichten of linkconversie. <\/SPAN><\/P> <\/SPAN><\/P>We zijn ook op zoek naar enkele van uw CCTV-gegevens om te testen. Als u een PACP v7-export of een ander schema heeft en het niet erg vindt dit met ons te delen, zouden we het graag testen om ervoor te zorgen dat alles 100% functioneel is.<\/SPAN><\/P><\/P><\/P>Aan de slag met CCTV in Pro<\/STRONG><\/SPAN><\/P>Er zijn enkele installaties vereist:<\/SPAN><\/><\/>\n1. <\/>www.microsoft.com/en-US/download/details.aspx?id=13255\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">Microsoft Access Database Engine 2010 Redistributable<\/><\/>\nAangezien ArcGIS Pro een 64-bit applicatie is, zorg ervoor dat u de x64-versie kiest.<\/> us.v-cdn.net/6038851/uploads/legacyfs/online/357275_pastedImage_2.png\" style=\"width: 620px; height: 378px;\" \/>2. pyodbc<\/>U kunt dit eenvoudig installeren via de pro.arcgis.com/en/pro-app/arcpy/get-started/what-is-conda.htm#ESRI_SECTION1_175473E6EB0D46E0B195996EAE768C1D\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">Python Package Manager<\/> us.v-cdn.net/6038851/uploads/legacyfs/online/357276_pastedImage_3.png\" style=\"width: 620px; height: 395px;\" \/> Als ArcGIS Pro crasht na de installatie, zie dancommunity.esri.com/thread/195911-workaround-installed-package-crashing-pro-141\" target=\"_blank\"> dit GeoNet bericht<\/> voor een gids om het probleem op te lossen.De afbeelding toont versie 3.0.10. &nb sp;&nb sp;&nb sp;&nb sp;&nb sp;&nb sp;&nb sp;&nb sp;&nb sp;. PYODBC versie 4 wordt ook ondersteund.& nbsp;. Versie 4.0.17 is getest op RC2. Mike &amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;p Paul ArcGIS for Utilities
<\/P>
In de loop der jaren hebben we veel waardevolle feedback ontvangen over de
Vanwege gebruikersverzoeken om andere importtypes en de nieuwe PACP v7 te ondersteunen, wisten we dat het tijd was om CCTV Processor te verbeteren.<\/SPAN><\/P><\/P>1:<\/STRONG><\/SPAN> Overstappen van Model Builder naar een Python Toolbox: <\/STRONG><\/SPAN>Model Builder is geweldig om een complex proces te definiëren, we hebben een snellere, gemakkelijker te gebruiken en stabielere tool gebouwd met behulp van een <\/SPAN>
2: Ontworpen voor ArcGIS Pro:<\/STRONG><\/SPAN> Om de aankomende Utility Network naast gegevens die worden weergegeven in een Geometric Network te ondersteunen, hebben we CCTV Processor gemigreerd naar ArcGIS Pro. Dit stelde ons ook in staat om de code te stroomlijnen, waardoor deze sneller en betrouwbaarder werd.<\/SPAN><\/P> <\/SPAN><\/P>3: Oplossing van BUG-000104129:<\/STRONG><\/SPAN> De huidige tool werkt uitstekend voor observatiepunten op een pijp uit meerdere onderzoeken, maar we hadden één probleem dat moeilijk op te lossen was in de huidige versie. Als een pijp meer dan eens werd onderzocht, maakten we slechts één inspectielijnsegment aan. De nieuwe versie heeft deze bug opgelost.<\/SPAN><\/P> <\/SPAN><\/P>4: Ondersteuning voor meerdere invoerschema's:<\/STRONG><\/SPAN> De update stelt ons in staat meer dan alleen PACP v6.0.4 versiegegevens te ondersteunen. U krijgt nu de optie om PACP v6.0.4, PACP v7.0.7 en Custom te selecteren. Het selecteren van een van beide PACP-opties vult automatisch de rest van de parameters van de tool in. Als u Custom selecteert, moet u deze parameters aan uw invoer koppelen. Er is nu een optie om extra schema's toe te voegen aan de lijst met opties. We zullen dit proces bij release toelichten of als u het wilt proberen, plaats dan een reactie en wij zullen instructies geven.<\/SPAN><\/P><\/P><\/P><\/P><\/P>We hopen dat u de nieuwe versie leuk vindt. Dit is slechts de eerste preview. We hebben nog niet alle functies overgezet, zoals berichten of linkconversie. <\/SPAN><\/P> <\/SPAN><\/P>We zijn ook op zoek naar enkele van uw CCTV-gegevens om te testen. Als u een PACP v7-export of een ander schema heeft en het niet erg vindt dit met ons te delen, zouden we het graag testen om ervoor te zorgen dat alles 100% functioneel is.<\/SPAN><\/P><\/P><\/P>Aan de slag met CCTV in Pro<\/STRONG><\/SPAN><\/P>Er zijn enkele installaties vereist:<\/SPAN><\/><\/>\n1. <\/>
Mike &amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;p Paul
ArcGIS for Utilities
You will need a machine that has the 64 driver installed so you can create the fgdb from the access files. I was able to get 64 bit access driver on my machine with 32 bit office by first installing the 64 bit driver and then office.
I have noticed the CCTV Processor is being replaced with CCTV Manager. The 64-bit Microsoft Access Database Engine is now a requirement for these tools to work. Will ESRI still provide a workaround for those of us who are still running the 32-bit version?
We're using the latest beta processor to convert multiple clients historic data from an old Access database system into a GIS system. All of our clients have converted over successfully except for one, and we are getting the following error when we try to run their data through the processor. Any help would be greatly appreciated!
Start Time: Monday, June 25, 2018 5:37:09 PMRunning script CreateConditionPoints...17:37:09 Saving results to C:\Users\mfacer\Documents\ArcGIS\Projects\VersaillesCCTV\CCTVResults3.gdb17:37:12 Loading 3,138 records from CONDITIONS table17:37:13 Loading 243 records from INSPECTIONS table17:37:16 Loading 3,142 records from MEDIA_CONDITIONS table17:37:16 Loading 243 records from MEDIA_INSPECTIONS table17:37:17 Splitting lines17:37:17 Locating conditions Traceback (most recent call last): File "C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3\lib\site-packages\pandas\core\common.py", line 399, in _asarray_tuplesafe result[:] = valuesValueError: could not broadcast input array from shape (0,2) into shape (0)
During handling of the above exception, another exception occurred:
Traceback (most recent call last): File "C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3\lib\site-packages\pandas\core\frame.py", line 2564, in _ensure_valid_index value = Series(value) File "C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3\lib\site-packages\pandas\core\series.py", line 264, in __init__ raise_cast_failure=True) File "C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3\lib\site-packages\pandas\core\series.py", line 3277, in _sanitize_array subarr = _asarray_tuplesafe(data, dtype=dtype) File "C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3\lib\site-packages\pandas\core\common.py", line 402, in _asarray_tuplesafe result[:] = [tuple(x) for x in values]ValueError: cannot copy sequence with size 2 to array axis with dimension 0
Traceback (most recent call last): File "C:\Users\mfacer\Documents\ArcGIS\Projects\PennHillsCCTV\CCTVProcessorA4W_Preview_RC2\CCTVProcessorA4W\Maps and GDBs\cctv\gptools.py", line 455, in execute image_name=abstract.media_condition_image) File "C:\Users\mfacer\Documents\ArcGIS\Projects\PennHillsCCTV\CCTVProcessorA4W_Preview_RC2\CCTVProcessorA4W\Maps and GDBs\cctv\gptools.py", line 411, in run points, lines = p.save_to_disk(target_gdb=gdb) File "C:\Users\mfacer\Documents\ArcGIS\Projects\PennHillsCCTV\CCTVProcessorA4W_Preview_RC2\CCTVProcessorA4W\Maps and GDBs\cctv\core.py", line 467, in save_to_disk df = self.process() File "C:\Users\mfacer\Documents\ArcGIS\Projects\PennHillsCCTV\CCTVProcessorA4W_Preview_RC2\CCTVProcessorA4W\Maps and GDBs\cctv\core.py", line 423, in process df[self.inspection_point] = df[[self.pipe_shape, 'percent']].apply(lambda f: self._locate_point(*f), axis=1) File "C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3\lib\site-packages\pandas\core\frame.py", line 2519, in __setitem__ self._set_item(key, value) File "C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3\lib\site-packages\pandas\core\frame.py", line 2584, in _set_item self._ensure_valid_index(value) File "C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3\lib\site-packages\pandas\core\frame.py", line 2566, in _ensure_valid_index raise ValueError('Cannot set a frame with no defined index 'ValueError: Cannot set a frame with no defined index and a value that cannot be converted to a Series Failed to execute (CreateConditionPoints).Failed at Monday, June 25, 2018 5:37:17 PM (Elapsed Time: 8.35 seconds)
I'm working on a version that will read the CCTV data from a file geodatabase. There will be a separate tool (which still requires pyodbc), to convert Access to FGDB.
I am running into the same issue as Tristan because my version of Office is 32bit. Is there any way to get this new version of CCTV Processor to work for those of us who can't install the 64bit version of Office?
Thanks everyone for the feedback so far! We've just uploaded a new beta version with the following enhancements and fixes:
We're also investigating an import of MACP inspections. If you have any MACP data that you can share, please let us know. We're also interested in any version 7 data (PACP or MACP).
You can email to pleblanc@esri.com or mmiller@esri.com
sorted([None, ''])
gives that error message. As you noted, pandas will insert NaN (which is similar to None). The simple fix is to filter None out before sorting inside the create_sql function.
I'm curious what configuration of the data will get into this state.
Your error is saying TypeError: '<' not supported between instances of 'NoneType' and 'str', look if that value shows up anywhere in your data, the "<". Also looks for any strings in a number field or numbers in a string field. Otherwise it sounds like an problem with either the create_sql function which I assuming is writing a SQL clause as a string before passing to an sqlParser but something how the string is created is messed up. The tool usings python pandas. In pandas the object type does not necessarily mean dtype str. and pandas forces the type to change when it inserts NaN values so this could be happening here. However I'm mostly just speculating as I did not deep dive into debugging it
Hmm, I'd need to look at the data. Can you provide your pipes feature class and access database? You can email to pleblanc@esri.com
Paul, I do not see any empty values in the tables, specifically in the ConditionID field. Any other assistance would be greatly appreciated.
There's probably an empty value in one of the access tables. I think this might be be ConditionID field.
I am getting the following error when running this tool and would greatly appreciate any help in solving this problem:
Running script CreateConditionPoints... Traceback (most recent call last): File "<string>", line 438, in execute File "C:\Users\mfacer\Documents\ArcGIS\Projects\PennHillsCCTV\CCTVProcessorA4W\Maps and GDBs\cctv\cctv.py", line 230, in __init__ self._check_dtypes() File "C:\Users\mfacer\Documents\ArcGIS\Projects\PennHillsCCTV\CCTVProcessorA4W\Maps and GDBs\cctv\cctv.py", line 236, in _check_dtypes pipe_pk = self.pipe[self.pipe_pk].dtype File "C:\Users\mfacer\Documents\ArcGIS\Projects\PennHillsCCTV\CCTVProcessorA4W\Maps and GDBs\cctv\cctv.py", line 280, in pipe sql = create_sql(self._pipe_table, self.pipe_pk, self.inspection[self.inspection_fk].tolist()) File "C:\Users\mfacer\Documents\ArcGIS\Projects\PennHillsCCTV\CCTVProcessorA4W\Maps and GDBs\cctv\cctv.py", line 37, in create_sql values = sorted(set(values))TypeError: '<' not supported between instances of 'NoneType' and 'str' Failed to execute (CreateConditionPoints).
Tristan, would it be possible for you to share you data with us? You can email to pleblanc@esri.com
What version of Office do you have installed? I have x86 Office 365, and I can install and use x64 Access driver without issue.
I have Microsoft Office Suite 32bit and Access 32bit installed. If I try to install the Microsoft Access Database Engine 2010 Redistributable(64bit) I get an error "You cannot install the 64-bit version of Microsoft Access Database Engine 2010 because you currently have 32-bit Office Products installed"
If I force the install using the /passive command prompt command it "installs" however when try to run the CCTV processor I get the following error, "Unable to load odbcji32.dll"
If I remove Office and Access and then install Microsoft Access Database Engine 2010 (64bit) the CCTV processor works but I don't have Office suite or Access now.
If I attempt to reinstall Office and Access 32bit, I get the following error "You cannot install the 32-bit version of Microsoft Office Suite because you currently have 64-bit Microsoft Access Database Engine 2010 installed"
This is a bit of a Catch 22
Is there a correct installation practice for Office 32bit and Access 32bit along with getting the CCTV processor to work other than installing the 64bit version of Office?
[UPDATE]
- I was able to get it to work alongside Office only by installing the 64bit version of Office and Access. This is not ideal.
- I was able to run the processor (PCAP 6.04 Schema) however the results were incorrect only 146 conditions came through out of an expected 6431.
- I was able to run it with the old CCTV processor and the results were as expected 6431.
- Not really sure what wrong with the new CCTV processor,
For example:Using the Old CCTV processor, I have a pipe with ID 4082. It has three separate inspections on it (95, 96, 403) and a total of 87 conditions.
Using the new one, it only has 3 conditions one for each pipe inspection (95,96, 403) and that's it, everything else is missing.
So for this year's CCTV going to use the Old CCTV Processor and hopefully next year the new one works correctly.
[UPDATE 2 - 28/11/2017]
- So it appears installing the 64bit version of office causes some additional headaches when using ArcGIS 10.3.1 and trying to load Excel tables into ArcMap.
- It gives you the following error: "Connect: Failed to connect to database. An underlying database error occurred. Class not registered."
- You can read more about this problem here: .XLSX PROBLEM - Failed to Connect to Database - Class Not Registered
- Easiest solution was to save the excel file as ".xls"
The goal is to have it updated and release for ArcGIS Pro 2.1 in January. You can start with the Beta and update when the release version is available. The end results will be very similar.
I'm looking to set this up for the first time, should I just wait until its official released as an update and ArcGIS Pro integrated? CCTV Processor | ArcGIS for Water
Any idea how much longer?
Thx
That solved the problem. I just needed to modify the table names in the original survey database. Thank you very much Paul!!!
Does your sample database match the PACP schema? It's looking for 'inspections' and your PACP database table is called 'pacp_inspections'.
You can either rename your table to be 'inspections' (case doesn't matter) or modify the schema to use your table name of 'pacp_inspections'
CCTVProcessorA4W\Maps and GDBs\cctv\schema\PACP v6.0.4\schema.xml
Ok yea that fixed the initial error. I should have caught that but thank you Paul!
I'm running into another error though. Sorry, I'm not sure how to look through the script and debug it myself. I think there is any issue with the save_to_disk function. Not sure why I'm getting this error with my own database and not the sample.
Start Time: Monday, September 11, 2017 10:23:31 AMRunning script CreateConditionPoints...Traceback (most recent call last): File "<string>", line 442, in execute File "C:\_MyTools\CCTVProcessorA4W_Preview_RC1\CCTVProcessorA4W\Maps and GDBs\cctv\cctv.py", line 433, in save_to_disk target=table_names[self._inspection_table.lower()])KeyError: 'pacp_inspections'Failed to execute (CreateConditionPoints).Failed at Monday, September 11, 2017 10:23:34 AM (Elapsed Time: 3.59 seconds)
Steven,
Are you using a PACP v7 schema? The code is incorrectly guessing that 'Direction' is the Inspections ID field. If you change that 'InspectionID' or similar, it should work.
Can someone please help me out? I'm trying to use the tool and keep getting this error:
I tried using the sample data and it worked. I've compared the field types in my PACP Database with the sample data and they are identical. Is there something I'm missing??
That library is required to use the tool. That is why you are getting the !
Python toolbox is not loading for me. I talked with my IT Dept about downloading that Access Database Engine x 64-bit because I am thinking this is my issue. They informed me not to do this as we are running 32 bit. Is there a work around for this? I cannot tell if I am experiencing another issue since I am unable to download the 64 bit Access Database Engine.
Thanks!
At the moment, only an access database is support as an input type. Is your data in an Access Format? If so, select custom and then fill out the parameters. As for how to get a custom item in the drop down, we have not typed those instructions up.
Paul93
... I'm expecting instructions for the Custom format (I saw it ask for Access database, but by default the data are in XML) now ..
Great, at least we have some nice troubleshooting steps logged for the next person. Thanks!
Finally! I really don't know what was it. Actually I download it again, extract it, open ArcGIS Pro ... didn't work, then remove it and add it again and ...BOOM!
One other thought, this PYT requires the cctv folder, all the logic is in there, the pyt is just a shell that loads from there. Can you make sure the folder structure looks like this?
* Mine is not loading as I do not have ODBC install
Can you make sure the PYT is valid, can you download it again. If right clicking will not let you edit it, something else is going on. Let me download it also to ensure it did not get corrupted
same
Aangemelde leden kunnen berichten plaatsen, updates volgen en meer. Nieuw hier? Registreer een gratis account.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
