My main concern is should I import data as is or optimize this data as
they are quite detailed? Also each region border is one separate
polygon. Should I merge neighbour region nodes and import seperate
border lines or again should I leave data as is?
While out riding just now I crossed
Hi,
i added the feature for rocks, but its not yet available as a tag.
http://www.openstreetmap.org/browse/changeset/1369385
It's a good thing to have as it's a marine hazzard, and not sure why it's
not listed, as they can be above or below water, perhaps as a caution icon?
http://wiki.openstreetm
On Sun, May 31, 2009 at 2:45 AM, Peter Herison wrote:
> Karl Newman wrote:
> > Peter Herison wrote:
> >> Iván Sánchez Ortega wrote:
> >> AFAIK, the biggest microSD card that you can put into an eTrex is a
> >> 2 GB card (the bigger microSD-HC cards won't work).
> > This is for firmware 2.80. With
Karl Newman wrote:
> Peter Herison wrote:
>> Iván Sánchez Ortega wrote:
>> AFAIK, the biggest microSD card that you can put into an eTrex is a
>> 2 GB card (the bigger microSD-HC cards won't work).
> This is for firmware 2.80. With 3.00 you can use SD-Cards up to 4GB.
> But it's irrelevant because
Hello,
have you removed the kill switch inside polyshp2osm.py?
In the latest version of the file I don't see the -s switch. Also -l is
the output_location. So if you want to output your file to the c drive
with the prefix open, you would use the following option: -l C:\open. It
will create files t
Iván Sánchez Ortega wrote:
> El Sábado, 30 de Mayo de 2009, Paul Houle escribió:
>> I just got a Garmin Etrex Vista HCx that I'd like to use for viewing
>> Openstreetmaps and for creating tracks I can upload. I'm about to buy
>> an SD card for this: how big of a card do I need to hold Openstreetm
6 matches
Mail list logo
