Properties that are not mapped to node data and require
to be mapped appear with the following status 
in the list
of properties, and the same status appears on the Nodes tab. This
is the case for the
in the list
of properties, and the same status appears on the Nodes tab. This
is the case for the id property. You must
map it to a column because its values should uniquely identify the
rows. Additional properties that are not mapped to node data
appear with status 
in the list
of properties.
in the list
of properties.To map the id property to the City column:
-
Click the
idproperty. -
Click the
Citycolumn.You can map other properties as required.
In this example, you have georeferenced data, so you
need to use the
latitude and longitude columns to position the nodes. These columns
are mapped automatically because of their names. The preferred format
for latitude and longitude is DMS (degrees, minutes, seconds). For
example: 32D43’31”N. If the latitude and longitude columns
contain only numbers, the values are interpreted as degrees. For example: latitude 12.56 is interpreted as 12.56 degrees, which
equals 12D33’36”N (in DMS). To map several properties to the same column:
-
Map both the
idproperty and thenameproperty to theCitycolumn.
To add properties and map them to columns:
-
Click the
button. -
Type the property name
population. -
Map this new property to the
Populationcolumn.
The result is shown in the following figure. Note that
with
City mapped to name, the name appears on the nodes in the preview. 
Mapping node data to properties
To remove the mapping of a property:
-
Select the property in the list.
-
Click the
button.