# Setting up a project

> Four wizard steps — name, coverage area, coordinate system, elevation — and your dashboard tracks where you are.

Source: https://geodb.io/guide/topic/project_setup/ · Category: Getting set up
A project is the working unit of geoDB: one deposit, one property, one
campaign — your call. Everything you import, map, log and share happens
inside a project.

## Use the setup wizard

The **project setup wizard** walks you through four steps: the project's
**name and reference CRS**, its **coverage area** (upload landholdings or
draw one), the **working coordinate system**, and **elevation data** for
the area. You don't have to finish in one sitting — your dashboard shows a
setup card with your progress and takes you back to the next step whenever
you're ready.

## The two decisions worth a minute of thought

- **Coordinate reference system (CRS).** Tell geoDB what grid your incoming
  coordinates are in — a UTM zone, a state plane, or plain latitude and
  longitude. geoDB keeps your original values exactly as imported *and*
  a converted copy for maps and 3D, so nothing is ever lost — but the
  import can only be right if the declared grid matches the data. The
  *Coordinate systems* topic below covers this properly.
- **Units.** Metres or feet, for depths and elevations, set in project
  settings. Pick what your logging and survey data actually use.

Both can be revisited later in project settings, but getting them right on
day one means never wondering why holes plot in the wrong hemisphere.

## After the wizard

The dashboard fills in as data arrives. Three early wins worth doing next:
bring in your **land holdings**, request **topography** for the project
area, and **invite your team** — each has its own guide topic below.