Greg Troxel-2 wrote
> I don't think it's off topic at all.
Well, I think it would be better to open a new thread, because this one is
about a default typ file for mkgmap.
Greg Troxel-2 wrote
>> project to add some non-OSM data to my maps but I thought the only way to
>> do this was with osmosis,
Hi all,
this is for sure confusing. I think the problem is in the data flow.
Current implementation works like this:
1) Single OSM ways are passed to the style rules
2) The style can create 0, 1 or more routable lines (=roads) and 0 or more
other lines for this single OSM way.
3) The next step is
On my Montana, those settings don't seem to do anything. I am getting
better labels than with qmapshack, some primary hwy labels with level
2-6, not much change from 2-6, some additional labels at level
1/res23. I wonder if part of the problem may be that the names are
very long, I'll try s
Lorenzo Mastrogiacomi writes:
> If I understand correctly I would say yes.
> unclassified roads should be tagged with name=* in osm if they have a
> name and should not take names from nearby roads.
I am really not following what's going on.
Most unclassified roads will have a name and some mig
Ben Konrath writes:
> I realize this is a bit off-topic on this thread but I'm curious to know
> your process for combing non-OSM data with splitter. I was just starting a
I don't think it's off topic at all.
> project to add some non-OSM data to my maps but I thought the only way to
> do this
If I understand correctly I would say yes.
unclassified roads should be tagged with name=* in osm if they have a
name and should not take names from nearby roads.
Lorenzo
Il giorno dom, 02/12/2018 alle 18.29 +, Gerd Petermann ha scritto:
> This doesn't happen because of road merging, it is a
This doesn't happen because of road merging, it is a - normally - wanted result
of the housenumber processing.
Maybe I should change the code so that unclassified roads are not treated like
service roads here.
Gerd
Von: mkgmap-dev im Auftrag von Lorenzo
It seems to me that road merging in presence of addr:place addresses
causes the incorrect propagation of labels to nearby streets.
For example, I see this unnamed road gets the label "Strada Provinciale
Potentina".
https://www.openstreetmap.org/way/209592070
This name does not come from an addres
Hi Lorenzo,
an unnamed service road should solve the problem because the numbers are not
assigned to the same road.
Gerd
Von: mkgmap-dev im Auftrag von Lorenzo
Mastrogiacomi
Gesendet: Sonntag, 2. Dezember 2018 18:17
An: Development list for mkgmap
Bet
Ok Gerd, no worries :)
I guess a service road should also have a name and different from the
main road to avoid merging because in my previous example there were
already several unnamed roads around the housenumber. Right?
https://www.openstreetmap.org/node/5569912919
Lorenzo
Il giorno mer, 2
I just generate an XML file with negative ids like:
...
and give as a parameter to splitter after the main osm.pbf map data
file.
Ticker
On Sun, 2018-12-02 at 16:02 +0100, Ben Konrath wrote:
> Hi Greg,
>
> On Tue, 27 Nov 2018 at 18:21, Greg Troxel wrote:
> > Semi-related, I
Hi Greg,
On Tue, 27 Nov 2018 at 18:21, Greg Troxel wrote:
> Semi-related, I am carrying a diff to render "boundary=parcel"; I
> include state parcel boundary data with osm data in splitter. I have no
> idea how many others want this, but given that parcel data is not in
> OSM, merging while map
On my Etrex:
Map Setup > Advanced Map Setup >
Zoom Levels >
Auto zoom: on/off
Zoom Levels >
4 controls for the resolutions at which following appear
Points/Waypoints/Street labels/Land Cover
Text Size (Points, Streets, Etc) >
4 controls for Points/Waypoints/Street l
13 matches
Mail list logo
