Skip to main content
All CollectionsUsing the Platform
Understanding Limitations of Uploaded Project Areas
Understanding Limitations of Uploaded Project Areas

To ensure data accuracy and prevent unintended project configurations, Orbify Platform limits the density of uploaded polygon project areas. This article explains why this limitation exists and how it works.

Michał Wieczorek avatar
Written by Michał Wieczorek
Updated this week

When creating project areas in Orbify Platform, you can upload multiple polygons as a single project. However, to ensure data accuracy and prevent unintended project configurations, we have implemented a density limitation on the uploaded polygons.

Why this limitation exists?

We allow multiple polygons to be uploaded as a single project area to provide flexibility in defining your areas of interest. However, uploading polygons that are very far apart can lead to several issues:

  • Inaccurate Data Analysis: Combining data from geographically distant areas with potentially different environmental conditions can produce misleading results and inaccurate insights.

  • Difficult Navigation: Navigating to individual, small polygons on a zoomed-out map (required to view the entire project area) can be challenging.

  • Unintended Project Configurations: Users may unintentionally create projects consisting of areas that are very far apart, leading to incorrect data analysis and reporting.

To address these potential issues, we have implemented a density limitation that ensures the uploaded polygons are "dense" enough to be considered a single, cohesive project area.


Technical details

The limitation is based on the ratio of the combined area of all the polygons within a project to the area of the bounding box that encompasses all the polygons.

The formula for this calculation is:

Density Ratio = (Combined Area of All Polygons) / (Area of Bounding Box)

To be considered a valid project area, the density ratio must be greater than 0.001.

What This Means in Practice

If the combined area of your polygons is significantly smaller than the area of the bounding box that surrounds them, you will not be able to upload them as a single project area. This typically occurs when the polygons are very far apart and/or have a small combined area relative to the overall area they cover.

How to Resolve This Issue

If you encounter this limitation, we recommend the following solutions:

  1. Create Separate Projects: Divide your project area into smaller, more cohesive areas and create separate projects for each.

  2. Group Related Projects in a Portfolio: If the projects are related, you can group them together in a portfolio to maintain organisational structure.

  3. Consider the Data Implications: If you still want to upload the polygons as a single project area, be aware of the potential for inaccurate data analysis and misleading insights.

Conclusion

We have implemented this limitation to ensure data accuracy and prevent unintended project configurations. By understanding the reasons behind this limitation and the technical details involved, you can create project areas that provide the most accurate and useful data for your needs.


Did this answer your question?