Creating Partitions
Partition polygons must already exist and be accessible from a datastore before partitioning can be used in a session in 1Integrate.
They must exist as geometric features in a single class within your datastore. Suitable Partition polygons may already exist or they can be created in a separate 1Integrate session and committed to a datastore, or created using other tools
Best Practice Tips
For best performance its a good idea to have partition polygons that:
- are compact in shape (more like squares than long thin shapes)
- have similar number of features inside them (so dense urban areas should have smaller partitions that sparse rural areas)
- have no gaps between them
- cover all the data you want to process