Understanding Location Taxonomy [#610922]

I've been trying to figure this out for a while and have not come up with any real answers to my predicament. Afetr reading a lot and trying to figure out how the location taxonomy module works, I now understand that I can assign locative data to a taxonomy term, however I woul like to do the exact opposite of what this module does and apply taxonomic data to locations. Is there a way to do this?

I want to create a taxonomy that would describe the kind of location I am collecting data on [using terms like hospital, store, park, school, gym, etc.], and then expose that taxonomy to only the location data collection in the form of a select box. Later on I want to be able to create maps and views based on the type of location. Am I missing something here or is my idea just a pipe dream?

Comments

Comment #1

iparsin commented 21 July 2010 at 05:53

You are way better than me, I still could not figure out how exactly taxonomy location works. Anyway, I want to do exactly what you want; collect location data and assign a type to it. Any idea...please help? Thank you.

Comment #2

njathan commented 27 August 2010 at 20:33

I too want to understand how this sub-module works..
My purpose too is similar to what's mentioned above. However, my main motive of evaluating Location Taxonomy (as opposed to using 'Hierarchical Select' module's content taxonomy feature which is already working) is to make use of the geonames integration that this module provides... I am thinking i can create a country -> state -> region taxonomy structure by using this module in conjunction with GeoNames data... and in future use this to churn our more useful stuff... am i right?

Comment #3

Stomper commented 21 February 2011 at 01:34

If I understand your use case correctly, then I have similar needs.

I have a taxonomy of university campuses, I would like to link them to a city-state in Location module.

Do we need Conditional Field support?

Comment #4

chowdah commented 27 February 2011 at 04:07

My solution to the problem was to make a content type called Directory Listing, where I collect all my location information, but collect other data as well and a custom taxonomy restricted to the Directory Listing content type.

To reference the directory listing in nodes, I used a custom cck field called field_location_reference that was of the type node reference. So if I wrote a story, or listed and event, I just referenced the node that held the locative data using the node reference explorer widget on the specialized cck field.. If I wanted to reference Directory Listings in node body fields (in the body of the story), I used link_node filter module - all you have to know is the node id and you can reference another node by typing [node:1234].

This worked best for me, because I was intending to build a directory anyhow.