Comments on John Graham-Cumming: The 10:10 Code

If you like it even shorter try my modified Geohas...

2011-06-20T14:43:01.571Z

If you like it even shorter try my modified Geohash algorithm I used in my twittori.com project. http://blog.twittori.com/about-link-format/

Maybe it's my military experience, but I find ...

2011-06-20T13:40:22.049Z

Maybe it's my military experience, but I find UTM or MGRS the easiest.

We don't need a twelfth system for encoding la...

2011-06-20T13:00:38.207Z

We don't need a twelfth system for encoding lat/lon tuples. Pick an existing one and start using it.

Currently, we have:

- decimal lat/lon

- d/m/s lat/lon

- UTM ( http://en.wikipedia.org/wiki/Universal_Transverse_Mercator_coordinate_system )

- MGRS ( http://en.wikipedia.org/wiki/Military_grid_reference_system )

- Geohash ( http://geohash.org/ )

- "Natural Area Code" ( http://en.wikipedia.org/wiki/Natural_Area_Code )

Please, suggesting something like this and encouraging people to implement it is like coming out with a device that only charges over micro-USB. Just... don't.

The US has something similar but it is not used. I...

2011-06-20T12:08:03.454Z

The US has something similar but it is not used. In the US it is called ZIP+4 and the +4 such as

12345-1234

Identifies a specific property and can be reversed to an address with the right database. However the ZIP+4 is very rarely used.

And how about a version in Factor!

By the way, I also get "MEQ N6G 7NY5".

Agree with id.php - any geo-code needs to have the...

2010-06-16T02:48:58.291Z

Agree with id.php - any geo-code needs to have the ability to be humanly interpreted - so if you see two codes you can immediately tell if they are close to each other. Geohash has that ability since the left-hand characters encode enclosing (larger) areas.

Talk about a serendipitous finding. I've been...

2010-06-15T18:38:21.617Z

Talk about a serendipitous finding.

I've been thinking of, and attempting to create something like this, to extend the concept universally unique identifiers. (UUIDs)

Not a bad idea (and the checksum is nifty!). Howe...

2010-06-15T17:47:05.618Z

Not a bad idea (and the checksum is nifty!). However, the GeoHash scheme has two important properties that 10:10 does not:

* arbitrary precision (to nearest 5 bits)
* lat/lon are interleaved

Bit interleaving in particular is useful because a geohash which is the prefix of another contains the other in its bounding box. Two geohashes which share prefixes are near each other. And so on.

This is great for search (e.g. google) and for use as a single database key for a location.

I am not a scientist, but rather a "jack of a...

2010-06-15T14:26:05.460Z

I am not a scientist, but rather a "jack of all arts" (photography, music, and writing).

I "proposed" a similar way of uniquely encoding locations in my utopian novel "The Vavilovian Conspiracy"

Free to download from www.lulu.com/blackbirdcraven

2010-06-15T11:45:58.118Z

This comment has been removed by a blog administrator.

So far so good but once encoded how does anyone el...

2010-06-15T11:44:42.542Z

So far so good but once encoded how does anyone else use it? Need a decode routine ideally with a link to Gmaps. Apart from that I agree with others who suggest eliminating ambiguous characters like I 1 l

I translated the code to C#, and I got MEQ N6G 7NY...

2010-06-15T09:10:33.023Z

I translated the code to C#, and I got MEQ N6G 7NY5 as well for the coordinates for the terminal coordinates. The SOC-algoritm from 2006 and the 1010-algorithm differs both in the calculation of the checksum and the alphabet used. the SOC-version uses a 32 character alphabet, and the 1010-version uses only 29 characters. My C# implementation (including exe) for both SOC and 1010 twoway conversions can be found at http://bit.ly/SOC1010

When I converted the 1010-coordinate back to latlong for the eurotunnel terminal, I got a difference of 11.1m from the original coordinates...

I like this, even though practically it's not ...

2010-06-15T08:33:09.942Z

I like this, even though practically it's not very usable. Yahoos WOEID doesn't do error checking, but does a few things that make it v powerful:

- takes accuracy into consideration
- brings some sort of place hierarchy
- helps when the geocode of a place changes (earthquakes etc)

It's a long way for WOEIDS to become something that can be put into a GPS device, but using smart metadata is always better than, er, not that smart.

London is 44418.

http://developer.yahoo.com/geo/geoplanet/guide/concepts.html

Hey Nice Idea man.. But I propose either to use al...

2010-06-15T08:13:06.024Z

Hey Nice Idea man.. But I propose either to use alphabets only or remove some confusing (look a likes )LIke: (1 and I,l),(0,o,O),(B,8),(b,6)

I made "GLOCO" a while ago, it encodes l...

2010-06-15T06:49:11.696Z

I made "GLOCO" a while ago, it encodes lang/lat to a code of 5 up to 10 characters long, since takes into account populair locations in the worlds. Hence city centres have shorter codes, compared to deserts. (www.gloco.com)

It would be nice (though technically impossible) t...

2010-06-15T05:19:12.149Z

It would be nice (though technically impossible) to use a system where it's easier to calculate the distance between two points.

Perhaps putting a grid over a Winkel Tripel projection would work better

Here is another way to make the resolution approxi...

2010-06-15T00:21:37.861Z

Here is another way to make the resolution approximately consistent across the globe.
Enclose Earth into a cube. Divide each face of the cube into a 8,000,000 by 8,000,000 grid. Project the location onto the cube. The square number is your code. There are 3.84E14 squares on the cube: that's also 10 characters in base 29 but it gives you a resolution better than 1 meter on the ground anywhere in the world.

It's a clever idea, but it's too clever fo...

2010-06-14T23:09:11.477Z

It's a clever idea, but it's too clever for a stupid person like me. I look at "MED 8FV N9K5," and it's not immediately obvious to me that it describes a point north of the equator and east of 0 longitude.

cool stuff, two comments tho, first i translated y...

2010-06-14T22:20:04.946Z

cool stuff, two comments tho, first i translated your code to perl and couldn't get the same answer, so i then tried it in js and i got the same answer i got in perl!

so i think that the location at 51.09559,1.12207 maps to MEQ N6G 7NY5

secondly, c %= 29 you probably meant c %= base

cool stuff, two comments tho, first i translated y...

2010-06-14T22:18:45.464Z

Very interesting! Q1: Where in the code the radiu...

2010-06-14T21:07:53.001Z

Very interesting!

Q1: Where in the code the radius 10m is specified? Can we produce code with 500m radius?

Q2: Does this mean all points in a radius of 10m distance of a specific point will produce the same code?

Do you have reverse ? i.e. given the string splits...

2010-06-14T20:21:29.533Z

Do you have reverse ? i.e. given the string splits to proper lan/lat ?

this code is made less readable by use of single c...

2010-06-14T19:47:08.407Z

this code is made less readable by use of single character variable names. :( Is it too much to expand them please?

What a great idea for a google maps mashup!

2010-06-14T19:27:02.311Z

What a great idea for a google maps mashup!

This looks like simple arithmetic. I would sugges...

2010-06-14T19:17:55.731Z

This looks like simple arithmetic.

I would suggest two basic improvements...

1) Take into account that at higher latitudes, longitude need not be encoded as accurately.

2) don't combine latitude and longitude. Keep them separate, with a space in between. That way, a human reader can tell that two encoded points are near each other.

Comments on John Graham-Cumming: The 10:10 Code

If you like it even shorter try my modified Geohas...

Maybe it's my military experience, but I find ...

We don't need a twelfth system for encoding la...

The US has something similar but it is not used. I...

And how about a version in Factor!By the way, I also get "MEQ N6G 7NY5".

Agree with id.php - any geo-code needs to have the...

Talk about a serendipitous finding. I've been...

Not a bad idea (and the checksum is nifty!). Howe...

I am not a scientist, but rather a "jack of a...

So far so good but once encoded how does anyone el...

I translated the code to C#, and I got MEQ N6G 7NY...

I like this, even though practically it's not ...

Hey Nice Idea man.. But I propose either to use al...

I made "GLOCO" a while ago, it encodes l...

It would be nice (though technically impossible) t...

Here is another way to make the resolution approxi...

It's a clever idea, but it's too clever fo...

cool stuff, two comments tho, first i translated y...

cool stuff, two comments tho, first i translated y...

Very interesting! Q1: Where in the code the radiu...

Do you have reverse ? i.e. given the string splits...

this code is made less readable by use of single c...

What a great idea for a google maps mashup!

This looks like simple arithmetic. I would sugges...

And how about a version in Factor!

By the way, I also get "MEQ N6G 7NY5".