Attached patch should fix (all?) subdivision splitting problems.
Error like Area too small to split at ... cannot occur any more
because the way how subdivisions are split is changed.
I think it's still not the optimal way but there should be no loss in
highly densed areas any more.
This is
I get the error below splitting SRTM of Spain. My commands:
mono Srtm2Osm.exe -bounds1 35.99 -9.501 43.79 4.6 -step 10 -cat 100 20
-large -corrxy 0.0005 0.0005 -o srtm_peninsula.osm
java -Xmx2000m -jar ../../osmosis/osmosis-0.24.1-java5/osmosis.jar --rx
enableDateParsing=no srtm_peninsula.osm
On Wed, Sep 14, WanMil wrote:
Attached patch should fix (all?) subdivision splitting problems.
Error like Area too small to split at ... cannot occur any more
because the way how subdivisions are split is changed.
I tried to apply it on top of mkgmap-r2028, but it does not compile,
On Wed, Sep 14, 2011 at 09:57:16AM +0200, Thorsten Kukuk wrote:
I tried to apply it on top of mkgmap-r2028, but it does not compile,
toGarmingString is an unknown symbol. I disabled the two lines for now
and I will testing it with my maps.
There is no toGarminString either.
Unfortunately, this
El 14/09/11 09:56, Thorsten Kukuk escribió:
On Wed, Sep 14, Carlos Dávila wrote:
I get the error below splitting SRTM of Spain. My commands:
Known problem, only use google or search in the mailing list archive.
My currentl solution is to use splitter-r123, that one still works and
I don't
On Wed, Sep 14, WanMil wrote:
Attached patch should fix (all?) subdivision splitting problems.
Error like Area too small to split at ... cannot occur any more
because the way how subdivisions are split is changed.
I tried to apply it on top of mkgmap-r2028, but it does not compile,
Ralf,
I don't think it will work in Mapsource/Basecamp with two different routing
layers in one map.
For instance you have a car based routing map in Layer 1:
family-name=Layer1
input-file: 1001.osm.gz
input-file: 1002.osm.gz
And a bicycle/foot routing map in Layer 2:
family-name=Layer2
On Wed, Sep 14, 2011 at 09:57:16AM +0200, Thorsten Kukuk wrote:
I tried to apply it on top of mkgmap-r2028, but it does not compile,
toGarmingString is an unknown symbol. I disabled the two lines for now
and I will testing it with my maps.
There is no toGarminString either.
Unfortunately,
Hi,
when using Garmin modes like Taxi for special routing (like
race-bicycle routing) is there a trick to make make-opposite-cycleways
working?
So that the artifical created way doesn't gets the bicycle but the taxi
flags?
Chris
___
mkgmap-dev mailing
I was using the patch you had posted on 21st June so far and have tested
the new patch now. Both work equally well for me - no area to small
errors.
- Bartosz
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
Hi
look in the data you can find the splitted pbf and the resulting img
here: http://www.aighes.de/data/tile_with_problem.7z
Thanks. However I get a different error:
Exception in thread main java.lang.AssertionError: Invalid label
offset found 4611728
at
On Wed, Sep 14, Thorsten Kukuk wrote:
I tried to apply it on top of mkgmap-r2028, but it does not compile,
toGarmingString is an unknown symbol. I disabled the two lines
for now and I will testing it with my maps.
I did rebuild all of my OSM and SRTM maps, no Area too small messages
anymore
12 matches
Mail list logo
