nodes not creating geocode data

tagging and marked as a duplicate of #798484: nodes not creating geocode data (if the issue is different, just repost and say why).

I can confirm this under the rc1 and the latest dev. The longitude and latitude fields are not getting populated with the data from the geocode.

Maybe in some projects... but the pattern in location lately is for someone to post a problem in 3.0, for someone to suggest dev has a fix, for someone to test and see if dev indeed has the fix. Then if the problem is fixed in dev, to mark the issue fixed/closed. If it is not fixed in dev, to proceed to try and make the fix against dev.

So really, we need to know if it is a problem in dev.

Yes, latest dev version is broken.

By the way I am using the location cck field.

I'm not sure where to post this or if it is relevant.

I am adding nodes using Node Import and suddenly the newly important nodes didn't show up in my proximity search. After a ton of head scratching I figured out the long / lat weren't being created. I found that to make it work I had to use the full state name instead of the two letter abbreviation.

For anyone else that might stumble upon this I was able to fix my issue after reading much of the source code of this module and after having to jump through many hoops to get gmap geocoding working. I didn't have to modify any source code to do it, but there are several configuration options that must be set in order for this to work.

It doesn't seem that JIT geocoding is working, but I haven't done any troubleshooting on why it doesn't work yet.

@zdean
If the problem exists in dev then the issue goes against dev not against the certain version. Then it gets fixed in dev and a new release will be made. If the problem doesn't exist in dev then it is fixed and you either need to use dev or wait for a new release. That is standard drupal practice in these queues. This problem happens to exist in both dev and 6.x-3.1-rc1 and so it should be marked against the dev. I am going to leave it to you since it is your issue and I don't seem to have this problem anymore. You might want to provide more information about your setup (modules using, configuration options, etc.). I might be able to help you if you provide more information.

@jdwfly. Would definitely be useful to understand the config steps. We could probably add that later in the documentation which seems to be in need of updates.

tagging (adding key word bounty so someone might find this issue)

I created Documentation on how to get this to work. Please check out http://drupal.org/node/817592 and let me know your comments. This worked for me, hopefully I didn't miss any steps. Hope this helps newcomers to the Location module to get up to speed an running quicker.

Do I get the bounty? :-)

zdean, why did you remove the location bounties tag? Someone in location, looking to do paid work will have a hard time finding this without it... ?

ok, post back when you have more info on how to reproduce the issue. thanks for sticking with this and keeping us updated.

I'm having the same problem. My first node (of type Tour Date) is the only one that would generate coordinates. Same with first user. Other nodes and users not appearing on gmap.

Been working on this for 2 days, and just moments after posting I fixed it: in the content type settings, make sure to allow coordinates.

did something change that made it necessary to add allowing coordinates? for example, did it work before an upgrade to dev, where before allowing coordinates was not selected?

stopped working again! Something is broken. I'm using latest location and gmap dev versions on a fresh install.

the official release just came out. I know this has been going on for a while, but please try the new official release on a new blank test site, and document the tests to reproduce the problem and post back. Thanks.

Here's what happens to us:

A new node gets saved fine with geo-coding because it is entered with the full state name, e.g.

City: New York
State: New York

when it gets saved, that info is stored as:

City: New York
State: NY

If a node like this hasn't already been geocoded, it will fail to geo-code it with the abbreviated state name. Change the state name to New York and save, geo-coding works fine. I didn't try dev yet, this is with the most recent release. Was this fixed in dev?

-Daniel
My Gym and Trainer

Dear all,
Not sure if you have seen this. Have a look:
http://drupal.org/node/899624

I think this is the same problem, but I do not know if the suggested code will help. Can someone take a look and tell me if it is relevant or I've just sent you on a wild goose chase. :)

Look forward to hearing from you. Cheers!

Regards,
Chang

I'm still experiencing this issue in dev. Geocoding only works if you create a node, delete its location, and then specify the location again.

Update -- After removing the base_url variable from my settings.php file, this began working.

This leads me to believe that location (and in my case gmap_location) is making a request for lat and long, but that the geocoding information isn't making it back. This could stem from hosting problems or Drupal's configuration.

Kind of vague, I know, but it's a starting point.

Closing old D6 issues as D6 is end of life