Troubleshooting Drawing Tools

This article pertains to Drawing Tools when error messages are received.  I would hope that if one is encountered that is not on this list that the article can be edited to add the scenario, error, workaround, and specific nuances.  

The remainder of the issues under this section are specific drawing tool scenarios we have encountered.  

Scenario #1: Client orders a corridor study report but still wants to use drawing tools.

Issue: Client placed corridor study report, but then begins working drawing tools immediately. One day they no longer have access and receive this error:

Error: Error 0: ObjectName: Property ValidationKey: PropertyCoverages Message: Property coverages contains one or more invalid data., 1: ObjectName: PropertyCoverage ValidationKey: ReportGUID Message: ReportGUID is required., 2: ObjectName: PropertyCoverage ValidationKey: ReportGUID Message: ReportGUID is required. For error reporting: OrderGUID: 00000000-0000-0000-0000-000000000000 PropertyGUID: 8439d8e1-11b2-40e7-8004-4345f1b394ed Account #: 3530EDR

Here is a workaround to propose to clients who order a radius map product but not a radius map (such as corridor study reports) and want to utilize Drawing Tools. This is a workaround proposed by Thomson in GSD-57905.

Explanation from development angle:

Seems the same issue as the other case. The Historical Aerial data loader ran last and that over-wrote the propertycoverages table (HistoricalAerial/HistoricalTopo/CertifiedSanborn dataloader is using an old format tp.xml and over-writing propertyCoverage table with guid.empty for the other reports). There is a backlog item in dataportal to fix this DATAPORTAL-602

Note: Usually when the order has RadiusMap report which runs last, it would reset propertyCoverage for all reports. This is why we don’t get this error that often. These recent orders does not have RadiusMap. The historical Aerial/Topo reports which as per earlier investigation is using an older format of tp.xml is over-writing the propertyCoverage.reportGuid for all other reports.

Dumbed Down Explanation for Client:

There is a dataloader process that occurs in drawing tools at various points when data is loaded to Drawing Tools. It will run initially for the current aerial/topo, then the dataloader process runs again for the historicals. When this process runs, it is looking for 'propertyCoverage' and unfortunately the corridor study report doesn't have propertyCoverage set on the back end. Since Drawing Tools doesn't see the propertyCoverage, it will throw the error and won't be usable again.

Workaround:

We have a 'fix' that will be provided for this type of scenario in the future but I do not have a time frame on that fix. (DATAPORTAL-602) Development's suggestion is to start the drawings only after the historical imagery are available (Historical Aerial, Historical Topo & Certified Sanborn) in the drawing tools. If you begin drawings nearly immediately after the current aerial/topo are available, that is when you run the risk of having the work you completed disappear.

Seemingly, when this error is received:

Error

0: ObjectName: Property ValidationKey: PropertyCoverages Message: Property coverages contains one or more invalid data., 1: ObjectName: PropertyCoverage ValidationKey: ReportGUID Message: ReportGUID is required., 2: ObjectName: PropertyCoverage ValidationKey: ReportGUID Message: ReportGUID is required.

For error reporting:

OrderGUID: 00000000-0000-0000-0000-000000000000

PropertyGUID: 55ba78d7-50d9-42a3-b7ac-2220296f9558

Account #: 3530EDR

IF THERE ARE EDR PRODUCTS:

Rerun Radius map to get the missing GUIDs

Once radius map is complete and in PARCEL, check drawing tools

If error still persists, rerun aerial/topo and sanborn if available.

Once historicals are rerun, if drawing tools still won’t open, create a GSD to SDG Support and tag Zach Fisk and Anand Ganesan..

IF THERE ARE NO EDR PRODUCTS:

Since it does not have RadiusMap, you won’t be able to re-load lightbox data loader and it will need to be reloaded manually. Create a GSD to SDG Support and tag Zach Fisk and Anand Ganesan.

Knowledge grabbed (from GSD-58250)

If the error is with ‘PropertyCoverage ValidationKey: ReportGUID Message: ReportGUID is required.’, then the root cause is that one of the historical imagery report (Historical Topo/Aerial/Sanborn) is failed.

1. It could be either with an incorrect/invalid address for the TP or some other issue with the imagery report. If the issue is due to invalid address, in that case, radius map also would fail. So, if radius map also failed, check if the property address has any special character or missing the address line 1. After fixing it, we need to re-run the imagery reports and after historical imagery reports are finished, we need to run rad map dataloader.

2. If Radius Map was successful, the historical imagery reports are also available in lightbox → what this means is that the imagery reports took a long time to complete. When imagery reports completes after rad map, there is a defect in the system that the historical imagery data loaders are resetting the reportGUID for VECApp. This causes both draw tool and VEC App to fail. So, if this happens VEC report also fails. In this scenario, we just need to re-run the radius map dataloader (the sets mentioned in GSD-57841). We don’t need to re-run historical reports.

3. Radius map ran successfully. Historical Imagery reports failed. This is what happened with this GSD. We need to first run rad-map dataloader. (this would populate the missing reportGUID in propertycoverages). Once rad map is completed, run historical topo and aerial (and sanborn if available).

What else I have learned (from GSD-57841)

This issue was caused by the very same issue we used to get with VECApp once in a while.

The HistoricalTopo/HistoricalAerial is using an outdated version of tp.xml file. So, whenever HistoricalTopo runs after the other reports, it resets the PropertyCoverages.ReportGuid for all other reports to guid.empty. The current solution is to re-run RadiusMap (or CurrentAerial/CurrentTopo if RadiusMap is not available) Data Loader. More details regarding this temperorary solution is documented in confluence page VEC App Error (or DrawTool Error) with ReportGUID missing or does not exist. Solution is to re-run RadiusMap I think support has a way to re-run reports such as RadiusMap without help from developers - if someone knows those steps, please add it to this confluence page.

Note: We have a story in dataportal backlog to fix this issue permanently by fixing the HistoricalTopo/HistoricalAerial applications to use the latest TP.xml format. DATAPORTAL-602: Lightbox // DataLoader: HistoricalAerial, HistoricalTopo & CertifiedSanborn running after RadiusMap/CurrentAerial is setting NULL reportGUID for PropertyCoverages - causing VEC reports & DrawTool to Fail

Check for Colons in the names of the images & file name duplications

Taken from GSD-66384

1. Figure 3 -Site Plan is listed twice (though the names are slightly different leading item 2)

2. Almost all drawings have a colon in the name. Each figure is essentially named with the label before the colon and thus are not unique and is the root of the failure

I renamed the aerials for 1939 and 1946 by removing the colon. First I attempted to export those two images and it failed, after removing the colon the images printed.

(snip of my output for those two figures)

All figure names should be renamed by removing the colon and watch out for Figure 3, it’s second and last in the list. If they want it to print twice it should be fine, but name needs to be slightly different.