Skip to the content.

Creating Students

Students - a point feature class

The student point feature class is created by geocoding a table of student information to a street centerline layer, address point layer or other reference data typically used for geocoding. When geocoding students to street centerlines, it is important to use offset parameters to be sure that student points are not placed directly on a street and they fall within a distinct study area and attendance boundary. It should be noted that in order to effectively develop enrollment forecasts, you will need a minimum of three years (preferably four years) of geocoded students all extracted from the SIS at, or close, to the same date each year. That date is usually the fall reporting period each year for fall-generated forecasts.

Source:

This data comes directly from the District’s student information system (SIS) and is downloaded in one of the following formats and imported into a geodatabase table ready for geocoding. The downloaded data should be exported from the SIS into either Excel (.xlsx), comma or tab-delimited text (.csv) or dbase (.dbf).

Required Fields:

There are three required fields that must be added to the geocoded student attribute table in order for SchoolSite Pro to properly identify students to be excluded or optionally included in the enrollment forecasts or various types of redistricting plans.

  1. GRD - This field is defined in ArcGIS as a “Short Integer” or “Long Integer” field and should only contain numeric values, typically ranging from 0 through 12, and sometimes -1 and/or -2. 0 represents kindergarten, -1 or -2 would represent TK or PK (see discussion below). The District’s student data downloaded from the SIS may include a Grade or other named field, but the values in that field many times include characters other than numbers such as KA or KP, PK, or some other value of the District’s choosing. This type of data is not recognized for use with SchoolSite Pro and those values must be transferred or interpreted to include only numeric values in the GRD field. The GRD field with standardized grade values is critical to both the forecasting model and redistricting plans.

  2. SCHL_CODE - This field is defined as a “Short Integer” or “Long Integer” and contains the school ID or program ID number of the student’s school or program of attendance. It is critical that the ID number in the student table matches a corresponding point with the school ID in the schools point feature class (i.e. there needs to be a location where the student is attending school).
    • Student cannot have 9999 in the SCHL_CODE field
    • Students cannot be coded to school code 0. For example, a student cannot have SCHL_CODE = 0.
  3. STUTYPE - This field is used to identify certain types of students that will be excluded or optionally included in the enrollment forecast model as well as students that will be excluded from boundary planning (i.e. a particular group of students don’t move during a boundary change). The STUTYPE field is defined as a “text” field of 2 characters in length.

STUTYPE Field Explained:

The STUTYPE field contains numerous two-letter code values to identify and standardize various types of students, whether they are special education, pre-kindergarten, home study, etc. The reason these students are identified with a STUTYPE code is because certain students may or may not take classroom space which is relevant to the discussion of forecasts and facility needs, and in other instances certain types of students may need to be identified as not being moved in certain redistricting scenarios (i.e. special day class in self-contained classrooms).

Student type classifications are prioritized where some student classifications take precedence over others. This can happen when a student can be classified under two or more different codes. For example, if a student lives outside the district but is also a special education student.

It is also critical that STUTYPE classifications be consistent between different year’s student geocoded data. If certain students are being excluded in development of enrollment forecasts from the most current student data file, those same students, based upon the codes, will be excluded from previous years in the forecast calculations. The mathematical calculations in the forecasts may be in error if there is no consistency in coding different student types from year to year.

The two-letter STUTYPE codes used by SchoolSite Pro are explained below and are listed in order of precedence for coding each student record:

How Classification Codes are used in SchoolSite Pro Redistricting Plans:

There are three types of redistricting plans that can be created in SchoolSite Pro:

  1. Plan by Current Resident Students
  2. Plan by Projected Resident Students (i.e. forecasted students)
  3. Plan by Current Resident and Enrollment

There are slight variations in how classification codes are used in creating each type of plan.

Current Resident Students Plan

During setup for Current Resident Students, non-K12 students as well as the following classes of students are automatically excluded from boundary planning as well as reporting in the plan statistics window: AD, NP, AE, HH

During setup for Current Resident Students, in addition to students coded as GE, you have the option of including the following classes of students: CH, OT, SE, and IS.

Including any of these five classes of students will involve those students being moved during the boundary planning process and they will be included in the statistics window under the appropriate grade levels.

Projected Resident Students Plan

The students moved as well as reported in the statistics window are those that were included or not included by choice in the development of the enrollment forecasts being referenced in the plan. For example, if special education students were excluded from the forecasts, they will not be in the forecasted numbers used in the boundary plan.

Current Enrollment Plan

During setup for plans based upon Current Enrollment, the software will determine which students are outside the District (OD) or non-geocoded (UM). Those students will not be moved during the boundary planning process. In the statistics window non-resident and unmatched students will be listed by their school of enrollment under a separate OD_UM column. Of the remining geocoded students residing in the District, those students outside of grades -1 through 12 are automatically excluded from the boundary planning process but are reported with their enrolled school under the Non_PK12 column in the statistics window.

