Where: web portal, Add job on the dashboard.
When you finish: you have a job on your list and you know how to tell whether its Katapult import actually started.
A job is the container your crews work inside. Everything they capture belongs to one.
Create it
On your dashboard, choose Add job, or Create your first job if you have none yet. It is not in the side menu.
Pick how to start it (table below).
Follow the steps. For a Katapult job, configurations made from that job's Katapult model are listed first; pick one of those. The last step confirms what you are about to make.
Create. For a Katapult job this also starts the import.
You return to the dashboard, not to the new job. Open it from your list.
Start a job | When | Steps you will see |
Import from Katapult | Your poles live in Katapult. Recommended if you use it. | 4 if your Katapult key is stored, 5 if it is not (the extra step asks you to connect to Katapult) |
Create blank job | Crews add everything on the map themselves | 3 |
Import from KML | Your data arrives as KML, KMZ or GeoJSON | Takes you into the map-file import instead; see Bring your map file in as a job |
If Cloneable asks you to connect to Katapult, your organization has no Katapult key stored yet. See Store the credentials your integrations need. Once a key is stored, the wizard skips that step and lists your Katapult jobs. If they load, the key works.
Need a configuration you do not have? Build it before you start the job. Leaving the wizard part-way loses what you entered.
Read the message when it finishes
A Katapult job can be created successfully while its import fails to start. Cloneable tells you, but every message has the same title, "Job created". Read the line under it.
You see | It means | Do this |
Job created, with "Bringing the Katapult job into Cloneable. Large jobs can take a few minutes." | The job exists and, for Katapult, the import started | Open the job when the poles arrive |
Job created, with "The import from Katapult didn't start. You can run it from the job later." | The job exists and is empty | Tell us before sending a crew out |
Job created, with "This configuration has no import trigger, so nothing came in from Katapult. You can run an import from the job later." | The job exists and is empty. The configuration you picked is not set up to bring jobs in from Katapult | Tell us before sending a crew out. Next time, look for the Import trigger tag on the configuration in the last step |
If poles never arrived and you are not sure which message you saw, treat it as the second one until proven otherwise.
If you ticked more than one Katapult job, you see one message for the whole batch instead, for example "3 imports started". Any job whose import did not start is listed so you can retry it.
If something goes wrong
Problem | Do this |
The wizard shows "Katapult jobs couldn't be loaded." with Try again | If Try again gives the same message, your Katapult key is not working. See "Error loading jobs" when I import from Katapult |
Creating the job itself fails | It shows in the wizard, so you will not miss it. Try again; if it keeps failing, tell us the name you gave the job. |
Related