Learn what each of the different Boundary Types are and when to use them.
What's included in this article?
Why are there different Boundary Types?
The Boundary Type selector exists so that uploaded boundaries can be categorized according to what the boundary is used for. This also determines where in Enroll the boundaries can be selected and used.
For example, a district boundary will appear at the School Group level and is used to define a boundary for the entire zone where all schools are located.
What are the different Boundary Types?
District Boundary
District Boundaries will be selected when importing a boundary file that outlines the entire district, not the schools in the district. District Boundaries are selectable in the School Group and in the Student Address condition in the rules engine.
You can see the difference in the images below. The district boundary outlines the entire district rather than each of the individual school zones that make up the district.
District boundaries should be used when there are rules that dictate whether students can apply or register based on their location inside or outside of the district.
For example, if you have a rule that students can only apply to your schools if they live within your school district, you would want to import this type of boundary. This will allow the boundary to be selected at the School Group level and then used in a rule to prevent out of district students from applying.
School Zone
The School Zone boundary type will be selected when importing individual school zone boundaries. These are the most common type of boundary that will be imported into Enroll. School Zone boundaries are selectable in individual school settings and in the Student Address condition in the rules engine.
School Zones should be used when there are rules that dictate whether students can apply or register based on their location inside or outside of a specific school zone.
For example, if students are allowed to directly register to the school they are zoned for but are not allowed to register at any other schools, you would import these boundaries as a School Zone boundary type and then select the boundaries for the appropriate schools in school settings then create corresponding rules.
Priority Zone
Similar to the School Zone boundary type, the Priority Zone boundary type will be selected when importing individual zones that determine whether students receive a specific priority for the lottery. Priority Zones are only selectable in the Student Address condition in the rules engine. They are not directly assigned to any schools or groups.
Priority Zones should be used when there are rules that dictate whether students are eligible for a priority based on their address.
For example, a lottery has priorities based on zip codes found within the district. Students who live within a specific zip code are given priority in the lottery because they live within that zip code. Priority Zones would be imported for all of the qualifying zip codes and used in priority creation.
Other
This option is similar to the Priority Zone type and is used to create a custom category for grouping and organization of boundaries. They are not assigned to School Groups or Schools but can be used in the Student Address condition of the Rules Engine.
Common Use Cases for custom categories: Grouping Transportation Zones, Grouping Census Tract Zones
Comments
0 comments
Article is closed for comments.