“Post type missing” on a GeoDirectory CSV import means the importer could not read a value from the post_type column for that row. Usually the column is there, but the file has been saved in a way the importer cannot read.

Common causes

• The file was saved with semicolons instead of commas. Excel does this in many European locales. GeoDirectory reads comma separated files only, so the whole row ends up in one column.
• The header row was changed, so there is no column named exactly post_type.
• The post_type cell is empty, or contains a post type that does not exist on your site. Places use gd_place.

How to fix it

1. Instead of the sample file, add one listing by hand and export it from GeoDirectory > Settings > Import/Export. The export has the exact columns your site uses, including your custom fields.
2. Open the CSV in LibreOffice Calc. When it asks, choose comma as the separator and UTF-8 as the character set.
3. Add your rows below the exported one, keeping the header row as it is.
4. Save as Text CSV, keep the comma separator and UTF-8, and import the file.

Category imports have the same requirement: use the category export as your starting point, because each row needs the post type in its cat_posttype column.

More tips are in CSV imports useful tips and the listings import settings overview.