Hi,
first of all: Big thanks for 3 byte Garmin type support!
Attached patch add support for aerialway and move vineyard to own Garmin
type. Thanks.
--
S pozdravem/Best regards
Bc. Ondrej Novy
Email: n...@ondrej.org
Jabber: on...@njs.netlab.cz
ICQ: 115-674-713
Tel/Cell: +420 777 963 207
Index:
On Wed, 19 Aug 2009 23:18:02 +0200
Felix Hartmann wrote:
> Could you or someone try to modify this patch so that it compiles
> against mkgmap 1140.
Try attached.
Not been tested, so please verify it works as expected.
Cheers,
Mark
diff --git a/src/uk/me/parabola/mkgmap/osmstyle/ActionRule.j
Hi
Felix Hartmann schrieb:
> Why don't you directly compile with mkgmap?
>
Several reasons:
- it is much faster to store the contours in a file locally than
calculate them every time
- mkgmap does not download the files automatically, strm2osm does
- mkgmap is not capable of doing large areas
Thilo Hannemann wrote:
Am 19.08.2009 um 22:17 schrieb Simon Josefsson:
How do I use the test-map:all-elements feature?
(I have a problem with highway=service roads on my Legend HCx when it
uses Swedish, it labels the roads as "Allé" which I suspect is a
mis-translation of "Alley" -- solving
Torsten Leistikow wrote:
Moin,
finally I got my eclipse environment running and was able to build
mkgmap from source. So the next step was my first extension of mkgmap.
Until now a single OSM element was converted into a single garmin
element, i.e. the first one in the style file with the match
Am 19.08.2009 um 22:17 schrieb Simon Josefsson:
> How do I use the test-map:all-elements feature?
>
> (I have a problem with highway=service roads on my Legend HCx when it
> uses Swedish, it labels the roads as "Allé" which I suspect is a
> mis-translation of "Alley" -- solving this might require
Am 19.08.2009 um 22:01 schrieb char...@cferrero.net:
> I've created a partial list for the GPSMap76Csx though my aim was
> slightly different (I wanted to understand what symbols the hex codes
> translated into). Is there any way we can fork this page into
> separate pages per unit otherwise it w
Thilo Hannemann writes:
> Hi everybody,
>
> just wanted to advertise the list of POIs at
> http://wiki.openstreetmap.org/wiki/OSM_Map_On_Garmin/POI_Types
How do I use the test-map:all-elements feature?
(I have a problem with highway=service roads on my Legend HCx when it
uses Swedish, it
Quoting Thilo Hannemann :
> Hi everybody,
>
> just wanted to advertise the list of POIs at
> http://wiki.openstreetmap.org/wiki/OSM_Map_On_Garmin/POI_Types
>
> The purpose of this list is to collect experimental evidence about
> which POIs are displayed on which units. There are notable dif
Hi everybody,
just wanted to advertise the list of POIs at
http://wiki.openstreetmap.org/wiki/OSM_Map_On_Garmin/POI_Types
The purpose of this list is to collect experimental evidence about
which POIs are displayed on which units. There are notable differences
between the different uni
Greg Troxel a écrit :
>> and I have lots of errors like this one :
>> GRAVE (RoadNetwork): Road Avinguda Meritxell; FIXME (OSM id 6182097)
>> contains zero length arc
>> GRAVE (RoadNetwork):
>> http://www.openstreetmap.org/?lat=42.50842&lon=1.53407&zoom=17
>> GRAVE (RoadNetwork): Road Avinguda Meri
Nop wrote:
Hi!
Paul schrieb:
Unless you already have data for Srtm2Osm then this approach will not
work as NASA has moved the data and Srtm2Osm is no longer being updated.
This is no longer true. Bomm has taken over and updated srtm2osm, it is
working again and I am currently even te
Hi!
Paul schrieb:
> Unless you already have data for Srtm2Osm then this approach will not
> work as NASA has moved the data and Srtm2Osm is no longer being updated.
This is no longer true. Bomm has taken over and updated srtm2osm, it is
working again and I am currently even testing some improve
Paul writes:
> Ralf Kleineisel wrote:
>> On 08/19/2009 12:56 AM, Nolan Clifford wrote:
>>
>>> I spent a lot of time today trying to figure out the above and did not
>>> succeed. Would anyone be willing to produce a step by step guide on
>>> how to achieve it please?
>>
>> I did it this way
Ralf Kleineisel wrote:
> On 08/19/2009 12:56 AM, Nolan Clifford wrote:
>
>> I spent a lot of time today trying to figure out the above and did not
>> succeed. Would anyone be willing to produce a step by step guide on
>> how to achieve it please?
>
> I did it this way:
>
> Create OSM file w
Felix Hartmann writes:
> I think we should open a wiki page where we should add what
> line/poi/polygon types are possible.
There is already resources/garmin_feature_list.csv. It would be nice to
add to that, so it's in the sources, rather than having a duplicate list
that has to stay in sync.
Mark Burton wrote:
That list is in my eyes just crap when it comes to extended types, as
any of those lines / points / polygons will only be shown if defined in
typfile, and many others if defined too. I only don't know whether there
are any regions that will not be shown, or only shown in Maps
Mark Burton wrote:
That list is in my eyes just crap when it comes to extended types, as
any of those lines / points / polygons will only be shown if defined in
typfile, and many others if defined too. I only don't know whether there
are any regions that will not be shown, or only shown in Maps
> That list is in my eyes just crap when it comes to extended types, as
> any of those lines / points / polygons will only be shown if defined in
> typfile, and many others if defined too. I only don't know whether there
> are any regions that will not be shown, or only shown in Mapsource.
My
2009/8/19 Felix Hartmann :
> That list is in my eyes just crap when it comes to extended types, as any of
> those lines / points / polygons will only be shown if defined in typfile,
> and many others if defined too. I only don't know whether there are any
> regions that will not be shown, or only s
Mark Burton wrote:
Hi Felix,
I did not look into the patch, but does it mean that I could use in my
style-file the following:
[0x01234 resolution 22]?
And then off course add a definition for this type in my typfile.
Or is there more that needs to be changed?
Actually, my knowle
On Wed, Aug 19, 2009 at 10:44 AM, Nolan Clifford wrote:
> Am I on the right track with the following approach:
> [...]
I think what you are doing is essentially correct. I believe, however
that the code still needs to be refined somewhat.
When I tested this (which I have not done for some time),
Hi Felix,
> I did not look into the patch, but does it mean that I could use in my
> style-file the following:
> [0x01234 resolution 22]?
>
> And then off course add a definition for this type in my typfile.
>
> Or is there more that needs to be changed?
Actually, my knowledge of extended
svn commit wrote:
> Version 1140 was commited by markb on 2009-08-19 10:00:27 +0100 (Wed, 19 Aug
> 2009)
>
> Added support for extended types.
>
> These are sometimes called '3-byte types' but the upper 8 bits of the
> type is not encoded in the map objects (just the lower 16 bits) so any
> non-z
Version 1140 was commited by markb on 2009-08-19 10:00:27 +0100 (Wed, 19 Aug
2009)
Added support for extended types.
These are sometimes called '3-byte types' but the upper 8 bits of the
type is not encoded in the map objects (just the lower 16 bits) so any
non-zero value for the upper byte ha
Ralf, thanks for posting your instructions. I will try them out
later. Is is it possible to do without srtm (I'm on a mac and want to
avoid executing windows commands)? Am I on the right track with the
following approach:
1. Download file(s) from say
http://dds.cr.usgs.gov/srtm/version2_
On 08/19/2009 12:56 AM, Nolan Clifford wrote:
> I spent a lot of time today trying to figure out the above and did not
> succeed. Would anyone be willing to produce a step by step guide on
> how to achieve it please?
I did it this way:
Create OSM file with contours:
mono Srtm2Osm.exe -larg
27 matches
Mail list logo
