Location terms are currently only assigned by Feeds on import. Channel tags are used for tagging items by users and for creating 'channels' of news from such tagged items.

Location and Channel tags are currently two completely separate vocabularies. We should merge them to allow for the following features:

- Tag items with geo terms (tag "Haiti" will make item show up on map in Haiti)
- Make any tag a geo term in retrospect simply by adding location information to it (add geo location to "G8 Summit" and make it show up on map)
- Use tagging stack not only for location auto tagging but any term autotagging

Comments

verikami’s picture

verikami commented

+1 for this :—))

Good step for implement locations to Feeds (sources) — as well — it will be nice and logically consistent to have geotaging appended to all of data types (Channel/Feed/Feed item). But — a question: if we have only one dictionary for that — this wouldn't resolve inconsistency of Yahoo Placemaker's fuzzy set of data mentioned @ #784928: Taxonomy inheritance ...

In my opinion, it will be easier to go further, if we have a separate subsets of geodata for all this items. Then we can switch, compare and filter them. The problem of wrong data is significantly more visible if you use MN in worldwide context (so many words, the same names...). Yahoo Placemaker is fine, if we want to have "some" results, but having a personal (local) consistent set of places looks also interesting...

...loose thoughts...

cglusky’s picture

cglusky commented

Makes sense. What I struggled with most with MN and Placemaker was a quick way to edit bunk locations. So if channel/location unification helps get us to inline quick edit of taxonomy terms I think you get a real bonus.

Will White’s picture

Will White commented
Status: Active » Needs work

Work is mostly complete on this and the patches are in the make file. Just need to get tests together for the various patches.

Will White’s picture

Will White commented
Status: Needs work » Fixed

This is complete as of MN 1.1.

Status: Fixed » Closed (fixed)

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