Define A Processing Area In Pix4D Cloud By Uploading A .KML File

PIX4Dcloud PIX4Dcloud Feature Request
1

Dear Pix4D Support Team,

I’m writing to express a concern regarding the current functionality in Pix4D Cloud.

In Pix4D Mapper, we have the ability to define a processing area using a .KML file, which provides precise control over the region of interest and significantly improves processing efficiency. However, this option is currently not available in Pix4D Cloud, and it limits the flexibility and control users have over their datasets.

For many projects—especially those involving large datasets or complex survey areas—the ability to import a .KML-defined boundary is essential. It helps reduce unnecessary processing, save credits and time, and ensure consistency with existing project boundaries defined in other GIS tools.

Having this same capability in Pix4D Cloud would greatly enhance its usability and align it more closely with the functionality of Pix4D Mapper. I believe many users who rely on cloud processing for collaboration or scalability would benefit from this addition.

Please consider adding support for .KML-based processing area definition in future Pix4D Cloud updates. I’d be happy to provide additional feedback or examples of workflows where this feature would make a major difference.

Best regards,

Mark Jordan

Skymatics Ltd

2

This is incredibly valuable feedback, Mark. As a UX designer here at Pix4D, I find your request for KML processing area boundaries in PIX4Dcloud to be highly relevant and interesting.

We are seeing strong internal traction focused on our recent Region of Interest (ROI) implementation and overall workflow efficiency. This kind of detailed input is vital; it directly informs and encourages our team’s efforts to iterate and deliver superior value to our existing tools.

Thank you for articulating the need behind the need here. We recognize that your priorities are: Consistency across dataset limits (supporting scalability and GIS collaboration), credit savings (by helping reduce unexpected processing results), and ultimately of course, time efficiency.

We have many things on our product radar, and we are constantly evaluating the many great ideas and feedback we receive. Rest assured that we will thoroughly evaluate this improvement proposal to the existing ROI functionality as we plan future releases. We are fully committed to building a better product, and we truly value this direct interaction and powerful Voice of Customer input.

Thanks!
Best,
Jesus Reyes