Also, these are still hard to remember. Personally, I'm a fan of http://what3words.com/
I'm currently here: http://w3w.co/lives.fend.spent
51–60 of 124 posts
Also, these are still hard to remember. Personally, I'm a fan of http://what3words.com/
I'm currently here: http://w3w.co/lives.fend.spent
I'm a little confused about what this replaces, but it's definitely not postcodes. * Postcodes have a specific meaning: they're both a geographical area and a mail delivery zone (at least in the US). Replacing one short code with another, which requires a different and less reliable third-party service to correctly decode, doesn't seem like a good idea. * Latitudes and longitudes are unambiguous, well-understood, and…
Their own website is displaying/using MapCode's incorrectly. For example, they have 0C.T4 and they say it's in Ireland and appears to be some bench in the picture. However, if you use that MapCode, you will see it's the middle of some river in Amsterdam. 0C.T4 == 52.369764, 4.868898 Another: 81.J4W They seem to claim it's in Alaska, appears to be some road. However, it's another river in Amsterdam. 81.J4W == 52.50895…
It looks like the mapcodes are country specific, and two countries can have the same mapcode.
Earlier quoted context omitted.
Their own website is displaying/using MapCode's incorrectly. For example, they have 0C.T4 and they say it's in Ireland and appears to be some bench in the picture. However, if you use that MapCode, you will see it's the middle of some river in Amsterdam. 0C.T4 == 52.369764, 4.868898 Another: 81.J4W They seem to claim it's in Alaska, appears to be some road. However, it's another river in Amsterdam. 81.J4W == 52.50895…
Mapcodes also have to be combined with some context. In most places it's just the country name, but in large countries it also requires the state (or equivalent). So if you go to the interactive map on the mapcodes site, there's a little link marked context and you need to change that to Ireland. Results in this: http://www.mapcode.com/getcoords.html?iso3=125&mapcode=0C.T4...
I've written a fairly extensive GPS library for some embedded device projects in the past, and I can attest to the computer not caring about the long coordinate system, they are just floating points really.
Yeah, but so are the British post codes. 6-7 symbols and you're down to meters usually. At least for the cities. They definitely bring you close to the front doors.
I'm a little confused about what this replaces, but it's definitely not postcodes. * Postcodes have a specific meaning: they're both a geographical area and a mail delivery zone (at least in the US). Replacing one short code with another, which requires a different and less reliable third-party service to correctly decode, doesn't seem like a good idea. * Latitudes and longitudes are unambiguous, well-understood, and…
Their own website is displaying/using MapCode's incorrectly. For example, they have 0C.T4 and they say it's in Ireland and appears to be some bench in the picture. However, if you use that MapCode, you will see it's the middle of some river in Amsterdam. 0C.T4 == 52.369764, 4.868898 Another: 81.J4W They seem to claim it's in Alaska, appears to be some road. However, it's another river in Amsterdam. 81.J4W == 52.50895…
I'll cite a .doc file here, it's also available on the Developers page:
> 1. Codes only need to be accurate enough for public, every-day use. At the human scale, when you are within a few meters of a destination, you are “there”.
> 4. People live within a “country context”. Addresses seldom include a country name. Unless clearly stated otherwise, they can safely be assumed to be in “this” country. Codes that are known to be within a particular territory can be designed to be much shorter. For example, every location in The Netherlands can be uniquely specified with at most 6 letters . Even in a large country like India, at most 7 letters are needed.
> 6. Short codes are reserved for areas where the population density is high. For example, every locations in The Netherlands can be represented by a unique 6-letter mapcode. However, the majority of the population is concentrated in a dozen urban areas totaling less than 3,000 km2 (1,800 square miles). By reserving the 5-letter mapcodes for these areas, half the population of The Netherlands can be found using 5-letter codes. On average, mapcodes for relevant locations in The Netherlands are thus closer to 5 letters than to 6 letters. In fact, a significant percentage of the population can be found in 100 km2 of city centers, which can be covered by 4-letter mapcodes.
> Based on these ideas, we envisaged a system that would work anywhere on Earth, and would (on average) provide the shortest possible codes to everybody. By using massive amounts of data gathered over the past 30 years by mapping company Tele Atlas (merged into the TomTom Group in 2008), a data table was constructed ...
> Finally, on top of any and all national mapcodes a location may have, it also always has a 9-letter, context-less map code.
> To understand mapcode accuracy, you need to understand that a specific mapcode defines a specific location X, but represents all the locations within a certain distance meters of X. For example, the Dutch mapcode “49.4V” decodes into coordinate 52.376514, 4.908542. This does not only mean that coordinate 52.376514,4.908542 can be represented by mapcode 49.4V, but that all coordinates within roughly 5 meters of that coordinate can also be represented by mapcode 49.4V.
(it continues to describe "high-precision mapcodes")
Why did they make it?
> The mapcode system was revived and worked out in 2006 when TomTom decided to expand their operations to countries like India and China. It was difficult to sell navigation devices in these countries, among other things because a significant part of the population lives without address, lacking not just house numbers but often even street names, which often made it hard or even impossible to enter a destination. It was thought that the introduction of a simple and ubiquitous system for representing locations (and hence destinations) would in due time make navigation devices as welcome there as anywhere else.
There is already a service like this that uses 3 words instead of that weird string: http://what3words.com
I started work on something pretty much like this about 5 years ago but never pursued it for various reasons. I still have one of the registered domains with nothing to show for my preliminary work: www.tinynav.co.uk I got as far as designing the encoding scheme, including a database of point types (house, utility pole, ancient monument, park, private event etc..), together with special codes for corporates to use fo…
" A short address for any location on Earth" It doesn't check out: Surface Area of Earth: 510.1 * 10^6 km^2 Distinct map codes: 36^5 = 60.466176 * 10 ^6 Area of 1 map code = 8.4 km^2 Oh! It's narrowed by country... so it doesn't address any location on Earth. Only populated areas. If you want to actually refer to ANY location on Earth, there's another system, Ham Radio grids. It uses four to six digits and refers to…
I'm a little confused about what this replaces, but it's definitely not postcodes. * Postcodes have a specific meaning: they're both a geographical area and a mail delivery zone (at least in the US). Replacing one short code with another, which requires a different and less reliable third-party service to correctly decode, doesn't seem like a good idea. * Latitudes and longitudes are unambiguous, well-understood, and…
> latitudes/longitudes, unless we're talking about shortening their representation. That's a much smarter idea than this mapcode system. It would make sense to replace the base-10 representation with base 36.... at least in the Roman alphabet. It would probably be smarter to pick a base that works with the world's alphabets. Oh yeah, not all the world uses alphabets! But even then, it's not that huge of an improvemen…
> Mapcodes can be easily translated between several different alphabets. The default system is based on the roman alphabet. Mapcodes in other alphabets are generated by character substitution.
And it's not based on representation of lat/lng, which is why it's more of an improvement:
> As explained in the previous section, by reserving short codes for the most densely populated areas, mapcodes for addresses (i.e. places that people need to visit) are on average as short as theoretically possible, within the limits we set for ourselves. One such limit is to use only rectangular areas in our definitions. Another is to limit the size of the “context” data table to about 16,000 records. Probably the most relevant design choice was the choice of character set. For example, had we allowed both capital and lowercase letters, 3 times as many people could have 5-letter codes instead of 6-letter codes.
> The mapcode system allows about 100 km2 of a territory to be covered by 4-letter mapcodes. These are usually reserved for the capital city. About 6,000 km2 can be covered by 5-letter mapcodes . Roughly 250,000 km2 can be covered by 6-letter mapcodes. If a territory is larger than that, the remainder requires 7 letters. A few territories on Earth (notably, Australia, Brazil, Canada, China, India, Mexico, Russia and the USA) are large enough to merit 8 letters, but these actually consist of sub-contexts, i.e. people there live in a state, republic or oblast much like people elsewhere live in a country. Within such a sub-context, mapcodes are shorter.