Hi,
Just want to share a report from one of the gps map users.
In this example, the gate blocks any motor vehicle from going to
grasshopper street and spider intersection, and to crispina. This gate
is only passable by pedestrian.
If the destination is somewhere crispina, the correct route
Hi,
Is this supported in mkgmap?
http://wiki.openstreetmap.org/wiki/Relation:restriction
What should be added in the relations style file?
--
cheers,
maning
--
Freedom is still the most radical idea of all -N.Branden
wiki:
On Thu, Mar 18, 2010 at 02:06:12PM +0800, maning sambale wrote:
I'm inclined to think that this is a data problem (the gate should
explicitly define that is only usefule for pedestrians). I can't find
the correct tagging for this one at the moment. If such tag exist, is
it supported by
Hi Maning,
Is this supported in mkgmap?
http://wiki.openstreetmap.org/wiki/Relation:restriction
What should be added in the relations style file?
Just like multipolygons, it is handled by mkgmap directly, outside the styles.
It is supposed to just work, out of the box. But note that the
Thanks! I added this turn restriction for testing:
http://www.openstreetmap.org/browse/relation/453702
Will report back when map is compiled.
On Thu, Mar 18, 2010 at 3:10 PM, Marko Mäkelä marko.mak...@iki.fi wrote:
Hi Maning,
Is this supported in mkgmap?
To see the RestrictionRelation warnings of mkgmap, you will have to enable
some logging:
java -Dlog.config=logging.properties -ea -jar mkgmap.jar ...
Simple question, when the switch -ea is already in the mkgmap syntax
as above, you don't have to add the ea in the arguments.list file?
--
I got this error recently:
time java -Xmx1512m -jar mkgmap.jar --read-config=args.list philippines.osm
java.lang.NullPointerException
at
uk.me.parabola.mkgmap.osmstyle.RuleFileReader.isIndexable(RuleFileReader.java:234)
at
Hi WanMil,
The messages are generated because the generate-sea algorithm
generated two polygons with role=inner and one of these polygons
lies inside the other. I don't know if that's a bug of the
generate-sea code or if the OSM data has a problem.
I could imagine that there could be two
maning sambale (emmanuel.samb...@gmail.com) wrote:
To see the RestrictionRelation warnings of mkgmap, you will have to enable
some logging:
java -Dlog.config=logging.properties -ea -jar mkgmap.jar ...
Simple question, when the switch -ea is already in the mkgmap syntax
as above, you don't
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
2010/03/18 09:08:55 WARNING (MultiPolygonRelation): 63240004.osm.gz:
Multipolygon http://www.openstreetmap.org/browse/relation/301046 contains
errors.
2010/03/18 09:08:55 WARNING (MultiPolygonRelation): 63240004.osm.gz: Polygon
4611686018427484412(7P : (43036113[6P]) carries role inner
Hi WanMil,
So we have to wait til tomorrow and then you can check if the
generate-sea code will generate a full valid sea area without any
flodding for finland? Wow, I hope that's working!
I just checked the islands in Tornio/Haparanda, with today's dump, and
I did not notice any
Anyone else with knowledge of the file format is encouraged to join in!
Steve
Hi Steve,
I have just started to have a look on the internals of the garmin
fileformat. The wiki
(http://wiki.openstreetmap.org/wiki/OSM_Map_On_Garmin/Format) tells me
that there are the formats
TRE
NOD
MDR
SRT
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
On Mar 18, 2010, at 20:51, Felix Hartmann wrote:
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
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 -
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 from the v2 patch.
Did
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,
Thanks to charlie I activated logging in my map compilation and it
sure helps in fixing routing issues! I already found and fixed a few
oneways coming from nowhere
Several reports I don't understand:
2010/03/18 20:31:26 WARNING (StyledConverter): philippines.osm:
Motorway exit null
21 matches
Mail list logo
