Sorry for my previous message. Clicked on the wrong button.
El 29/03/11 17:48, Felix Hartmann escribió:
On 29.03.2011 17:25, Carlos Dávila wrote:
El 29/03/11 16:50, Steve Ratcliffe escribió:
The aim is not just to remove options, but is much more about
improving how it works in
The aim is not just to remove options, but is much more about
improving how it works in the default case without options, or to
remove the need for various options altogether that only ever existed
to work around some bug that is fixed or could be fixed very easily.
The problem with
El 29/03/11 16:50, Steve Ratcliffe escribió:
The aim is not just to remove options, but is much more about
improving how it works in the default case without options, or to
remove the need for various options altogether that only ever existed
to work around some bug that is fixed or could be
On 29.03.2011 17:25, Carlos Dávila wrote:
El 29/03/11 16:50, Steve Ratcliffe escribió:
The aim is not just to remove options, but is much more about
improving how it works in the default case without options, or to
remove the need for various options altogether that only ever existed
to
Also, if I'm not sure whether it is called Avenida de la
Libertad, Avenida la Libertad or Avenida Libertad, using spell menu
is much faster. Would it be possible to get partial searches working in
address search?
I know that this is technical possible and expect it to work in the near
future.
Hi
There is a new branch for an overhaul of the options. There are a
number of recent (and not so recent!) posts about options that are
badly documented, have the wrong defaults or just plain shouldn't
exist.
The first couple of things I plan to do in preparation are:
1. Make it possible to
Hi
I think it would be better for the user of mkgmap, that they get with
the same used parameter the same result. Opt-in is better then opt-out.
If I set --route, map should contain routing information and if I don't
set --route, there shouldn't be any routing information in the map. I
think
Things already on the list include: --charset, --remove-short-arcs,
--ignore-osm-bounds, setting options inside the style (which can
already be done, its just not really used properly).
.
Is there any reason to remove --ignore-osm-bounds or is there any
replacement? I use it very often for
Hi Steve,
On Fri, Mar 25, 2011 at 01:17:22PM +, Steve Ratcliffe wrote:
Things already on the list include: --charset, --remove-short-arcs
I agree that --charset (and possibly --latin1) should be removed, but
what is bad about remove-short-arcs? I thought that it is useful when
the map has
Hi
There is a new branch for an overhaul of the options. There are a
number of recent (and not so recent!) posts about options that are
badly documented, have the wrong defaults or just plain shouldn't
exist.
That's great! I think we should invest some time on mkgmap
documentation. Some
On 25.03.2011 18:22, Marko Mäkelä wrote:
Hi Steve,
On Fri, Mar 25, 2011 at 01:17:22PM +, Steve Ratcliffe wrote:
Things already on the list include: --charset, --remove-short-arcs
I agree that --charset (and possibly --latin1) should be removed, but
what is bad about remove-short-arcs?
11 matches
Mail list logo
