With the release of the GeoRSS v1 spec recently, I have added support for those tags (georss:) to a new GeoRSS module, using the location module as an API to store the location information. I separated it out into a new module as it depended on another module (currently aggregator2) to give it geodata for incoming feeds so feeds coming into Drupal can have location information extracted form them and saved against the nodes. The module also adds the 'official' GeoRSS tags to the outgoing feeds from Drupal, similar to the way that the location module does with the W3C geo: tags.

These tags do not currently work in the location module as they are being converted to plain text (see discussion in gmap module issue tracker).

Would now be a good time to fix this support and move the code which adds geodata (in the form of geo:, icbm: and geourl:) from the location module into the GeoRSS module to add to the official georss: namespace which is already implemented there?

Comments

geodaniel’s picture

Title: GeoRSS support » Moving GeoRSS support
Version: 4.7.x-1.x-dev » 6.x-3.x-dev
Assigned: Unassigned » geodaniel
Status: Active » Needs review
StatusFileSize
new1.31 KB

Attached is a patch against HEAD to remove the faulty geo:Point entry that location module adds. For outgoing RSS, the georss module adds a choice of the official GeoRSS simple, GeoRSS GML or the W3C geo:Point based on location information sourced from the location module API. It also supports these flavours of geodata when being consumed by the aggregator2 module, and will soon support other aggregators too.

I have not added support to the module for icbm or geourl as I believe they are pretty much unsupported now. Having said that, I would add them in if there were enough people interested.

geodaniel’s picture

Title: Moving GeoRSS support » Reorganisation of GeoRSS support
Status: Needs review » Needs work

The latest version of location module removes support for geourl and icbm, leaves in a fixed version of the geo:Point tag (with the exception of a minor typo, noted elsewhere).

Ankur suggested in an email to me, and I'd agree, that this be left in as a default for people who don't want to have to add another module to their list; but if the GeoRSS module is enabled (it also provides other functionality, so is a useful extension to the location module) then the controls in there take should precedence. I'll attach a patch for this soon, if that sounds like a good solution.

geodaniel’s picture

Status: Needs work » Needs review
StatusFileSize
new2.57 KB

And the patch...

geodaniel’s picture

Please could we also backport that to Drupal 4.7 (if the patch is accepted)? It'd just need a module_exist instead of module_exists function call in the 4.7 version.

bdragon’s picture

Status: Needs review » Closed (duplicate)

Location HEAD now lets you choose your GeoRSS method.