Hi Garvan,
Can now explicitly tag boundary nodes with mkgmap:on-boundary=1.
Apologies for the beginners question, but how do I use this? In the OSM
source like this?
node id= -1 lat=11.00 lon=103.72
tag k = mkgmap:on-boundary=1 /
/node
I am assuming this is to allow us to mark
On Wed, 24 Mar 2010 14:33:15 +
Toby Speight t.m.speight...@cantab.net wrote:
When --generate-coastline=multipolygon fails, I'm left with a map that
has no distinction between land and sea. However, if I don't
use --generate-coastline, I at least get a line (from my style/lines).
Is there
The patch to support different min sizes for lines and polys has now be
committed. I added a couple of options so that the default values (1
and 8 as per the original patch) can be changed if required.
Mark
___
mkgmap-dev mailing list
This patch squashes spaces in label strings so that High Street
becomes High Street.
Is there any reason why we would want to preserve multiple spaces?
Mark
diff --git a/src/uk/me/parabola/imgfmt/app/Label.java b/src/uk/me/parabola/imgfmt/app/Label.java
index 149205b..ec2b11a 100644
---
Hello Felix,
Could it be that the new for polygons 8 is much much bigger compared
to the old (using patch) 8???
Or that the patch was not enacted on resolution 24??
Err, why?
Mark
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
Felix,
Or that the patch was not enacted on resolution 24??
Yes, that's true and looking at the code, I think that for polygons it
probably should always be done and, furthermore, should be done after
the polygon splitting so that any tiny polygons produced by the
splitting get removed. i.e.
Hello Chris,
I found that I had to set the ferry road class to 3 to be able to
reliably route using them.
Mark
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Use road_class 3 for route=ferry.
Mark Burton says that this is needed for reliable routing.
That was rather quick. Let's hope I'm right.
As for evidence, here's an example route that has uses two ferries and
has no intermediate way points.
Mark
attachment: ferry
Hello Christoph,
Hello list,
I try to make Garmin maps with different layers.
http://wiki.openstreetmap.org/wiki/All_in_one_Garmin_Map
The idea is, that you can enable or disable some transparent maps that you
won't see.
For this reason I use mkgmap with different options and
Hi Felix,
On 22.03.2010 00:42, Mark Burton wrote:
v6 - don't trash first ref if it is the same as the name (sans shield)
and more refs follow
-
In principle the patch works very good.
Good.
I do get complications when using this patch in combination to Wan Mill's
Hi Steve,
Steve's been handling the MP patches, hopefully he will look at
incorporating that patch.
All of that patch (as far as I can see) was included in the r1607 patch.
Oh yes, it's already been done.
I've been so immersed in my own little world that I missed that one.
Mark
Felix,
okay searching for roads works very well now.
Good.
However the ENQ problem is
not solved for me. Using: /set ref = '${ref}'/ inside relations file for
relations that have a ref (like EV6) and then
/{ set name='${ref|highway-symbol:box:6:4} ${name}' |
Felix,
Sorry, once again, I am nonplussed by the style syntax, what does the
6:4 mean in the above?
This means 6 characters maximum, or 4 non numeric characters maximum if
I remember it correctly. Default is 7:5 if I remember correctly.
OK - thanks.
Well, the 0x2f and 0x2e
BTW - do you think this v4 patch is working well enough to commit now?
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Clinton,
BTW - do you think this v4 patch is working well enough to commit now?
yes
Me too! :-)
Good and thanks for the earlier +ve report.
Unless anything untoward crops up, I shall commit it later today.
Mark
___
mkgmap-dev mailing
Folks,
You can see the additional label will only be added if it differs from the
name after the Garmin codes have been stripped from the name.
Sure, what's the point in having multiple labels the same (apart from
the shield code)?
Mark
___
Hi Paul,
Hmm, I would have thought permissive would have been the same as
destination but with preference given to permissive routes as a
tiebreaker.
The Garmin doesn't do permissive - it really only does yes or no so
the choice is one of:
permissive = yes
permissive = no
permissive is
Felix,
I'm not setting multiple labels. The display_name is the name shown for
routing instructions. If not set, the ref alone will be taken instead.
So instead of say left on A11 Westautobahn the GPS will only say left
on A11.
Hmm, for me, I still get the longer routing instruction.
v5 - now understands the 0x1b prefix code that introduces a lower case
letter (and also is used to prefix a couple of separators (0x1b and
0x1c).
I thought great, now I can prefix my road names with ^\ (aka 0x1c) and
they won't show up so readily when zoomed out. That worked as expected
but,
Felix,
The patch for the patch by Clinton, allows that display_name can be
identical to name and I find it pretty useful.
I am very slow - please spell it out for me.
How does having two labels that are the same apart from the first one
having a highway shield prefix behave any differently
Felix,
Your version 4, disallowed setting display_name and name to the same value.
Actually, display_name isn't really handled specially at all, it's just
the same as any other ref but it goes to the head of the ref queue. i.e
if you have:
name = peach
ref = banana;orange
display_name = kiwi
Hi Clinton,
Sure, what's the point in having multiple labels the same (apart from
the shield code)?
I suppose because Felix said so isn't a good argument is it? ;-)
I think that I have twigged what the issue is - I think what Felix is
possibly looking at this situation:
name =
Felix,
Your right, it would really be needed that all of the three combinations
of name and ref are searchable independently.
name
ref name
ref
All it requires is that all of the labels that are attached to a road
are read in by the MDR generating code. Where those labels got their
values
Felix,
Thanks for the explanation - I was hoping you would write English
rather than style language as I understand that about as well as I
understand German language!
Anyway, I think I have worked out what the issue is. It's because there
are trailing labels following and they get shown
v6 - don't trash first ref if it is the same as the name (sans shield)
and more refs follow
-
v5 - now understands the 0x1b prefix code that introduces a lower case
letter (and also is used to prefix a couple of separators (0x1b and
0x1c).
I thought great, now I can prefix my road
Hi Paul,
I'm curious how mkgmap handles permissive, private, and destination
access types myself.
'permissive' is considered to be the same as 'yes' and 'designated'.
'private' is considered to be the same as 'no'.
'destination' routing on a way(s) should stop the gps routing through
those
This patch codes around the problems introduced by highway shields with
regard to the sorted roads:
1 - the sort order should now be much improved
2 - no duplicate symbols (shield version + non-shield version)
It also includes a fix to the label reading code so that labels with a
highway
v2 - remove more duplicate labels that only differ in letter case -
remove leading spaces from labels even if they start with a Garmin code.
Still something wrong with motorway names because on the UK map, only
the M74 appears in the mapsource road names - all other motorways are
missing - very
Hi Clinton, Felix,
Hi, I just got this comment yesterday via my homepage. Seemingly mkgmap in
some circumstances puts ENQ - functional characters into the name of
streets (when adding the name from a route relation).
ENQ is ASCII 0x05, which is one of the codes for highway shields.
v3 - now works harder to clean up road names for use in MDR file - not
sure if this will have a beneficial effect but it could possibly fix
the issue recently reported by Felix.
Motorways are still not showing up.
---
v2 - remove more duplicate labels that only differ in letter case -
Hi Clinton,
On Mar 18, 2010, at 22:49, Mark Burton wrote:
v3 - now works harder to clean up road names for use in MDR file
Er... this patch needs to be applied on top of the v2 patch does it not?
It just patches the MDR file, but does not contain the patches to all the
other files
v4 - found the motorways (and a load of other roads too!)
v3 - now works harder to clean up road names for use in MDR file - not
sure if this will have a beneficial effect but it could possibly fix
the issue recently reported by Felix.
Motorways are still not showing up.
---
v2
Hi Clinton,
On Sun, Mar 14, 2010 at 11:29 PM, Mark Burton ma...@ordern.com wrote:
Hey, that's a really great bug, it causes anonymous peaks to be
named in honour of a bus stop!
This may be caused by the def (default value) and height filters.
I believe the statement is attempting
Steve,
It turns out that the problem is Labels that are empty but not null. All
such labels, however generated, show as whatever label was defined right
after the first empty one.
The attached patch should fix it.
That looks better, thanks.
Mark
Hi Nakor,
I don't know what is causing the SEGV but have you tried using another
runtime? Perhaps, it's a problem in OpenJDK.
# Java VM: OpenJDK 64-Bit Server VM (14.0-b16 mixed mode linux-amd64 )
Mark
___
mkgmap-dev mailing list
Stylists,
Just noticed that in the UK map, points tagged natural=peak that don't
have a name are showing a name of '6140565'. I guess it's something to
do with this rule from the points file:
natural=peak {name '${name|def:}${ele|height:m=ft|def:}' } [0x6616 resolution
18]
The style language
Felix,
Ups, sorry. I don't understand why it ran through using the default
style, but it is hanging on the templates.args file which seems to be
the real culprit.
If I run mkgmap with *.osm.gz for map input, it runs through fine. If
however I use -c template.args then it gets stuck
Hi Someoneelse,
Is 6140565 the last name in the .osm file being processed at that
time? I've seen a similar effect with all unnamed natural=peak being
named YHA Ravenstor (which happened to be the last name in the file
that I was processing at the time). As to how to fix it; haven't a
Chill Felix,
Sorry, I had a syntax error here that caused mkgmap to pass when not
using template.args (and outputting a 0kb map). It's using
location-autofill=2 and my style-file which will cause mkgmap to get
stuck on kosovo (as well as on some more countries like recently Slovakia).
I
Felix,
The problem is triggered by the fact that in your style file you give
anonymous roads of the same type, the same name i.e. 'rd', 'trk',
'ucl', etc. So the map ends up containing lot's of roads with the same
names. The kosovo map contains a huge number of anonymous roads.
The code that is
Hello Tony,
I got my first GPS recently, a Garmin GPSmap 60CSx, and am now trying
to create maps for it via mkgmap, but am having problems. I'm running
Debian Lenny, with mkgmap-r1600 (current version) and Sun Java 6. My
machine is 32-bit AMD with 2GB memory.
I managed OK (using an older
I recently discovered jvisualvm and have been using it to profile
mkgmap. One thing I haven't discovered yet is how to profile an
application from the start - its trivial to attach to an already
running java app using the gui but if it's already running, you could
miss some useful info. So, the
Hi Carlos,
Building a map of Europe I get the following message:
Overflow of the NET1. The tile must be split so that there are fewer
road in it
Would it be possible to include tile name in the message?
Please try attached patch. If good, I will commit it.
Mark
diff --git
Hi Daniela,
Hi!
One street shoes a gap that does not seem to be in the osm data:
http://www.deltadelta.de/nmz/sc21.png
vs.
http://www.openstreetmap.org/?lat=48.08617lon=11.50167zoom=17layers=B000FTF
I tried to navigate to the Bad Forstenrieder Park. Since one can not
pass this gap,
Carlos,
Using sun java as in machine A fixed the problem for splitter, although
mkgmap still needs a slightly higher amount of memory. May it be due to
--max-jobs?
Sure, if you have more cores available than before, --max-jobs will
process that number of maps in parallel so it will take more
Hi,
I have noticed for the last 2 weeks the mkgmap was hanging but nothing
in a the change log jumped out as someting that may have caused it.
After some debugging I have tracked it down to ways like:
http://www.openstreetmap.org/browse/way/29416921
The debug log shows it stops when it hits
As this patch fixes the problem that Garvan reported and no one has
reported that it has broken anything I will commit it in a day or so
unless any -ve reports come in.
Mark
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
Hi WanMil,
I give a very big GO for commit to this patch :-)
I am not familiar with the MP code so it would be better if someone who
is familiar with it commits it rather than me as I prefer to only
commit stuff that I understand!
Hope you don't have to wait to long.
Cheers,
Mark
Those people using MapTk will be interested to know that a new version
has just been released (2.7.2) - among other things, it fixes the
problems with multiple lines/POIs that have extended types.
Also, does anyone know if any of the extended type POI codes do not
show a little dot in the middle
Felix,
Mapsource 6.13.x never
routes above more than 1 border however
Sadly, that's true for our maps.
But it will happily route over multiple tiles that have been created
with cgpsmapper. I can take the tiles from the NZ opengps map set and
generate an overview map with mkgmap and give
Hi Garvan,
Thanks for persevering with this issue.
Your latest example has brought me enlightenment!
I will work on a solution this evening.
Mark
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
Hi Nick,
Unfortunately, those tiles are not routable as mkgmap --routes only seems to
work with a default style.
Routing should work with any style as long as the roads are given
sensible garmin types/resolutions. There certainly shouldn't be any
interaction between routing and sea
The short arc removal code was removing (non-short) arcs when their ends
were close enough to be considered the same point.
Now it just leaves them be.
Please test this patch if possible because I have reworked the short
arc removal code (and some badness could have crept in).
You will
Hi Felix,
You will be interested to learn that the problem I mentioned recently
regarding my polylines not taking the style from the MapTk generated
style file is due to a bug in MapTk - I contacted the author about it
and he got back to me today saying it's a bug, I'm working on it.
Cheers,
Hi Nick,
I'm not so sure I understand - is there something wrong with my typ file if
it generates seas without flooding at any zoom level?
I appreciate having to readup on creating routable styles.
If you are using --generate-sea=polygons (or no-mp, means the same) you
need to define a land
Felix,
I
still have too many turn right / turn left even though the direction is
straight on (like 10° direction change on same road).
Please provide an example of that (snapshot of route in mapsource + OSM
URL so I can grab the data).
Thanks
Felix,
Well at some other points it did not want to route over 2 tile borders,
seems not to be perfect yet - but the greatest step into the right
direction so far when it comes to inter tile routing.
Hmm, I'm sure that WanMil's patch does something good but I can't see
how it can affect
I just noticed on my etrex that tiles that touch the coastline are
flooded when zoomed in less than about 30Km. Neither mapsource or the
nuvi show the same problem with the same map (this is with
--generate-sea=polygons). When zoomed out, the coastline looks fine.
Anyone else seen this? got a
OK - I think I found what was wrong. I recently removed the 0x4b poly
from the TYP file and that was the only poly on level 1. What I didn't
realise is that all the polys on higher levels then got shifted down
one level so that the sea poly was now on level 1 (I guess the etrex
does something
Hi Felix,
Many thanks for taking the time to respond - I believe the problem was
caused by me removing the 0x4b poly from the TYP file (see last post).
Mark
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
Felix,
Doesn't sound right to me. There is no need for 0x4b at all (my maps do
not contain 0x4b). The only thing that I could imagine that happenend
based on your above description is that both sea and land were at the
same level, or that the polygon for land was not correctly set. Try
Felix,
Well according to maptk, sea is the only poly on DP level 0 (maptk
counts from 0), while land is on 1, and all other polygons are on 2 or
higher. Maptk makes no automatic adjustions to the levels, so if were to
remove sea at 0, then all other polys would stay at their DP level.
Felix,
Just another thought. Are you using single color or pattern for land?
Try using a pattern for land (set both colors the same, or for maptk set
just one pixel to a different color).
Using single color instead of pattern, does definitely sometimes lead to
problems. Garmin modern
Hi Felix,
Patch works for UK.
Good, me too - I have committed it.
However I think we should rather have this done generally for ;.
Quite possibly, but that requires more thought/effort and what we need
right now is a quick fix to make the coastline work again so we will
have to make do
Hello Minko,
The option --road-name-pois often creates place names that are totally wrong.
Two adjacent streets in the same district can have different place names.
I think it is better not to show the place name until this problem is solved?
Is there a way to make these POI invisible on
Carlos,
It seems you know my city better than me ;-)
I wish I did, I'm sure the weather would be a lot nicer there than it is
here!
The closest I have been to your city is looking at it with josm.
Cheers,
Mark
___
mkgmap-dev mailing list
Felix,
The new flooding is solved. The big flooding in the tile of Bremen
in Germany still exists however (I do know that the geofabrik cut is
100% responsible for it). There is one problem however, the land polygon
is ommitted. So background color is missing, t'would be great if not the
Hello Garvan,
I found a generalize function in gpsmapedit that removed 10% of the
points in the file, but the national boundaries still did not display,
so I split the very long polyline up and then it compiled correctly.
I don't see why that was required because we already split lines
I don't use 0x4b in Typfile anymore. Having two polygons for one
function (get rid of yellow on etrex) is slowing down GPS/Mapsource .13.x
Fair enough - please try attached new patch that generates the land
poly.
The big flooding in the tile of Bremen
in Germany still exists however (I do
Hi Steve,
Someone has tagged part of the UK coastline with natural=coastline;cliff and
this has broken
--generate-sea=polygons,no-sea-sectors,close-gaps=1000. Is this valid syntax
that mkgmap should cope with?
Don't know whether it's valid or not but I will put in a workaround.
Cheers,
Hi Steve,
Someone has tagged part of the UK coastline with natural=coastline;cliff and
this has broken
--generate-sea=polygons,no-sea-sectors,close-gaps=1000. Is this valid syntax
that mkgmap should cope with?
The attached patch is a quick workaround.
If possible, please test.
Cheers,
Style gurus,
I want to have a rule that matches one way trunk roads. Given that
onewayness can be specified with (at least) 3 different tag values
(1,yes,true) do I have to have something like the following, or can it
be simplified:
highway=trunk (oneway=yes|oneway=true|oneway=1) [...]
i.e.
v2 - further fixes
Carlos, this still gives you an extra turn left onto Calle Osa
Mayor and I know what's happening there but can't fix it - how
about the other problems you were seeing? better/worse?
Hopefully, these changes will fix the bad routing directions we have
been seeing
It could be that tile contains a lake tagged natural=coastline but it's
the wrong direction, i.e. it's an anti-lake!
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hopefully fixes the recent regression which caused incorrect turn
directions to be issued (most likely to occur when entering roundabouts
that have flares).
Actually, the bug was there before but it was being masked by some other
code that recently got removed so the bug then popped to the
Hi Carlos,
I'm sorry, I tested the wrong map (too much things at the same time). I
have seen some improvements, but not all weird instructions have
disappeared. I'll report more details after testing some more.
OK - I will work on it again this evening.
Mark
Felix,
I looked for an anti-lake, but could not find one...
I think ultimately we would need some check against flooding. Easiest
maybe would be if there are more than 30 forest polygons inside water
(without natural=land) and if so, then assume tile is flooded and put
land into the
Felix,
It would be great to have the possibility to put a one point road (there
has to be some code to make sure it's not munged by the dp-filter) with
a highway shield.
I don't think you can have a one point road but I don't see why you
can't have a very short two point road (say, 2.5m
Hi Carlos,
At least since version of 12/02/2010 I'm getting some weird turn
instructions in places where they worked fine in the past . In this area
[1] I get two of these estrange instructions when driving SE from
Avenida Cordel de Merinas to SW in Avenida Hernán Cortés. The
sequence of
Hi Nakor,
Would it be because of that regression that whendriving that route (
http://maps.cloudmade.com/?lat=42.560106lng=-83.18043zoom=17directions=42.561639094255526,-83.1770396232605,42.558565013969705,-83.18168520927429travel=carstyleId=1opened_tab=1)
the only instruction you get is Turn
Felix,
I looked for an anti-lake, but could not find one...
So that tile contains no ways with natural=coastline?
Mark
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Well it probably does, but it must be tiny. Will recheck with gpsmapedit
later - in Mapsource I could not find it.
grep is your friend.
However, I'm just working on a patch to try and avoid the flooding -
stay tuned.
___
mkgmap-dev mailing list
Hi Felix,
Please try the attached patch, hopefully it will stop the flooding.
Mark
diff --git a/src/uk/me/parabola/mkgmap/reader/osm/xml/Osm5XmlHandler.java b/src/uk/me/parabola/mkgmap/reader/osm/xml/Osm5XmlHandler.java
index f78b1f9..f7aba49 100644
---
Marko,
If nobody opposes, I will commit the patch.
Fine, but why not hang on for a while and give people a chance to try
it out and report back before it gets committed.
Mark
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
Hello Marko,
Sure, it is a non-trivial change to the algorithm. What about one week?
If I forget, WanMil please remind me. :-)
My rule of thumb for committing non-trivial changes goes along the
lines of:
if you receive negative reports, either fix the patch or convince the
reporter
Hi Carlos,
At least since version of 12/02/2010 I'm getting some weird turn
instructions in places where they worked fine in the past . In this area
[1] I get two of these estrange instructions when driving SE from
Avenida Cordel de Merinas to SW in Avenida Hernán Cortés. The
sequence of
Hello Marko,
I tried to fix this by adding oneway=yes to the flare roads, but it did
not fix the issue. Other warnings that I fixed yesterday are gone, so
my dump should be fine.
2010/02/23 09:51:40 WARNING (RouteNode): 63240004.osm.gz: Outgoing
roundabout flare road
The good news is that this should now no longer falsely complain about
a flare road being the wrong direction when that flare road pair are
the only roads connected to a given roundabout.
The bad news is that it will now find more bad flare roads than it did
before - and you thought you had
Hello Garvan,
http://dl.dropbox.com/u/4900023/cambodia.osm
If you zip up that file to save my bandwidth, I will take a look at it.
Mark
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Well, I looked at it but learnt nothing. I just get an empty map, no
lines, no diagnostics, nothing at all.
Mark
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
If you zoom in I think the contours and provincial boundaries will show
up, but at full zoom nothing shows because the national boundaries are
missing. I am not sure exactly when they should show in mapsource, but
gpsmapedit tells me they are not in the img file at all.
OK, I think what's
Marko,
Thanks for the report.
In other words, please commit the patch.
Good, I will do that.
Mark
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hello Marko,
+ new AccessMapping(motor_vehicle, RoadNetwork.NO_CAR),
That's not enough because if motor_vehicle=no, you also want stop
psv/taxi/emergency/hgv.
It's more like:
String mv = way.getTag(motor_vehicle);
if(accessExplicitlyDenied(mv)) {
way.addTag(motorcar, no);
//
Hello Torsten,
highway=* mkgmap_routing=foot {set motor_vehicle=no} [0x09 road_class=1
road=speed=1 resolution 22]
motor_vehicle is not understood by mkgmap - how about:
{set access=no; set foot=yes}
Cheers,
Mark
___
mkgmap-dev mailing list
Hi Clinton,
On Feb 12, 2010, at 12:46, Mark Burton wrote:
Is through route documented in the OSM Wiki? I was unable to find
any information on this.
Not yet, but it should be. I was rather hoping that some kind person
would add a page to the Wiki describing it.
So about adding
Hi Marko,
motor_vehicle is not understood by mkgmap
Actually, why not? If my memory serves right, mkgmap understands
motorcar and motorcycle (and maps them to the same access bit), but why
not motor_vehicle? For example in my understanding, tractors are
covered by motor_vehicle but
Hi Steve,
Unless you know better, I'd say it was time or nearly time to merge that
branch back to trunk.
Agreed.
The only slightly odd behaviour for me is at:
http://www.openstreetmap.org/?mlat=51.612512mlon=-3.961642zoom=18layers=B000FTF
..where, if I approach on the southern stub
Hi,
Unless you have another patch that modifies the toOSMUR() function to
print a /browse/way/* link in addition to the bbox link it currently
prints that doesn't give me the info I need. The idea was to not have
to copy/paste the ID that was printed into a manually constructed URL
that I'd
Hello Ævar,
Please try this version, it should now print the browse URL whether the
road is from OSM input or MP input.
Mark
diff --git a/src/uk/me/parabola/imgfmt/app/net/RoadDef.java b/src/uk/me/parabola/imgfmt/app/net/RoadDef.java
index de87495..1dc1e8a 100644
---
Hi Steve,
If that comes up today, I can test it tonight. Thanks in advance.
A v4 patch was posted yesterday, here it is again.
Cheers,
Mark
diff --git a/src/uk/me/parabola/imgfmt/app/net/RoadDef.java b/src/uk/me/parabola/imgfmt/app/net/RoadDef.java
index de87495..e6a187e 100644
---
1 - 100 of 644 matches
Mail list logo