QP 7.05.22 IKE Import Bug Fixes
Posted: Thu Aug 06, 2026 10:49 am
This update resolves a couple of bugs that users have reported when doing imports of IKE JSON files.
1) Datum/Zone not recognized.
2) Span Profiles not looking correct as attachment heights on one end are off.
Note: Elevation issues were corrected back in version 7.05.20.
The first issue has been resolved.
The second issue has largely been corrected in that it now works the same way as it did previously. This requires a bit of explanation in how Quick Pole imports IKE files.
IKE handheld units and IKE office can be used to create spans of attachments in one fundamental direction, one pole at a time. This saves time in the field and in the office, if Quick Pole can deal with the data this way. To that end, Quick Pole will attempt to match the height of attachments coming into a pole with those that are leaving the pole. The algorithm that Quick Pole uses will work well when the same number of attachments arrive and leave a pole. It is imperfect when this is not the case and will require some manual adjustment. This is generally easy to recognize and is much quicker to do for the odd poles in this situation, than entering more data in IKE Office and additional functions in the field.
The best way, but less efficient, is to copy forespan to backspan in the handheld unit, or similar process in IKE Office. This ensures that the JSON actually has attachment heights recorded for each end of the spans for all attachments. This method is supported in Quick Pole and is always absolutely perfect from a data perspective. It comes at an efficiency cost though. A lot of customers use the above method that records data in one direction only. This method needed an adjustment in this update to work like it did before.
1) Datum/Zone not recognized.
2) Span Profiles not looking correct as attachment heights on one end are off.
Note: Elevation issues were corrected back in version 7.05.20.
The first issue has been resolved.
The second issue has largely been corrected in that it now works the same way as it did previously. This requires a bit of explanation in how Quick Pole imports IKE files.
IKE handheld units and IKE office can be used to create spans of attachments in one fundamental direction, one pole at a time. This saves time in the field and in the office, if Quick Pole can deal with the data this way. To that end, Quick Pole will attempt to match the height of attachments coming into a pole with those that are leaving the pole. The algorithm that Quick Pole uses will work well when the same number of attachments arrive and leave a pole. It is imperfect when this is not the case and will require some manual adjustment. This is generally easy to recognize and is much quicker to do for the odd poles in this situation, than entering more data in IKE Office and additional functions in the field.
The best way, but less efficient, is to copy forespan to backspan in the handheld unit, or similar process in IKE Office. This ensures that the JSON actually has attachment heights recorded for each end of the spans for all attachments. This method is supported in Quick Pole and is always absolutely perfect from a data perspective. It comes at an efficiency cost though. A lot of customers use the above method that records data in one direction only. This method needed an adjustment in this update to work like it did before.