The Geotaxonomy module provides mapping of content based on their terms. It's best known for its use in Managing News.

A tagging vocabulary and autotagging should be handled in a distinct feature: #945184: Candidate Debut feature: debut_tagging, offering tag suggestions.

For debut_geotagging:

* Require debut_tagging
* On enable, import a set of terms with locational data.
* Use Open Layers and MapBox.

Possibly, this could be moved from the existing code in the Managing News distro to a Debut feature.

CommentFileSizeAuthor
#17 issue-945214-openlayers_plus_port_to_drupal7_1.patch27.52 KBao2
#8 openlayers_plus_port_to_drupal7_0.patch23.73 KBao2
#7 debut_geocoding.tgz4.63 KBao2
#1 debut_geotagging.tar_.gz13.22 KBnedjo

Comments

nedjo’s picture

nedjo
he/him/his
Primary language English
commented
StatusFileSize
new debut_geotagging.tar_.gz13.22 KB

Draft feature attached.

nedjo’s picture

nedjo
he/him/his
Primary language English
commented

Opened #945258: Consider moving selected features to Debut? on Managing News.

Also opened #946396: Standardize on OpenLayers as map client solution on Debut.

nedjo’s picture

nedjo
he/him/his
Primary language English
commented

Should integrate https://github.com/developmentseed/openlayers_plus.

ao2’s picture

ao2 commented

geofield: http://drupal.org/project/geofield is also a good way to add geotag information to content, it uses the field api.

ao2’s picture

ao2 commented

Hi, I am building a debut_geocoding feature based on geofiled, it is for drupal 7, can I hijack this issue to talk about it? The two features are quite related and they could even be merged eventually.

I also tried to add openlayers_plus to it, but it is not fully working with d7.

Thanks,
Antonio

nedjo’s picture

nedjo
he/him/his
Primary language English
commented

Yes please! I'm not working further on the geotagging feature I started for D6. A fresh start is needed and very welcome for D7. Geofield looks promising.

ao2’s picture

ao2 commented
Version: 6.x-1.x-dev » 7.x-1.x-dev
StatusFileSize
new debut_geocoding.tgz4.63 KB

OK, here it is, based on:

TODO:

  • Review the terminology, I find "geocoding" more general than "geotagging", and I'd use the former for any "natural" association to geospatial data to content, not only from a textual description of the location like in the usual definition, but even from a viasual map, for instance
  • support openlayers_plus, there's a patch about it in the archive for some initial support, but it still does not work fully with Drupal 7
  • Integration with some taxonomy mechanism or with the goecoding module from above, how can we do that? A layer for each geocoding mechanisms (map, goecoding textfield, taxonomy) rendered on the same map? And is there a way to use one field at time in the edit form, from a set of alternatives (map, goecoding textfield, taxonomy)?

This is my first experiment with features, be kind :)

@nedjo If it looks acceptable as a starting base I can set up a sandbox and give you rights to commit there.

Thanks,
Antonio

ao2’s picture

ao2 commented
StatusFileSize
new openlayers_plus_port_to_drupal7_0.patch23.73 KB

Attached is a patch to make openlayers_plus working with d7, I'll submit that to the upstream developers later, but for now we can reference this in our makefiles.

Regards,
Antonio

ao2’s picture

ao2 commented

@nedjo, about the world taxonomy that was in debut_geotagging, what about moving it debut_world?

I don't know the taxonomy API in d7 yet, so I don't feel confident playing with it myself right now.

nedjo’s picture

nedjo
he/him/his
Primary language English
commented

Hi Antonio,

Thanks for the contribution and apologies for the delay reviewing this.

I haven't yet installed this, just looking over the code. First off, some questions:

  • Has the

Some suggestions:

  • The fields for other content types should not go into this module, because then we would be creating dependencies. Or a geographic field does go here, it should be as a distinctly geographical content type, perhaps 'location'. Alternately - but this would be considerably more difficult - we could introduce a means where a site admin can select which Debut-provided content types should be enhanced with a geographic field, allowing us to enhance other features without creating dependencies.
  • Maybe a good name for the feature would be debut_location.
  • I think I recently read that a locational field had been added again to the OpenLayers module. Do you know if this is true? If so, is Geofield still the better option? Why?
  • Yes, any taxonomy stuff would go in a separate feature, maybe still called debut_geotagging. But the important thing is first to get the location handling right.
ao2’s picture

ao2 commented

@nedjo, your first question has been truncated.

I'll check your other remarks when I find some time.

Thanks,
Antonio

nedjo’s picture

nedjo
he/him/his
Primary language English
commented

Other related feature modules: http://drupal.org/sandbox/nicoz/1303200, http://drupal.org/project/odv

ao2’s picture

ao2 commented

@nedjo, if a feature could "enhance" existing content types without them depending on it, I think that would be great. I need to do some research about that.

nedjo’s picture

nedjo
he/him/his
Primary language English
commented

I think I recently read that a locational field had been added again to the OpenLayers module. Do you know if this is true? If so, is Geofield still the better option?

Turns out that Openlayers field is not a locational field but rather a way to add a map/preset to an entity. So Geofield it is.

I'll give some thought to the problem of enhancing existing content types without creating dependencies and post any ideas.
[edit: accidentally posted this from my partner's machine, correcting the username]

nedjo’s picture

nedjo
he/him/his
Primary language English
commented

if a feature could "enhance" existing content types without them depending on it, I think that would be great.

I've just implemented this in #1316514: Provide media field for other features for field_media. See the diff for that issue.

ao2’s picture

ao2 commented

I think this solution is OK, thanks a lot. And I agree debut_location is a better name.

Regards,
Antonio

ao2’s picture

ao2 commented
StatusFileSize
new issue-945214-openlayers_plus_port_to_drupal7_1.patch27.52 KB

I am abusing this thread again to keep track of an update to the patch in #8, sorry.

nedjo’s picture

nedjo
he/him/his
Primary language English
commented

There is now a debut_location feature at http://drupal.org/sandbox/pmackay/1571202.

ao2’s picture

ao2 commented

Hi nedjo, thanks, I'll take a look.

BTW I saw there is also a openlayers_plus module on drupal.org these days: http://drupal.org/project/openlayers_plus

nedjo’s picture

nedjo
he/him/his
Primary language English
commented

Moved debut_location issue to #1699460: Candidate Debut feature: Debut Location, providing location mapping and taxonomy since this issue is about geotaxonomy (something distinct from a general location feature).