GeoURL support?

Boris Mann - February 19, 2004 - 10:53

GeoURL is a way of adding location information to pages/blogs/etc.

I'm thinking of building a module that allows you to tag any node with relevant GeoURL information (this gets added as meta-tags) as well as the "what's close to this item?" link, which leads to a GeoURL requesting items that are close to the physical location of that post.

Here's the example for my site, which you can also retrieve as an RSS feed (so you could display "neighbours" right on your site).

Any interest?

» Login or register to post comments

I used keywords module

magico - February 19, 2004 - 11:05

I used keywords module to add extra META tags in the head. Here is my example:

meta name="geo.position" content="40.6412; -8.6187"
meta name="geo.placename" content="Aveiro"
meta name="geo.region" content="PT-01"
meta name="ICBM" content="40.6412, -8.6187"
meta name="DC.title" content="Fernando Silva Online"
meta name="DC.creator" content="Fernando Silva"

Yes, that works for tagging e

Boris Mann - February 19, 2004 - 11:14

Yes, that works for tagging every single page with the same location -- other systems (most notably WordPress) allow specifying a default location, and then per-post overrides.

Unless keyword lets you do this per-post?

I don't think so

magico - February 19, 2004 - 12:09

I don't think that keywords allows defining specific tags for posts. But it would probably be a great addition, because this way we would have a generic way of defining head tags for a specific posts.

Now that GeoURL is back this would be great.

Tarlbot - August 19, 2005 - 14:25

You may have missed it but GeoURL is back!

http://geourl.org/

It would be great to have a Drupal module that would allow you to put in a default Geo-location for your site, that was over-ridable on a node by node basis.

For those who don't know you need to put stuff like this in the head:

<M*TA name="geo.position" content="45.9226;-64.3622">
<M*TA name="geo.region" content="CA-NB">
<M*TA name="geo.placename" content="Sackville">
<m*ta name="ICBM" content="45.9226, -64.3622">
<m*ta name="DC.title" content="tarlbot.ca">

(Asterisks (*) in "meta" because "meta" was blocked as "suspicious content")

the geo.position, and ICBM both have the same data formatted a bit differently. Probably the DC.title should be the node name, not the site name if a position is input. In a perfect world the geo.region and or geo.placename would be hidden on a node where a custom position had been input but geo.region and or ge.placename were not added.

Wow, that's an old post of

Boris Mann - August 22, 2005 - 04:50

Wow, that's an old post of mine!

Would be fairly easy to build these days on top of the "location" module. A GeoURL module would tie into this, using a user's location as the default tag, which would be overriden by any location-enabled content.

Old but relavent

Tarlbot - September 30, 2005 - 00:00

Yes old, but now that GeoURL is back it is relavent again.

Location (API, module)

rport - December 8, 2008 - 13:22

I arrived here looking for a current answer to the Geo Locationquestion...

The answer?: location.module and associated API allow Drupal objects, including nodes and users, to be associated with specific physical locations.

While the location.module might not be an answer for you, it worked for me..

Russ

---
Russ @ Maintenance Essentials