On Thu, Apr 15, 2010 at 11:52:41PM +0200, Daniela Duerbeck wrote:
>I think here could be (new) functions like "p.getWebsite" and so on called.
I think that it would be better to use the mkgmap: name space for it.
The style definition would translate the attributes to, say,
mkgmap:description, and
Hello list,
As far as I understand, if I wanted to make, let's say, a hypothetical
interstate cycleway from any OSM motorway with the mkgmap, I'd have a
line in my style like:
highway=motorway {add access = no; add bicycle = yes; add foot = yes}
[0x16 road_class=4 road_speed=1 resolution 14]
And there are many other things that can be easily recycled.
Have you ever been lost in an unknown city and asked yourself: Where is the
next hot spring?
Garmin thinks that finding hot springs is essential, so they gave them a menu
item.
Dani
P.S: Etrex Users can do the same, but they have no
Marko Mäkelä wrote:
> Is the addr:* translation currently hardcoded in mkgmap? Where is it?
>
I think here: MapBuilder.java
Search for "FIX MY ADDRESS".
Around it there are function calls like "p.getStreet()" and so on.
I think here could be (new) functions like "p.getWebsite" and so on call
On Thu, Apr 15, 2010 at 01:02:08PM +0200, Minko wrote:
>I have been experimenting to 'fool' my Garmin to use addr:streetname etc for
>some other information and this trick worked.
Is the addr:* translation currently hardcoded in mkgmap? Where is it?
I found one oddity last year: addr:housenumbe
Minko wrote:
> Hi,
> It would be great to be able to add more information to the pois.
> At the moment the information that can be seen is streetname, number, postal
> codes and placenames
> in the properties of some of the pois (the gps can't show this properties box
> on all kinds of pois unfor
Toby Speight wrote:
> POIs with address information have this in their description when viewed
> on my eTrex, but the generation of this appears to be hard-coded. It
> would be nice to be able to have different information in there - opening
> hours for shops, or telephone numbers for pubs and hot
Hi!
In the Oregon text strings can be easily changed since they are defined
in xml-files in a directory inside the flash file system.
I recycled now e.g. truckstop (0x2f16) to amenity=taxi.
#amenity=fuel & fuel:HGV_diesel=yes [ 0x2f16 resolution 19 ] must be
commented out in the point file,
amen
> At the moment processing of multipolygon boundary relations creates a
> lot of unwanted effects (artificial boundaries on tile bounds, lots of
> warnings etc.).
>
> The patch excludes the boundary relations from the multipolygon
> processing. This can be changed with the new option
> --process-bo
> On Mon, Apr 12, 2010 at 12:51 PM, Apollinaris Schoell
> wrote:
>> relation looks good. You should try to create just a single tile first to
>> see if it's mkgmap or splitter.
>> splitter clips ways from relations outside of the tile and this is a known
>> problem. recent versions of mkgmap ca
Hi,
It would be great to be able to add more information to the pois.
At the moment the information that can be seen is streetname, number, postal
codes and placenames
in the properties of some of the pois (the gps can't show this properties box
on all kinds of pois unfortunately)
I have been ex
Toby Speight (t.m.speight...@cantab.net) wrote:
> POIs with address information have this in their description when viewed
> on my eTrex, but the generation of this appears to be hard-coded. It
> would be nice to be able to have different information in there - opening
> hours for shops, or telep
POIs with address information have this in their description when viewed
on my eTrex, but the generation of this appears to be hard-coded. It
would be nice to be able to have different information in there - opening
hours for shops, or telephone numbers for pubs and hotels, for example.
So, would
13 matches
Mail list logo