CCTV Managerが利用可能になりました！最新情報はArcGIS Solutions for Water<\/A>からご覧ください。<\/SPAN><\/PRE><\/P>これまでに、CCTV Processor<\/A>ソリューションについて多くの素晴らしいフィードバックをいただいています。 このソリューションをご存じない方のために説明すると、これはArcMap用のジオプロセシングツールで、NASSCO PACP標準バージョン6の閉回路下水道ビデオ検査データをインポートします。 検査および状態テーブルは、それぞれの観察点ごとにポイントに変換され、調査されたメインラインはラインとして変換されます。 観察画像や写真も添付ファイルとして読み込まれ、データをサービスとして公開し、組織内の誰でもCCTVデータにアクセスできるようにします。 このソリューションは、CCTV調査中に収集された豊富な情報を解放するものです。<\/SPAN><\/P><\/P>他のインポートタイプや新しいPACP v7への対応を求めるユーザーからの要望により、CCTV Processorを強化する時期だと判断しました。<\/SPAN><\/P><\/P>1:<\/STRONG><\/SPAN> Model BuilderからPython Toolboxへの移行： <\/STRONG><\/SPAN>Model Builderは複雑なプロセスを定義するのに優れていますが、より高速で使いやすく、安定したツールをPython Toolbox<\/A>を使って構築しました。 <\/SPAN><\/P><\/P><\/P>2: ArcGIS Pro向けに設計：<\/STRONG><\/SPAN> 今後のUtility Network対応とジオメトリックネットワークで表現されたデータをサポートするために、CCTV ProcessorをArcGIS Proへ移行しました。 これによりコードも簡素化され、より高速かつ信頼性が向上しました。<\/SPAN><\/P> <\/SPAN><\/P>3: BUG-000104129の解決：<\/STRONG><\/SPAN> 現在のツールは複数の調査によるパイプ上の観察ポイントには問題なく動作しますが、一つだけ修正が難しかった問題がありました。 パイプが複数回調査された場合、一つの検査ラインセグメントしか作成されませんでした。 新バージョンではこのバグが解決されています。<\/SPAN><\/P> <\/SPAN><\/P>4: 複数入力スキーマのサポート：<\/STRONG><\/SPAN> 今回のアップデートでPACPV6.0.4以外にも対応可能になりました。 PACPV6.0.4、PACPV7.0.7、およびカスタムから選択できるオプションが提供されます。 PACPV6または7を選択するとツールの他のパラメーターが自動入力されます。 カスタムを選択した場合はこれらのパラメーターを入力にマッピングする必要があります。 さらに追加スキーマをオプションリストに加えることも可能です。この手順についてはリリース時に詳細を説明しますが、試してみたい方はコメントを投稿してください。手順をご案内します。<\/SPAN><\/P><\/P><\/P><\/P><\/P>新バージョンを気に入っていただければ幸いです。 これは最初のプレビューに過ぎません。 メッセージやリンク変換など全ての機能はまだ移行していません。 <\/SPAN><\/P> <\/SPAN><\/P>また、テスト用に皆様のCCTVデータも募集しています。 もしPACPV7エクスポートや他のスキーマをお持ちで共有してもよろしければ、100%機能することを確認するためにぜひテストさせてください。<\/SPAN><\/P><\/P><\/P>Proで始めるCCTV<\/STRONG><\/SPAN><\/P>いくつかインストールが必要なものがあります：<\/SPAN> 1. <\/SPAN> Microsoft Access Database Engine 2010 Redistributable<\/> </ P>ArcGIS Proは64ビットアプリケーションなので、x64バージョンを選択してください。2. pyodbc</ P>これはPython Package Manager</ A>から簡単にインストールできます。インストール後ArcGIS Proがクラッシュする場合はこちらのGeoNet投稿</ A>をご覧ください。画像はバージョン 3.0.10 を示しています。PYODBC バージョン4もサポートされています。4.0.17 はRC2でテスト済みです。 </ P></ P>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;&</ P>ArcGIS for Utilities</ P><\BODY></ HTML>
<\/P>
これまでに、
他のインポートタイプや新しいPACP v7への対応を求めるユーザーからの要望により、CCTV Processorを強化する時期だと判断しました。<\/SPAN><\/P><\/P>1:<\/STRONG><\/SPAN> Model BuilderからPython Toolboxへの移行： <\/STRONG><\/SPAN>Model Builderは複雑なプロセスを定義するのに優れていますが、より高速で使いやすく、安定したツールを
2: ArcGIS Pro向けに設計：<\/STRONG><\/SPAN> 今後のUtility Network対応とジオメトリックネットワークで表現されたデータをサポートするために、CCTV ProcessorをArcGIS Proへ移行しました。 これによりコードも簡素化され、より高速かつ信頼性が向上しました。<\/SPAN><\/P> <\/SPAN><\/P>3: BUG-000104129の解決：<\/STRONG><\/SPAN> 現在のツールは複数の調査によるパイプ上の観察ポイントには問題なく動作しますが、一つだけ修正が難しかった問題がありました。 パイプが複数回調査された場合、一つの検査ラインセグメントしか作成されませんでした。 新バージョンではこのバグが解決されています。<\/SPAN><\/P> <\/SPAN><\/P>4: 複数入力スキーマのサポート：<\/STRONG><\/SPAN> 今回のアップデートでPACPV6.0.4以外にも対応可能になりました。 PACPV6.0.4、PACPV7.0.7、およびカスタムから選択できるオプションが提供されます。 PACPV6または7を選択するとツールの他のパラメーターが自動入力されます。 カスタムを選択した場合はこれらのパラメーターを入力にマッピングする必要があります。 さらに追加スキーマをオプションリストに加えることも可能です。この手順についてはリリース時に詳細を説明しますが、試してみたい方はコメントを投稿してください。手順をご案内します。<\/SPAN><\/P><\/P><\/P><\/P><\/P>新バージョンを気に入っていただければ幸いです。 これは最初のプレビューに過ぎません。 メッセージやリンク変換など全ての機能はまだ移行していません。 <\/SPAN><\/P> <\/SPAN><\/P>また、テスト用に皆様のCCTVデータも募集しています。 もしPACPV7エクスポートや他のスキーマをお持ちで共有してもよろしければ、100%機能することを確認するためにぜひテストさせてください。<\/SPAN><\/P><\/P><\/P>Proで始めるCCTV<\/STRONG><\/SPAN><\/P>いくつかインストールが必要なものがあります：<\/SPAN>
1. <\/SPAN>
</ P>
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;&</ P>
ArcGIS for Utilities</ P><\BODY></ HTML>
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
サインインしたメンバーは投稿、更新のフォローなどができます。初めてですか？無料アカウントを登録してください。
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
