Two issues:

I have a CSV containing restaurant listings that includes lat/long as well as full addresses, with each locational element in a separate field. I have set up a content type that has a full set of locational elements enabled via the location module (street, city, lat/long, etc.) that matches the CSV.

1. The matching routine only has location field options for country, latitude, and longitude. It does not offer options for address, city, postal code, or phone number, even though these are set as either 'allow' or 'required' in the content type location field collection settings.

2. When I run the importation, the preview screen shows that the latitude and longitude have been captured, but when the final import is run, these are not dropped into the location table. I am able to successfully add full locations using 'add content' - it is only when I am running node_import that locations cannot be added.

Thanks.

Comments

mlondon77’s picture

I'm having exactly the same problem. Does anyone have any ideas? I'm pulling my hair out over this one.

Thanks in advance for preventing me from going completely bald.

bdragon’s picture

Assigned: Unassigned » bdragon

Hijacking this issue.

Working on it over in the location queue.

http://drupal.org/node/297009

Robrecht Jacques’s picture

Do you plan to add node_import support in location module? Or do you prefer it being added to node_import module as a location.inc?

bdragon’s picture

I'm fine with it living in node_import as it is now.

joshualieb’s picture

Awesome. Thanks for fixing this. Works for me.

Although there is a subsidiary issue, now - when I run the import, the address is pulled in, and the lat and long are applied using the geocoding API, which overwrites the existing values, which is fine save for those records that have a problematic address. This I can fix on the data side, though.

Robrecht Jacques’s picture

Status: Active » Closed (duplicate)
kbk’s picture

Status: Closed (duplicate) » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.