2 megameter is a short trip (about 1250 miles)? I made this trip three
times in this last year. This is almost exclusively Interstate usage
(think German Autobahn).
On 05-May-21 03:32, Felix Hartmann wrote:
Really, routing over long distances on highways? I haven"t met people
using a Garmin
Huh, that statement is wrong. Garmin uses OSM and they acknowledge that
fact. I own five Garmin receivers for car navigation and use Garmin maps
in the new ones and mkgmap generated maps in the older ones. I do not
use Google Maps in my phones for navigation at all.
On 05-May-21 02:42, Felix
On Wed, May 05, 2021 at 03:32:52PM +0800, Felix Hartmann wrote:
> Really, routing over long distances on highways? I haven"t met people using
> a Garmin GPS device routing via highways - however many who use it for
> recreational purposes - so routing over short distances.
Well, I am another one
@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] new branch low-res-opt to test improvements for
filters
On Wed, May 05, 2021 at 03:32:52PM +0800, Felix Hartmann wrote:
> Really, routing over long distances on highways? I haven"t met people using
> a Garmin GPS device routing via highways - h
at 300m there is no difference at all. Actually the patch will help you to
set lower DP level for 300m (that is resolution 23 in Basecamp) while
giving higher DP values for higher resolution. That came because for
contourlines it needs very low DP value for resolution 23, while if you
keep that
before misanderstandings arise, maybee you can post here screenshot's ?
by carrouting I mostly use 300 m details in cities. By using this
resolution, the map should very accurat, not simplified. By very long
travels 3 km details. Using 3 km, the map can bee simplified. I don't
know, how this
2021 10:17To: mkgmap-dev@lists.mkgmap.org.ukReply to: mkgmap-dev@lists.mkgmap.org.ukSubject: Re: [mkgmap-dev] new branch low-res-opt to test improvements for filters Hi Karl,But even then you will never use the overview map. What resolution are you actually using on your device if routing
Hi Karl,
But even then you will never use the overview map.
What resolution are you actually using on your device if routing on a
highway? I guess 19 or 20...
The thing is simply with high DP filter value that you can see the highway
pretty straight, but as the route itself is not simplifed that
Hi.
Sorry for getting into the discussion.
Routing over long distances is important, also via highways.
There can be multiple nearby exists along the way that one does not know by
heart and does not want to miss.
Quite often one (at least i) does not want to fiddle around with device while
oh yeah - and as long as you do not crash the size limit on the overview
map - just use a lower DP value then. Removing of the zig zags actually
enables you to use a lower DP value in the overview map - hence matching
the route actually better than before. Overview map is always pretty fast.
Just
Really, routing over long distances on highways? I haven"t met people using
a Garmin GPS device routing via highways - however many who use it for
recreational purposes - so routing over short distances.
Anyhow if you use a lower DP value no problem there. It's mainly if you
zoom out to overview
Hi all, I see this completly different : many people use osm data for
routing. Routing is the main purpose for using OSM. If routing [
/quote] : //it will look a bit strange [end quote] /is not akzeptable.
Thomas
Quote :.
So yes with very high DP values and lots of
__
> Von: mkgmap-dev im Auftrag von
> Felix Hartmann
> Gesendet: Mittwoch, 5. Mai 2021 08:42
> An: Development list for mkgmap
> Betreff: Re: [mkgmap-dev] new branch low-res-opt to test improvements for
> filters
>
> Hi Gerd,
> why does a road have
Gerd
Von: mkgmap-dev im Auftrag von Felix
Hartmann
Gesendet: Mittwoch, 5. Mai 2021 08:42
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] new branch low-res-opt to test improvements for
filters
Hi Gerd,
why does a road have pointers to lines in any level ex
: mkgmap-dev im Auftrag von
> Felix Hartmann
> Gesendet: Mittwoch, 5. Mai 2021 07:36
> An: Development list for mkgmap
> Betreff: Re: [mkgmap-dev] new branch low-res-opt to test improvements for
> filters
>
> well a waterway can be merged if it's displayed without a
det: Mittwoch, 5. Mai 2021 07:36
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] new branch low-res-opt to test improvements for
filters
well a waterway can be merged if it's displayed without arrows so it should not
have special handling.
A cliff cannot be merged, because i
ed ways. Looking at
> this now, maybe it is better to use the joined way instead of the fragments.
>
> Gerd
>
>
> Von: mkgmap-dev im Auftrag von
> Felix Hartmann
> Gesendet: Mittwoch, 5. Mai 2021 03:47
> An: Development list
s now, maybe it is better to use the joined way instead of the fragments.
Gerd
Von: mkgmap-dev im Auftrag von Felix
Hartmann
Gesendet: Mittwoch, 5. Mai 2021 03:47
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] new branch low-res
oh sorry, no I got confused. We don't need that difference based on level.
It's one list where we add all types that in the typfile lead to being
impossible to change direction and then of course any routable line can be
merged also at level 0 if it is not on that list and has no
oneway attribute.
I think the simplify 4 patch had some more improvements for contourlines -
but then I played around all the time with the DP values so it's hard to
compare. I do know that simplify v4 versus 3 back then was an improvement.
I think merging lines of different directions would be good too - with the
Hi all,
as a result of the thread about raster problems I've started this new branch.
First commit implements experimental options to specify values for
--reducePointError and --reducePointErrorPolygon for each resolution
Options are --simplify-filter-line-errors as replacement for
21 matches
Mail list logo
