Pro & cons of using Core Location vs. Location CCK

• "core" location fields have been separated out into the "node_location" module, which is included in the location package. This way you can choose to have only one type on your site.
• Only locations added with node_location work with the "Node Locations" block.
• CCK Locations in Views require a relationship.

The basic difference is that core location fields are the 'legacy' way of storing locations, and the cck is the 'up-and-coming' method.

Given the state of most modules at this point it might be best for you to stick with the core location fields - although that is changing rapidly.

Myself, I would go with cck (as this is where everything is going in the future), and contribute code to projects that needs to move from core to cck. But if you are not a coder, then core fields is likely your best bet.

Cheers,

Patrick

well since this is a new site, sounds like location CCK might be the best choice

or.... will I be able to import into CCK later?

Turning Location CCK is easy enough

But how do I disable the native or core location features - so I don't see two?

hit 'edit' on the content type and set the number of location fields to zero

To turn off legacy-style locations, you should disable the "Node Locations" module on your modules page.

Attachment	Size
location modules.png	102.66 KB

This is interesting. I've been tinkering with this and using content_profile with location_cck as a way to store a users location.

It seemed like a good idea at the time ;)

What does everyone think of that?

For now and the future I would definitely propose using location_CCK. Besides the fact, that with any user, testing the module it will come to a fully featured method for storing Geographic data much faster, i'd propose CCK because of its broader point of view.

Some features core locations do NOT have are:

• using revisions
• using different location types by using different fields
• using different formatters (writing a new formatter for cck is quite easy)
• prepares for the Drupal-7-fields-in-core-point-of-view

Sure, using location_cck with content profile is a good solution.

Another general hint for using a GMAP output within a node in D6: Views Attach - really nice Views Plugin, with opportunity to weight the specific views, like fields for node view.

What's missing for location_cck mght be some additional widgets and formatters, I hope to provide some for that in the future, but cannot promise.

derhasi, I'm interested in using views attach to bring the location cck field in as a gmap, but it doesn't seem feasible.

I have a 'node content' type view that displays styled as a Gmap. It uses a relationship to gat the latitude/longitude fields from the location_cck feild. The views attachment shows all nodes that have a location. I can't seem to get the current node id to restrict the results to just the current node. Any ideas?

I understand the logic behind using location_cck over node_locations but is it actually possible to show the map on a node?

I'm using
Location 6.x-3.1-rc1
GMap 6.x-1.1-rc1
GMap Location 6.x-1.1-rc1
Views attach 6.x-2.0

You can restrict the view to the current node by using the Views-Argument by two ways:

1. When token.module is installed:

   • set Default argument in the Node content settings (below the general views settings) to [nid]

2. Using a the default argument within Argument Node: Node-ID

   • select Provide default argument
   • then select Node-ID from URL

I have done what you described in 1 & 2, but only 2 seems to work.
Method 1 still shows all location_cck fields.

I was using both options (after much experimenting) so it's good to know only the Node:Nid view argument is actually required.

Incidentally, I needed to add some patches to get this far, the modules are listed in my above post. I added these patches.

Token data not passed to argument comment #60
Array errors in location_cck module comment #5

It seems that location_cck is still very early days.

Thanks again.

When i'm building custom templates, i can't seem to pull only a portion of the information from the location_cck field. Using core location, i was able to access individual portions of the address, such as only the city in this example:

But using similar methods with location_cck seem fruitless. If i show all fields with print_r($node) in the node template, for example, the location_cck field is always one monolithic field.

Does anyone know of a way to pull only one "field" from the location_cck "field"? (i'm not sure here which should be called a field.)

If this is a limitation in location_cck, can this be addressed? (AKA, can i pay someone to fix it without a serious rewrite?)

If not, it's a total deal breaker for me.

I redesigned the node in question and did get access to the individual fields, but now have another node that is
exhibiting the same bad behavior. In the node template, this code:

    
<?php
 print_r($field_loc) 
?>
  

produces this output, with none of the individual fields accessible.

Does anyone know what I'm doing wrong, or what location_cck is doing wrong?

Thanks eink21, but I'm printing from a node template, and got the field name from doing a print_r on the node array. I'm stumped.

When I do a print_r on the location cck variable ("field_company_address" for me), I get the following...

So it appears to be working for me at least. No clue what the problem might be for you, but here are some things I'd try if I were you (I know they look too simple to work but I'm out of guesses pretty much...)

-Maybe it's an incompatibility or adjusted setting for the Gmap module or whatever other mapping/location/geocoding module you're using. (I noticed the coordinates in your output. On your input form, do you actually have individual location fields, or do you just have the user click on the map and the map generates an address for you?)
-Similar to the last point, maybe your geocoding program takes the address information, assigns it an exact set of coordinates, then simply stores all of the individual address fields together in one big field. Maybe if you deactivated whatever geocoding module/software you're using, the individual fields would show back up.
-Check the settings for that field (in the "Manage Fields" tab for that content type). You might've checked some of the boxes that prevent the fields from being displayed on the node output.
-Check your permissions
-Clear your cache
-Check any customizations you made to any location-related core/contributed modules
-Install devel module and do a dprint_r($field_loc) instead of just a print_r
-Also with devel, check under the "dev load" or "dev render" tabs to see if the individual fields are showing up there
-For this particular node template, did you disable or set the #access to 0 for these location fields?

Again... just a bunch of random ideas. I'm obviously no expert, but I figured I'd try to at least help a little.

My location module was up-to-date according to update status. But, I deleted location module, reinstalled it from a fresh download, ran update.php, and suddenly everything worked! Thanks for the help - I was getting really frustrated!

Drupal v6.13
Location Nodes v6.x-3.1-rc1

Node Locations works perfectly, too perfectly for me ... I need Node location for a content (working right!) but i can't get rid of a 'Location form' ('Emplacement' in french , with address , country ...etc.. fields) on user registration (except by disabling the 'Node Locations' module :( . Please, any tip or suggestion is warmly welcome ...

Attachment	Size
howtoDisableLocationFormOnUserRegistration.jpg	70.26 KB

the magic came from /admin/content/node-type/profile (beware uprofile too ;) , everything is working fine , sorry for any inconvenience

Hi All,

reading this thread and a lot of related informations and videos, I finally managed to have maps that partially suit my needs.
I'm using CCK, Location(used as CCK-field) and Views to get:

1. A map view with all contents 2 content types( "organization" and "projects")
2. A map attached to a node (of type "organisation") showing a single location of the node's address and also the locations of the projects that are attached to the organisation via node-reference and views-attach

For the first goal, I set up a view with a map display, a relationship to the CCK-field holding the location data of content-type01("organization"), the fields longitude and latitude coming from that relationship (used as data for the markers of the map).
That is working, but how do I get the data from the other content-type02("project") to be shown on the map also?
Can I somehow use 2 relationships and how can I make the configuration options of the GMap-display understand to use all the Lat/long-values no matter from which content-type they come from, like it is done with the Node-Locations-Page of the Location.module?

For the second goal, I set up a view with a display of "node content" to be attached to nodes of type "organisation", with a map display of the fields Lat/Long coming out of the relationship to the CCK-field, similar to the above, but with an argument set to Node-ID.
That also works, but now how can I see the locations of the related projects?(that are attached via the node-reference-field to the organisation)
Can I work with another view and then use the same map by assigning it the same ID via the GMap-Macro?