2 ms·
Or it's an indication that people are throwing up use cases that weren't what I was designing the code for. For example, people have said that the ability to c
by jgrahamc 15y ago
Or it's an indication that people are throwing up use cases that weren't what I was designing the code for.
For example, people have said that the ability to compare two codes is important to see how close they are. They've said this without justification and it is not a use case for which I designed the code.
Also, people have said that arbitrary levels of accuracy are important, they are not needed for a navigation device being used by an individual to get to a location.
Others have brought up the issue of using it instead of postcodes. It was not designed for that either.
- estel 15y agoBut isn't it the case that a system for encoding location is more likely to be widely accepted if it can be universally applied to a wide range of use-cases?
- qntm 15y agoMaybe wide acceptance isn't the use case! It's okay to intend a tool for a specific purpose! It's okay to do one thing well.
- owenmarshall 15y agoThen the blog post should mention what it does well. In my case, I figured out one place where it would: http://news.ycombinator.com/item?id=2674732 http://news.ycombinator.com/item?id=2674732 This post left too many blanks, and we are trying to fill them in. If you don't show people why we should use your tool, and why it is better than the alternatives, people may not figure them out.
- politician 15y ago"For example, people have said that the ability to compare two codes is important to see how close they are. They've said this without justification and it is not a use case for which I designed the code." So, actually, that property would be pretty helpful for deduplication.
- owenmarshall 15y ago>For example, people have said that the ability to compare two codes is important to see how close they are. They've said this without justification and it is not a use case for which I designed the code. I've raised this objection, but I still think it is quite valid. Compare "43 Montgomery St" to KN4 HNA M33B. First off, I'll tell you immediately which one I find more memorable! I can use any number of mnemonics to store the first; the second is near incomprehensible. Ignoring even that, people have quite a bit of experiential knowledge of local street addresses. Give most people an address -- even an unfamiliar one -- and they can provide with some degree of accuracy what's around, a way to get there, etc. For local use only, this encoding doesn't make sense to me. But, if we assume that the typical user of SOC would be a person who strictly uses their GPS to navigate from point to point, this encoding has some advantages. Another possible use case would be for travelers. Costa Rican addresses are based on distances from landmarks, and as a traveler I quickly learned that many of the landmarks refer to buildings that were demolished in the 1970s! In that case, 75 m Norte de la Coca Cola means exactly as much to me as HFW QMJ BBBE, and this encoding could actually be entered into my GPS.