[Components](https://oods-foundry.com/components) / viz.spatial

# GeoFieldMappingForm

Maps record fields to geographic coordinates and identifiers.

Generated from @oods/foundry 0.10.1

- Categories

  viz.spatial

- Contexts

  form

- Readiness

  `react-and-vue`

## Playground

This component's contract doesn't list typed props, so the playground shows its documented example.

Documented example `GeoFieldMappingForm` : mount and declared input triggers, A labelled Input/Checkbox recipe emits the complete typed field mapping on each edit, resynchronises authored values, and prevents native navigation. Embedded forms use a fieldset to avoid nested forms; field mapping does not geocode data..

The render follows the page's theme switch: light, dark or high contrast. Both frameworks render the same example.

The real GeoFieldMappingForm, live

React

Vue

Events it emits: change. Use either render above, and each event shows here with the framework that sent it.



## Code

The documented example. HTML is the markup the React component renders for it, which @oods/component-styles styles.

**React**

```
import { GeoFieldMappingForm } from '@oods/components-react';
import '@oods/component-styles/css';

export function Example() {
  return (
    <GeoFieldMappingForm
      latitude="lat"
      longitude="lon"
      identifier="country"
      autoDetect={false}
    />
  );
}
```

## Props, slots and events

Contract version 1.1.0. Types are from the React declarations in @oods/components-react.

Props

| Prop | Type | Required | Documented example |
| - | - | - | - |
| `title` | `string \| undefined` | no | |
| `latitude` | `string \| undefined` | no | `lat` |
| `longitude` | `string \| undefined` | no | `lon` |
| `identifier` | `string \| undefined` | no | `country` |
| `autoDetect` | `boolean \| undefined` | no | `false` |
| `embedded` | `boolean \| undefined` | no | |
| `disabled` | `boolean \| undefined` | no | |

### Slots

none

### Events

change

## States

editing, disabled

## Accessibility

- Role

  `textbox`

- How it gets its name

  `label` on `input[type="text"]`

### Keyboard

Keyboard

| Key | What it does |
| - | - |
| `Tab` | Focus the labelled native field |
| `x` | Edit the field name |
| `` | Toggle automatic detection |

### Obligations in the contract

- Visible text explains the declared trait values
- Every native control has a visible label

A labelled Input/Checkbox recipe emits the complete typed field mapping on each edit, resynchronises authored values, and prevents native navigation. Embedded forms use a fieldset to avoid nested forms; field mapping does not geocode data.

## Tokens

The token roles this component reads.

- `surface.panel`
- `text.body`
- `focus.outer`

## Readiness

The evidence recorded for this component, with its label.

`react-and-vue`: catalog_list gives this label when the React and Vue components have complete readiness evidence, but the sweep's generated apps don't use the component in both.

Readiness evidence

| Evidence | React | Vue |
| - | - | - |
| state | implemented-evidence-complete | implemented-evidence-complete |
| versioned contract | passed | passed |
| target implementation | passed | passed |
| package export | passed | passed |
| public declaration | passed | passed |
| dependency closure | passed | passed |
| framework scenario | passed | passed |
| accessibility | verified | verified |
| interaction | verified | verified |
| visual themes | verified | verified |

## Use your own

You can replace this component with your own React or Vue component. Map it, and generated code imports yours at the exact version you name. A contract report, run in a real browser, lists what your component met, what it didn't, and what wasn't checked.

The `component_map` call, with the parts in angle brackets yours to fill:

```
{
  "action": "create",
  "apply": true,
  "externalSystem": "<your design system>",
  "externalComponent": "<YourGeoFieldMappingForm>",
  "oodsTraits": [
    "Geocodable"
  ],
  "substitution": {
    "component": "GeoFieldMappingForm",
    "react": {
      "package": "<your-package>/react",
      "version": "<exact version>",
      "export": "<YourGeoFieldMappingForm>"
    },
    "vue": {
      "package": "<your-package>/vue",
      "version": "<exact version>",
      "export": "<YourGeoFieldMappingForm>"
    }
  }
}
```

## How this page was made

Generated at build from the published data, each source with the hash of what was read. [The page's manifest](https://oods-foundry.com/components/geo-field-mapping-form/manifest.json).

- **Contract**: `@oods/component-contracts@0.10.1 componentContracts.GeoFieldMappingForm` `sha256:2079a4ee359d…`
- **Documented example**: `@oods/component-contracts@0.10.1 sharedScenarios GeoFieldMappingForm` `sha256:9bcb963a1d9d…`
- **Catalog entry (catalog_list)**: `generated/0.10.1/system/catalog.json GeoFieldMappingForm` `sha256:9dcae43c32a4…`
- **React readiness**: `@oods/components-react@0.10.1 readiness GeoFieldMappingForm` `sha256:7f0330946015…`
- **Vue readiness**: `@oods/components-vue@0.10.1 readiness GeoFieldMappingForm` `sha256:f948649f24a5…`
- **Prop types**: `generated/0.10.1/components/prop-types.json GeoFieldMappingForm` `sha256:9da98e1c0474…`