Once the non-resident, unmatched and non-PK12 students have been identified, you have an option to choose a field in your student data to identify which of the remaining -1 through 12th grade students you may wish to exclude from boundary planning and reporting. The default field is STUTYPE. Using the STUTYPE field, you have the option of excluding any of the remaining classes of students, such as SE, OT, IS, CH, etc. For those that you choose to exclude, they will not be moved during the boundary planning process, however, they will appear as part of the enrollment at their school under a separate column in the statistics window similar to Non_PK12 and OD_UM.

If you choose not to exclude them from boundary planning, they will be treated as a regular student and will be subject to moving during the boundary planning process and will be reported under the appropriate grade level in the statistics window.

If you choose an optional field other than STUTYPE to identify classes of students, you can create any classification codes you wish to identify students to be excluded from the boundary planning process. The out of District, unmatched and non-PK12 tests will still be performed, but you are provided unlimited flexibility as to how to code and select the remaining resident PK/TK through 12th grade students for boundary planning. For example, you could code a group of students in a specific program such as dual language program offered only at specific schools to be excluded from the boundary planning process so they remain at the program school. Or you may choose more specific codes for handling special education classes.

How Classification Codes are used in SchoolSite Pro Enrollment Forecasting:

There are essentially two types of forecasts that can be created in SchoolSite Pro: student residence and optionally school of enrollment.

The standard forecast model within SchoolSite Pro includes forecasts by residence at the study area level. Utilizing those forecasts by residence is the basis for setting up any redistricting plans based upon Forecast Resident Students. So if there are any students excluded from a forecast based upon a STUTYPE classification, those same students will be excluded from any Forecasted Resident Student redistricting plan.

An option is available to create school of enrollment forecasts (i.e. staffing forecasts) which are derived from the resident forecasts.

Resident Forecasts

The use of the STUTYPE field and the classification of students for creating a resident forecast operates similar to the setup of a redistricting plan using resident students.

During setup for resident forecasts, grades -1 through 12 are automatically included for forecasting and the following classes of students are automatically excluded from the forecast calculations as well as any reports based upon the forecasts: AD, NP, AE, HH

During setup for resident forecasts, in addition to grades -1-12 GE students, you have the option of including the following classes of students: CH, OT, SE, and/or IS. If you include these students they will be incorporated in the forecasts along with all other students at their appropriate grade level. If you choose not to include them, they will not appear in the forecasts or any reports.

School of Enrollment (Staffing) Forecasts

Because school of enrollment forecasts are based on the underlying resident forecasts, the decisions you make about including or excluding students for your resident forecasts carry over into the school of enrollment forecasts. For example, excluding special education (SE) from your resident forecasts excludes them from school of enrollment forecasts. There are a few exceptions in that out-of-district and unmatched students are included in the school of enrollment forecasts. To learn more about how school of enrollment forecasts are calculated, see the following help topic.

Davis Demographics’ Student Type Classifications in order of priority:

Student Types used in Redistricting Plans (for students with grades -1 through 12)

Code Student Type Plans by Residence Plans by Enrollment Plans by Projected Students
NP Non-public student Excluded Included Excluded
AD Adult education Excluded Included Excluded
AE Alternative education student Excluded Included Excluded
HH Home/hospital student Excluded Included Excluded
OT Other student Optional Included *Inherited
CH Charter school student Optional Included *Inherited
IS Independent school student Optional Included *Inherited
SE Special education student Optional Included *Inherited
GE Resident K-12 student Included Included Included

*Inherited indicates that student type will be included if the residential forecast included that optional type during setup.

Student Types used in Forecasts (for students with grades -1 through 12)

Code Student Type Resident Forecasts Staffing Forecasts Mobility Calculation
NP Non-public student Excluded Excluded Excluded
AD Adult education Excluded Excluded Excluded
AE Alternative education student Excluded Excluded Excluded
HH Home/hospital student Excluded Excluded Excluded
OT Other student Optional *Inherited **Included
CH Charter school student Optional *Inherited **Included
IS Independent school student Optional *Inherited **Included
SE Special education student Optional *Inherited **Included
GE Resident K-12 student Included Included Included

*Inherited indicates that student type will be included if the residential projection included that optional type during setup.

**Mobility is calculated with all available student data to ensure the largest sample size possible and consistency year over year.

Suggested Additional Fields:

The District will have to decide what information would be most useful in your planning efforts. The more information on the file, the more alternatives you will have to query and graphically display your student data. You may want to include additional attributes such as:

Excluding students from the redistricting process:

During the creation of a plan by current students and current enrollment you will be asked to select a field from which you can choose one or more categories of students that can be excluded from the redistricting process. The identified students will remain at their current school of attendance regardless of any boundary changes. These students usually belong to a campus specific program (special needs, magnet school,academy, etc.)

Points to Remember:

For More Information:

Students must be geocoded by residence in order to perform redistricting and to obtain realistic forecasts (using the SchoolSite Pro Forecast Extension). For more information on how to geocode, see the ArcGIS help file or the Getting to Know ArcGIS manual.