Hi Felix,
I just played around a bit in Mapsource, and couldn't notice ANY
difference. If routing does not work somewhere without this patch, it
will not work either with the patch. If it works without patch, it does
so with patch too. (I installed the otherwise exact same map twice in
Felix,
Where TYPE is the Garmin line type to use (decimal, not hex).
The option parsing code doesn't seem to know about hex so it only works
with decimal types. A pain, but I can't be bothered to do anything
about it.
Mark
___
mkgmap-dev mailing
Thanks to those who have tried yesterday's table A patch. Seems like it
hasn't caused any problems (so far).
Today's offering includes the table A tweak but it also increases one
of the limits that determine when a route centre needs to be
sub-divided. As far as I can tell, the limit was
Felix,
After playing around a bit on my Vista HCx I did notice slightly
different routing too. The maximum distance that it manages without
route calculation error did not change however.
On the HCx, I just tried an 800Km route from where I live to Thurso and
it took quite a while (stuck
Hi Marko,
Sorry, I will go back to my cave, which hasn't seen the light of Windows. :-)
No need to be sorry. I only use mapsource as part of my mkgmap
development (XP on VMWare on Linux, of course). Personally, I don't
care much if the mapsource find stuff doesn't work but having
implemented
On Thu, 24 Sep 2009 23:21:24 +0200
Chris-Hein Lunkhusen chris66...@gmx.de wrote:
Hi,
I have some issue at the position 51.123 / 7.19:
http://img34.imageshack.us/img34/9803/bild1zh.png
I see this on my own map and on Lambertus' OSM routable.
In this area multipolygons are used very
The attached small patch implements a --rhd option that sets a couple
of bits in the map data that tell the GPS that the vehicles are RHD and
that roundabouts are navigated in a clockwise direction. This will make
the little roundabout piccy shown in the top left of the screen (on the
Nuvis, at
As suggested, moved from rhd to dol.
Two options are now available --drive-on-left and --drive-on-right.
By default, you should not have to specify either because mkgmap now
determines the side of the road to drive on from the direction
of the first roundabout it processes. But if you don't
Hi Dermot,
I've tried this on my map of Ireland and it works fine. Unexpectedly,
though, I see _no_ errors for wrong way roundabouts. One theory is
that our roundabouts are all pointing the right way...
Hmm, that would be rather amazing.
Is there any verbose mode I need to have on to see
Hi Carlos,
Since yesterday I get the error below trying to compile France and Spain
maps (from Geofabrik):
java.lang.AssertionError: relative pointer too large for 14 bits
Hmm, I know where this is coming from but would like a little more info
before I try a fix. Please use r1238 (just
Hi Carlos,
Here it is:
java.lang.AssertionError: relative pointer too large for 14 bits (source
offset = 1115876, dest offset = 1124268)
Thanks for that, it was useful.
Please try r1240, it could possibly fix the issue.
Cheers,
Mark
___
v3 - now reverses the order of the points in roundabouts that have the
wrong direction so that routing is more likely to succeed.
v2 - now prints OSM URL of first point in dodgy roundabout.
As suggested, moved from rhd to dol.
Two options are now available
Hi Marko,
You can always filter them out with grep if you don't want to see them.
Cheers,
Mark
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Marko,
You can always filter them out with grep if you don't want to see them.
Sure, I could. However, many of the warnings have been genuine
(such as sidewalks or cycleways being placed too close to the main road
or main crossing). I would also like to see any new warnings as they
v4 - improved quality of direction detection
v3 - now reverses the order of the points in roundabouts that have the
wrong direction so that routing is more likely to succeed.
v2 - now prints OSM URL of first point in dodgy roundabout.
As suggested,
Felix,
Additionaly It would be great, if the road-name-pois option could be
dropped
Just don't use it. Seriously, it was only intended to be a quick and
dirty way of being able to search for streets. When the global search
stuff matures it will almost certainly be redundant. But unless
Felix,
Ups, sorry I was not clear. I meant that we should include into the
global address index also streets without osm addresses. So that any
street present in the map, can be searched for by the address search
and not only proper addresses with housenumbers (because we don't have
v5 - added --check-roundabouts option to explicitly enabled
roundabout checking/reversing.
Not had much feedback on this yet, anyone (apart from Dermot) tried
it? Even if you don't drive on the left (almost the whole world?) you
may care to try out the roundabout checking. About 3% of all the GB
Hi Charlie,
If there's a way you can share a pre-built jar file then I'd be happy to
check it out as I spent ages fixing roundabouts in the Languedoc earlier
this year.
I've mailed one directly to you.
(Another common issue I've noticed is ways that don't meet: presumably
these were
Hi Paul,
Either you've fixed all the GB roundabouts or I've done something wrong
as I get no additional output when compiling a map of GB with this patch
applied.
If you have fixed them all then I see no negative side effects either
I very much doubt that I've fixed every one so I think
Paul,
I don't know about putting logging.properties into resources. I specify
the file to use by giving this option to java:
-Dlog.config=logging.properties
However, the logging.properties file I quoted did have different levels
of logging to the console and the log files, the console was less
Annoyingly, motorway exit POIs don't show up on my Nuvi so I thought
that the next best thing would be to label the exit roads with the exit
name (number). This patch does that in a generic way. It introduces a
new facility:
If a way (of highway type X) has a POI for its first point and that
Hi Dermot,
That finally worked for me too. That revealed to me that there were in
fact about 15 wrong-way roundabouts in Ireland. I'm happy to say that
there are now none at all :D
Very good.
One question, though - I'm also getting a few warnings like the following:
2009/10/03 15:06:21
Hi Ralf,
Hi all,
I have build a map with version 1247 and the following options:
--latin1 --route --tdbfile --remove-short-arcs --add-pois-to-areas
--link-pois-to-ways
Mapsource and my Etrex routes me through the bollards on Marktstraße
(setting was for motorcar).
Hi Ralf,
I know what the problem is. The code currently checks for the access
tag before the style file is processed so if the bollard doesn't have
an access tag already, the POI isn't linked to the way as it needs to
be for this to work.
Sorry for the hassle, I shall dream up a fix. In the
Hi Martin,
I also noticed this behavior at a bollard in my area.
Since about the same time(~2 weeks ago), there also were problems with
some turn restrictions being ignored.
If there are problems, it will be something else that's wrong because
they are not related.
It seems to me that only
Hi Paul,
When the turn restrictions were added was the no_u_turn restriction
implemented as I have recently been told by my 605 to make a U turn
where I have specifically added a no_u_turn restriction?
I feel it's only fair to mention that some of these no_u_turn
restrictions are flagged
Hi Paul,
Can I make this a feature request then? :) Consider the following
A B C
+---
|
---+
D E| F
|
\/
G
ABC is oneway in direction ABC
FED is oneway in direction FED
BE is twoway but is marked with
Hi Charlie,
I must be doing something wrong. I've just run this on the UK using
--drive-on-left and --check-roundabouts and it seems to be flagging
roundabouts that are correct (i.e. clock-wise).
Here's some examples:
2009/10/04 19:16:31 WARNING (StyledConverter): Roundabout 4831867
Hi Carlos,
Well, my ascii art is not so good ;-) . X should be on top of B.
I worked it out.
You're right, what I suggested won't work in that situation.
Cheers,
Mark
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
v2 - various changes - should now work with junctions that have more
than 1 side road - should be able to treat exits from roundabouts in
the same way as side roads.
-
The attached patch (which also includes the drive-on-left patch because
it's based on that) attempts to
Hello Martin,
2009/10/4 Mark Burton ma...@ordern.com:
Hi Martin,
I also noticed this behavior at a bollard in my area.
Since about the same time(~2 weeks ago), there also were problems with
some turn restrictions being ignored.
If there are problems, it will be something else
Hi Marko,
I tried --drive-on-right --check-roundabouts, and the generated map is of
the same size as with r1260. There are much more diffs than the time
stamps, though. This is with 3 tiles and 2 cores.
The code that calculates the arc headings is probably producing a
slightly different
You are building your maps with assertions enabled, aren't you?
Cheers,
Mark
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Nakor,
I can provide the osm data (22 Mb gzipped) if needed.
I think I need to see that because I tried with just a small region
around the problem area and it could route OK.
Can you put that data onto a web server somewhere?
Cheers,
Mark
___
Hi,
I can confirm that there are routing issues with that map, don't know
what the problem is at this time so I cannot give an ETA for a fix. I
will work on it as time allows.
Cheers,
Mark
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
Hi Nakor,
I haven't yet discovered why it appears to be impossible to cross
certain longitudes. I will keep thinking about it and, hopefully,
come up with a solution sometime.
However, that map is riddled with non-connected ways so even if the bug
is fixed, routing will still be very unreliable
This is something that was briefly discussed not too long ago and the
idea is that a road's speed or class can be modified by the
presence of a POI that defines new values for either/both of them. This,
hopefully, will make ways that have stuff like traffic signals and
crossings, etc. less
I have received zero feedback on the recent arc tweezing patch. I
believe that in its latest form (v4), it provides much improved
routing instruction quality. In particular, it should give you fewer
instructions to keep left/right or even turn left/right when you are
continuing on a long road
On Wed, 14 Oct 2009 08:45:52 +0200
Ralf Kleineisel r...@kleineisel.de wrote:
On 10/14/2009 01:14 AM, Mark Burton wrote:
These tags expect an integer value, optionally preceded by a + or -
which make the adjustment relative to the original value.
This is a good idea.
But I think
Hi Chris,
Does it work with and without the --ignore-maxspeeds option?
It occurs after the maxspeed processing.
By the why: Is the --ignore-maxspeeds option documented
somewhere? All I understand is that it turns off
the default mkgmap handling of maxspeed tags, so that
only the
Just realised, as the patch is now, it will only apply one delta to the
way's speed/class. If a way has multiple POIs that can change the
speed/class, only the last one processed (the order is, essentially,
random) will have an effect.
Cheers,
Mark
Felix,
While writing action rules to try out the link pois to roads I just
wondered whether mkgmap only looks at access/bicycle/motorcar =no or
also other values like = delivery / destination / forestry /
agricultural / private ?
It only looks at vehicle classes as in the list you
It would be great to have --delete-tags=motorcar,motorcycle (private/no)
Actually I'm a bit afraid of people putting access=no motorcar=forestry
but forgetting bicycle=yes or foot=yes.
What would best be --delete-tags/resources/deletetags and put all tags
with values into that file as a
Hello Ivan,
I think I found where my extended-type lines disappear. They are simply not
taken into account when estimating subdivision size, i.e:
MapArea.java, lines 389-394
private void addSize(MapElement p, int[] sizes, int kind) {
-if(p.hasExtendedType()) {
-//
Hi Ivan,
I will try to play with small-area osm contour file (as lines are usually
ordered by elevation) and map them via style to extended lines. There will
be no subdivision split as there are no other elements that will cause it.
Last lines drawn (i.e. certain elevation) would indicate
Felix,
Just a small question. If I add to a poi { add road_speed_min='-1'; add
road_speed_min='1' } what happens if the original road had road_speed=0
will it be increased or stay at 0?
(I assume and hope for the latter).
Yes, the min/max tags only have an effect if mkgmap:road-speed or
Felix,
Working Great!
Saves me about 10% processing time compared to removing access tags via
style-file as action rules!
Also gets rid of stupid things like ref=0 that are present on loads of
roads in Austria due to the import.
Very good - if you are happy with what it does, I shall
Felix,
Are you happy that the tweeze arcs stuff doesn't actually break
anything (compared to before)? If so, I shall commit it in its present
form
Better than the status quo, so would support committing it (and also for
a merge of the mdr branch into trunk, because at some point this
Sorry, ignore this - posted to ML by mistake.
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Carlos,
What happens if the distance between the tagged POI and the
next/previous points is very long? Shouldn't it be a limit to the length
affected by the reduction/increase of road_speed/road_class?
Arguably, yes. However, I ran out of energy before I could implement
that. The bollard
Carlos,
Arguably, yes. However, I ran out of energy before I could implement
that. The bollard code does very similar things but, to be honest, I
can't really be bothered at this time. If someone else wants to
implement that, I will happily integrate their patch. My feeling was
that in
As part of my current thrust to improve the mapping of the world's
roundabouts, I have added an option that checks the sanity of
roundabout flare roads. It probably can be fooled by some valid data
but it's pretty good at finding bad roundabout flares. Specifically,
it's looking for these errors:
Hi Felix,
here is the last version (working up to 1277 flawless)
Well, I can't see where the problem is at the moment. I did find and
fix a trivial bug while looking at the code introduced by 1278 so the
time was not wasted!
When you say created with continue command, what does that mean? Can
OK, let's try again. The attached patch adds a duplicate() method to
the Way class.
It's only really needed when using the continue patch. You will have to
edit StyledConverter.class in the do while loop where it's
looping around until foundType.isFinal() and in the body of the loop
it is
Thanks for your work, doesn't show any improvements for me however (but
adds about 25% to compile time).
25% is a huge overhead, that's not just the time taken to duplicate
the way. Perhaps the lines really are getting processed in their
entirety now and some other reason is causing them not
Ups, sorry replied to myself when wanting to correct the above
statement. Compile time did not increase, I had some background indexing
running at the same time. On second run it was more or less the same as
allways.
OK - no problem.
Does the output change size when using duplicate()
Hi Marco,
I'm using mkgmap very often and meanwhile it's working really good,
but I found something, that some img files are broken. After integrating
it into Mapsource,
MS is crashing with an error xx.img has an broken record.
How can I help you to find the problem? What do you
Hi Marco,
yes I can do. But before we start huge debugging.
I found out, that these file were bigger then 20 MB.
Could this be a limitation of mkgmap?
I recreated the maps with low max-nodes in splitter, the file became
smaller and it works, now.
Is there a know issue?
There's always
Hi Marco,
Yes I know that it's experimental software. I asked for known issues
concerning a file size over 20MB?
No I do not use assertion. Do you still need the map file, or shall I
rebuild the maps with assertion first?
Yes, please rebuild with assertions enabled and see if you get any
Hi Marko,
Thanks, with the logging.properties from
http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2009q3/003993.html
I got some warnings about roundabouts and fixed a few already.
Good, glad it's useful to you.
I did not find the old discussion on a problematic roundabout, so I cannot
Hi Marko,
In the warning output of finland.osm, I see 219 warnings about
turn restriction relations. Apparently, there not that many errors
in the map data, because I see duplicates, like this:
2009/10/20 15:39:32 WARNING (RestrictionRelation): Turn restriction 167929
has multiple 'to'
Hi Marko,
Could I get the two sets of warnings because I am running with --max-jobs=2?
Would it be possible to suppress the duplicate warnings, or at least
display a download URL for each violation, e.g., for the 'via' node?
I've added the OSM URL into the turn restriction messages.
As for
Version 1305 was commited by markb on 2009-10-22 10:45:48 +0100 (Thu, 22 Oct
2009)
Message tweak - s/road/street/.
Oops, that should have said s/street/road/. So much for shorthand!
Anyway, it's a good new feature - I found over 40 locations in the GB
map where oneway roads met up with
Hi Marko,
I believe that report-dead-ends: 1 is issuing a bogus error with r1308 here:
2009/10/22 22:03:07 WARNING (RouteNode): Confluence of oneway roads
(Laukaantie, 38626392), (637 Laukaantie, 38626390) at
http://www.openstreetmap.org/?lat=62.29304lon=25.81349zoom=17
As far as I
I just processed the latest OSM data for that junction and did not get
a warning, perhaps your data was stale?
Cheers,
Mark
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Marko,
On Sun, 25 Oct 2009 23:29:01 +0200
Marko Mäkelä marko.mak...@iki.fi wrote:
I remember that this was discussed some weeks ago, but I cannot remember if
a final conclusion was reached.
Certain types of these U-turn restrictions can be rewritten as
only_straight_through. For
Hi Marko,
mkgmap does not like this relation:
http://www.openstreetmap.org/browse/relation/55796
except = destination;taxi
restriction = only_straight_on
type = restriction
It does not recognize the 'destination'. I thought that I would ask if mkgmap
could support the analogy of
Hi Marko,
The error message
WARNING (RestrictionRelation): Turn restriction 113509 unknown member role ''
lacks coordinates. It could get a position from a participating node or way,
couldn't it? Failing that, it could at least display the URL
Hi Dermot,
On Tue, 27 Oct 2009 23:36:17 +
Dermot McNally derm...@gmail.com wrote:
I love the roundabout warnings and, with their help, I've been able to
fix all the broken roundabouts in Ireland that they have identified.
In the process, though, I've spotted a particular kind of false
Hi Marko,
Thanks for committing this, Mark!
No problem, it looked like good stuff.
I think that I have fixed all turn restriction errors in finland.osm now,
which means that I should not be bugging you about these error messages
any more. :-)
Next up are the 69 non-oneway roundabout
Hi Clinton,
I have committed the Java part of your patch so that people can easily
try it out with their own styles.
The patch to the default style file can be applied when it is approved
by testers.
Cheers,
Mark
Index: resources/styles/default/lines
Hi Nakor,
Please find attached a patch that will generate a .nsi file if --nsis is
provided on the command line. This .nsi file can be use with NSIS (
http://nsis.sourceforge.net) to build an EXE installer for installing the
maps with MapSource on Windows.
Known limitation: for now I
Hello Hendrik,
I have an issue when I try to go in my Garmin nüvi 755 to the node
http://www.openstreetmap.org/browse/node/493911864 (name=Sogesco Ducos).
The nüvi is showing a route to somewhere else approximately to node
http://www.openstreetmap.org/browse/node/481738937
Hello Hendrik,
Using the map data you supplied and the latest version of mkgmap,
mapsource can route to that destination from almost anyway (sensible).
I haven't tried using a real gps.
Sorry, I don't know what is causing the problem you are seeing.
The command I used was:
java -Xmx800m
Hello Marko,
I did not get two turn instructions on my latest bicycle ride. Luckily,
it was a familiar route and I was paying attention to the map, not keying
in the ref= of a bus stop or something.
The first occurrence was when I was approaching
Hi Chris,
I tested some turn restrictions in Mapsource and found that they
are used in all modes (car/bicycle/foot).
Is there an option to disable them for foot ?
In Germany the traffic signs for T.R. are only valid for vehicles.
When I added the exceptions to the turn restrictions
Hi Chris,
I took another look at the turn restriction exception stuff but could
not find a way of excepting foot traffic. Sorry, it remains a mystery.
Cheers,
Mark
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
Hi Nakor,
Remember that routing issue you reported about a month or so ago and I
could not find detect what was wrong at the time?
Well, today's commit to limit the number of points in a way appears to
have fixed that issue as well.
Cheers,
Mark
Hi Nakor,
I said:
Remember that routing issue you reported about a month or so ago and I
could not find detect what was wrong at the time?
Well, today's commit to limit the number of points in a way appears to
have fixed that issue as well.
Sorry, I was wrong about that. For me, the
Hi Nakor,
Well, today's commit to limit the number of points in a way appears to
have fixed that issue as well.
Good news indeed. I'll try this next time I update my maps and let you know.
I got it wrong. I tested with a smaller OSM file and the problem
doesn't appear with that but
Hi Felix,
I just tried a way with ~240 nodes (using max 300) and it routed
perfectly fine. I think we can actually safely incease this value
max 80 did degrade routing over long distances (though I don't think
there are many ways with more than 200 nodes without intersection or
Hi Andre,
The compile process is just ready and there were no 'zero length arc'
messages for the area I compiled. But the other message I mentioned
above remains and now I can give you the full text of it:
SCHWERWIEGEND (RouteArc): Way Bastia-Savona (id 8068024) contains an arc
whose
Hi Chris,
Looks good, error file is empty.
Good, I shall probably commit that as an interim fix until I find what
the real problem is.
Cheers,
Mark
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
Hi Felix,
Using your patch but setting the values to:
private final int MAX_POINTS_IN_WAY = 300;
private final int MAX_POINTS_IN_ARC = 200;
private final int MAX_NODES_IN_WAY = 64;
Gave me the best results so far, is there any reason why
max_nodes_in_way is set to 16?
Hi Andre,
SCHWERWIEGEND (RouteArc): Way Bastia-Savona (id 8068024) contains an arc
whose length is too big to be encoded so the road will not be routable
I have changed that message to include the length of the long arc.
Please process your map again and post what it says.
Thanks,
Hi Andre,
The reported is bug is gone. Thanks for the quick fix.
Sorry, I broke it!
Cheers,
Mark
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Ok, I think I know what's been going wrong with some people's maps
where the routing goes zig-zaggy when the way is longish. However, it's
not the number of points in the way or even the length of the way that's
wrong.
It's because the bounding box becomes sufficiently large that it causes
the
v2 - added some assertions to catch out of bound line start coordinates
- Increased size of line bbox - reduced size of polygon bbox.
I can process the whole of the UK with this patch without errors -
please test this on as much map data as possible and report any
assertions or SEVERE messages.
Hi Valentijn,
(Right after I compiled a map with your v1 patch, a 2nd version shows
up...) If the map does not complain in any way (i.e. no assertions),
does that mean I don't hit the bbox problem?
Yes, if the map builds OK with no assertions or SEVERE messages (that
were not being produced
Hi Felix,
Please apply the attached patch to mkgmap - keep the v2 bbox patch as
well - try processing those Austria and Alps files again and let me
know what happens.
thanks
diff --git a/src/uk/me/parabola/imgfmt/app/trergn/RGNFileReader.java
Hi Marko,
Geofabrik's finland.osm.bz2 from this morning processed fine. The
mkgmap.log.0 (with the patch) and mkgmap.log.1 (without) are of the same
size, and after grepping away the noise, the same three (already fixed)
errors remain.
Good.
I did not test the map in a device yet.
Hi Felix,
I have the problem that with the patch applied the mdr creation breaks
(on Austria and Alps from Geofabrik)!
Without the patch, this error does not occur!
These Austria and Alps files, what created them? Was it you using
mkgmap with this latest patch? Or did they come from
Felix,
Yeah that fixed it (I'm still calculating on Alps, but pretty sure it'll
pass too - otherwise I will follow it up).
Very good, so that's a sign extension issue in the code that reads
img files. It just so happens that the assertions I added as part of my
current effort detected the
Felix,
ups sorry, me in one go (as susual from geofabrik - download date 1.11).
I did not try out other countries yet, suppose they will fail too. With
problems on index creation appearing quite often I really think about
using a stable mkgmap version for the index creation, and another
Hi Marko,
I just did, testing the bicycle route to Kuortti that I mentioned in
http://wiki.openstreetmap.org/wiki/Mkgmap/routing/issues#Bad_bicycle_routing
a couple of months ago. It still makes the detour. It is most likely an
issue with Garmin's routing algorithm, not with the map.
Yes,
Hi Andre,
java.lang.AssertionError
at
uk.me.parabola.mkgmap.osmstyle.StyledConverter.addRoadWithoutLoops(StyledConverter.java:1078)
at
uk.me.parabola.mkgmap.osmstyle.StyledConverter.addRoadAfterSplittingLoops(StyledConverter.java:951)
Those line numbers do not correspond
Hi Felix,
Can you supply the mkgmap options please?
Cheers,
Mark
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Felix,
I believe I understand what the problem is here. My recent changes have
uncovered a problem that has been around for a long time. I shall work
on a solution this evening.
Cheers,
Mark
___
mkgmap-dev mailing list
Hi Felix,
could you explain a bit more how they work?
Simply, the contents of those ref like names are all concatenated
together with ; between them and then the first 4 names in that list
are used as the labels for the way. If the way also has a name then
that will be the first label and you
201 - 300 of 644 matches
Mail list logo
