Location Handling

Submitted by Evan Prodromou on Tue, 06/17/2008 - 02:17

Issue ID:	50
Issue Category:	feature
Component:	core
Priority:	normal
Status:	fixed
Assigned:	Unassigned
Version:	0.9
Milestone:	0.7
Keywords:	Location Microsyntax

Let users define their locations in notices.

Twittermap uses "L:location" as the format; see http://twittermap.com/maps/faq.html . You can also define locations, like this: L:location=address,city,region.

We'd need to store locations in the database; we'd also have to allow users to update their profile location using this method.

Legacy Data

This issue was migrated from another tracking system. The legacy data at time of import is provided below as a reference.

Ticket ID:

Reported by:

evan

Status:

new

Type:

feature

Component:

core

Priority:

Version:

0.9

Milestone:

0.7

Updates

#1

Submitted by JonTheNiceGuy on Wed, 06/10/2009 - 09:33.

Following on from this, [http://www.stoweboyd.com/message/2009/05/no-additional-twitter-meta-tags-please---the-next-web.html this article] (as discovered via [http://identi.ca/cubicgarden @cubicgarden] from [http://microsyntax.org microsyntax.org]) suggests the use of forward slashes as a start, and optionally if there are spaces in the name, an end character to indicate location.

For example: I've just arrived at /Manchester Piccadilly Station/ Who else is here?
or
I'm in /London now all weekend.

By using the syntax [Space or start of line]/[Location][Space, exclamation mark, question mark, full stop or end of line] and [Space or start of line]/[Location inc. spaces]/[Space, exclamation mark, question mark, full stop or end of line] you should be able to automatically populate the location field on-the-fly.

People who want to use GPS co-ords can use

I'm geocaching. Just found one at /53 25.123 -2 08.00/

This would remove the requirement to store locations in the database, as they'd be populating them dynamically based on what they *want* to provide.