Signing in
Open IQGeo in a tab, or Sign in to IQGeo in a tab
Open IQGeo in a tab, or Sign in to IQGeo in a tab
The extension works through your IQGeo tab. Open IQGeo in Chrome, sign in, and make the IQGeo tab the active one. If your IQGeo session expired, sign in again and click Refresh in the panel.
Sign in to app.cloneable.ai in this Chrome to use your jobs
Sign in to app.cloneable.ai in this Chrome to use your jobs
Sign in to app.cloneable.ai in the same Chrome profile, then click Refresh. The extension uses whichever Cloneable organization your browser is signed in to.
I don't see IQGeo in the extension
I don't see IQGeo in the extension
Check the extension is installed from the Chrome Web Store and up to date.IQGeo appears once Chrome has visited an IQGeo site. If your IQGeo isn’t on an
iqgeo.cloud address, add it under Private servers on the extension’s Home screen and allow access when Chrome asks.Setting up
Read the data dictionary, but not the palette and map styles
Read the data dictionary, but not the palette and map styles
The map in your IQGeo tab hadn’t loaded. Check that IQGeo shows the map and you are signed in, then click Re-read.
Can't create it yet
Can't create it yet
The check found problems before creating anything. Each line says what to change. Nothing was created.
Not created. Anything made on the way was removed
Not created. Anything made on the way was removed
Something failed partway through. The extension removed everything it had made, so you can run Step 3 again safely.
Someone else needs to set up, but they don't have IQGeo
Someone else needs to set up, but they don't have IQGeo
Setup reads IQGeo’s forms from the signed-in IQGeo tab, so it must be done by someone with IQGeo access and a Cloneable account that can manage configurations. Once it exists, everyone in your Cloneable organization can use it.
Bringing a scenario in
Select the scenario in IQGeo first
Select the scenario in IQGeo first
Click the scenario’s outline or title on IQGeo’s map. Its name appears under Scenario in the panel.
Scenario has no boundary in IQGeo
Scenario has no boundary in IQGeo
The extension brings in what’s inside the scenario’s boundary. Ask your design team to add a boundary to the scenario in IQGeo.
Nothing of the ticked kinds is inside this scenario
Nothing of the ticked kinds is inside this scenario
Tick more feature types under What to bring in, or check you selected the right scenario.
Some features failed
Some features failed
Failed features are listed with the reason. Click Retry the ones that failed. If a span fails because its pole isn’t in the import, update the extension: version 2.2.1 brings in poles just outside the boundary for spans that cross it.
Sending to IQGeo
This job's configuration wasn't made from IQGeo
This job's configuration wasn't made from IQGeo
Only jobs that use an IQGeo configuration can be sent. Bring the scenario in from the From IQGeo tab to get one.
Not sent: outside the scenario, or not in this scenario
Not sent: outside the scenario, or not in this scenario
Sending is limited to the job’s scenario. Move the feature inside the boundary in Cloneable, or ask your design team to adjust the scenario.
Held back
Held back
A feature is missing something IQGeo needs, such as pole height. The review lists each group with how to fix it and links to the objects in Cloneable. Fix them and click Refresh.
Stopped at a batch, or an interrupted send
Stopped at a batch, or an interrupted send
The send stopped partway, for example because the IQGeo session expired. Nothing after the stop was sent. Sign in to IQGeo again, click Refresh, then Send to continue from where it stopped. Nothing is sent twice.
IQGeo is busy, waiting
IQGeo is busy, waiting
IQGeo asked the extension to slow down. It waits and retries on its own. Keep the tab open.
IQGeo refused the request as too large
IQGeo refused the request as too large
Nothing in that request was saved. Send fewer photos at a time, or contact us to lower the batch size.
How it behaves
- Bringing a scenario in again updates the job’s values from IQGeo. It doesn’t move objects in Cloneable, and it overwrites Cloneable changes to fields that IQGeo also has. Send fielders’ changes before bringing the scenario in again.
- On send, Cloneable wins. Values from the job replace the values in IQGeo.
- Deleting: features that existed in IQGeo before Cloneable are never deleted, only unlinked.
- Moving a pole also moves anything that shares its point and the ends of its paths.