Get location coordinates from inside computed field

Paulwamail, I believe we are having sort of the same problem. I am trying to count the number of articles of content type dblog in nearest proximity.
So, Ive comed up with this (not entirely perfect) code:

$min_lon = ($node->location['longitude'] - 1);
$min_lat = ($node->location['latitude'] - 1);
$max_lon = ($node->location['longitude'] + 1);
$max_lat = ($node->location['latitude'] + 1);

$result = db_query("SELECT COUNT(node.nid) AS nid
 FROM node node 
 LEFT JOIN location_instance location_instance ON node.vid = location_instance.vid
 LEFT JOIN location location ON location_instance.lid = location.lid
 WHERE (node.type in ('dblog')) 
 AND (location.latitude > %f AND location.latitude < %f 
 AND location.longitude > %f AND location.longitude < %f)", $min_lat, $max_lat, $min_lon, $max_lon);
 
 $items = array();
while ($row = db_fetch_object($result)) {
  $items[] = $row->nid;
}
$node_field[0]['value'] = $items[0];
 
;

The problem is, exacly as yours, I cannot get an answer from the $node->locations[0][latitude] OR $node->location[latitude] fields, other than NULL.

So, Im pretty much stuck too. If I override the input values with this:

$min_lat = 63.4 - 1;
$min_lon = 10.39 - 1;
$max_lat = 63.4 + 1;
$max_lon = 10.39 + 1;

The script outputs fine.

So, what is needed to get the locations lat/lon of node from inside a computed field?
Thanks:)

And what is there if you print

<pre>
print_r($node);
</pre>

in your node template?

Oh, I see that we are working on different drupal versions. I do not know if the above works for 5.x, but at least maybe you got some clue on how to create your db query:)

<pre>
print_r($node);
</pre>

Will have a look.

[location] => Array
        (
            [lid] => 12
            [name] => 
            [street] => 
            [additional] => 
            [city] => 
            [province] => 
            [postal_code] => 
            [country] => us
            [latitude] => 63.326090
            [longitude] => 10.113290
            [source] => 1
            [is_primary] => 0
            [locpick] => Array
                (
                    [user_latitude] => 63.326090
                    [user_longitude] => 10.113290
                )

This one indicates the use of $node->location['latitude'], and this one:

[locations] => Array
        (
            [0] => Array
                (
                    [lid] => 12
                    [name] => 
                    [street] => 
                    [additional] => 
                    [city] => 
                    [province] => 
                    [postal_code] => 
                    [country] => us
                    [latitude] => 63.326090
                    [longitude] => 10.113290
                    [source] => 1
                    [is_primary] => 0
                    [locpick] => Array
                        (
                            [user_latitude] => 63.326090
                            [user_longitude] => 10.113290
                        )

                    [province_name] => 
                    [country_name] => United States
                )

indicates a $node->locations[0]['latitude'] when only one location.

So, this leaves me with no idea why I can't reach the value from computed field.

Maybe find a way of somehow sneaking print_r into a computed field to see what values are present in the field.

may be this is weights problem and when the computed field is doing its job there is not location data yet. If so you need to set weight of computed field module havier than location module in system table.

I have set the weight of locations to -10 at http://mysite.org/admin/content/node-type/dblog.
The computed field is at the very bottom of the list. Still nothing.

Thanks for suggestion though:)

Trying to use a cck location field instead, to see if that works better.

That query should indeed do the trick.Have you tried putting in a dummy lat/lon to see if the query works well?
If yes, your problem is identical to mine, $node->locations[0]['latitude'] = NULL, which is quite odd..

I got around the problem for now by accessing the database every time the node is loaded (via content template), so that the value is there. My solution is of course in question when it comes to performance, but it will have to do the job for now.

Finally!

I saved the whole $node query to the database, and found out that location values is indeed not saved in $node->location[0][latitude]. BUT, the new latitudes are stored in following:

$node->locations[0][locpick][user_latitude];
$node->locations[0][locpick][user_longitude];

So, to manipulate the locations from computed field, use these:)
However, I do not know what other location fields are called. To find out, just put

<?php
$node_field[0]['value'] = var_export($node, TRUE);
?>

in your custom field.
Let it save to the db as a 'text' type, save a node, then go to phpmyadmin and inspect the array.