Rich Gibson wrote:
> On 8/28/06, Andrew Turner <[EMAIL PROTECTED]> wrote:
>> Mateusz Loskot <[EMAIL PROTECTED]> wrote:
>> I would think the result would either be a table of "problems" and
>> solutions like the Wiki page Ari made (I tabelized it), or a "GeoZoo",
>> akin to O'Reilly's CodeZoo (http://www.codezoo.com/) that lists
>> various Geo-specific libraries and tools in various languages. So I
>> can just do: "KML export in C++" or something
>
> This looks like a design patterns sort of problem...start with a use
> case and move on. 'Parse GPS' is meaningful to a lot of people, and
> we'd be able to reach more with a 'pattern' like 'share GPS data
> between applications'
It sounds reasonable, but I'd add 1-2 levels of organization
to avoid huge tables, less readable.
How about "Mapping Hacks"-like organization by task (or better,
by hack:-)) and then language-solution matrix.
...
2. GPS
2.1 Share data between applications
lang/frmt | GPX | GML | ...
----------------------------------
C++ | bar | foo | ...
----------------------------------
Java | ... | ... | ...
----------------------------------
Python | ... | ... | ...
----------------------------------
| | |
I hope this ASCII art is readable.
Cheers
--
Mateusz Loskot
http://mateusz.loskot.net
_______________________________________________
Geowanking mailing list
[email protected]
http://lists.burri.to/mailman/listinfo/geowanking
