What you will make

A file-geodatabase polygon feature class for planning sites, with fields for a short ID, place name, and review status.

A geodatabase feature class is a structured dataset for one geometry type and spatial reference. Creating one with clear fields gives planning data a stable home and avoids starting each edit in an exchange format with fewer data-management capabilities.

• Create a feature class in a geodatabase.
• Choose geometry, fields, and spatial reference deliberately.
• Create and save simple features, then inspect the output table.

Work through the method

1. Choose what one row represents

   Decide whether each record is a site boundary, building footprint, road segment, or destination point. A feature class stores one geometry type, so do not mix points and polygons in the same class.

   Check your work: Write one sentence describing one record and its geometry.

2. Create the dataset

   In Catalog, right-click the project geodatabase and choose New > Feature Class. On Define, name the class and choose Point, Polyline or Polygon. On Fields, add the attributes. The Spatial Reference page follows Fields; choose a suitable known coordinate system there. Planning the CRS beforehand is different from the wizard page order.

   Check your work: The output location is the .gdb, and the geometry type matches your record definition.

3. Define fields

   Add a short text ID and only the fields needed for the planning question. Choose text, integer, or decimal data types to match the values. Use an alias for a readable label and allow nulls when a value may genuinely be unknown.

   Check your work: Field names are unique, data types fit, and no unknown is being replaced with zero.

4. Finish and add to map

   Complete the wizard and add the new feature class to the active map. Open Fields view or the attribute table to confirm the schema. Geodatabase feature classes have required geometry and object identifier fields created for them.

   Check your work: The empty class appears under the correct geodatabase and has the intended fields.

5. Create a few features

   Use Edit > Create Features, select the layer's template, and draw a few practice polygons within the supplied boundary. Enter an ID and place name for each. Save edits from the Edit tab.

   Check your work: The shapes draw, the table records match them, and edits are saved.

6. Check what you made

   Inspect the map and table together. Confirm the coordinate system, geometry, and attributes. If you need an exchange copy, export it separately rather than replacing the working geodatabase class.

   Check your work: The feature class can be reopened from the geodatabase and its records are legible.

Build a small reuse-sites layer

1. Create a polygon feature class inside the project geodatabase.
2. Add Site_ID, Place_Name, and Review_Status fields using suitable data types.
3. Digitize three practice sites from supplied boundaries or a clearly labeled illustrative base.
4. Save edits and export a screenshot or table for review.

Bring the method into a product

• Saved geodatabase feature class in the project
• PNG map view or CSV attribute table

Suggested formats: GDB, PNG, CSV.

Reflect: Which attribute should remain blank rather than be guessed when a site record does not provide it?

Avoid these mistakes

• A feature class stores one geometry type; related point and polygon data belong in separate classes.
• Choosing the wrong source coordinate system can place or measure new features incorrectly.
• Do not interpret an empty field as zero or a confirmed negative finding.