On Thu, Oct 27, 2011 at 4:56 AM, GerdP gpetermann_muenc...@hotmail.com wrote:
Hello list,
since a few days I try to understand the idea of the class
SparseInt2ShortMapInline in splitter because this seems to waste memory
although it is documented to save it. If I got this right, the amount of
On Thu, May 5, 2011 at 8:54 AM, Francisco Moraes
francisco.mor...@gmail.com wrote:
Hi,
I have tried to use the --wb option with Osmosis but it always fails for
me. It seems to treat the file as input instead of output. The only way
I can make it work is to use --write-pbf instead. Here's the
On Wed, Mar 2, 2011 at 5:36 PM, Michael Prinzing mi...@gmx.net wrote:
Hi,
I am getting the splitter from svn, compiling and running it unter
Windows XP SP3 using JDK 1.6.0_25. There are 2 problems if I am using a
splitter version newer than r161 (tryed until r167 so far).
1.)
This boundary is open by the coast side, as many others (¿all?) in
Spain. Something similar to the close-gaps in the sea generation could
do the trick.
That's not a nice job to do... We might continue the boundaries along
coastlines. This would be a job for a specialized BoundaryRelation
On Sun, Feb 20, 2011 at 8:22 AM, Steve Ratcliffe st...@parabola.me.uk wrote:
Hi
OK, I think I have this one solved, or at least worked around. The
original code used a character array to buffer up output before
I've looked at this and I think that the cause is the same as the other
problem
On Wed, Feb 9, 2011 at 5:15 AM, Henning Scholland o...@aighes.de wrote:
Am 07.02.2011 23:45, schrieb Minko:
Henning,
Did you try a higher overlap setting?
Maybe --overlap=6000 ?
--overlap
Nodes/ways/rels that fall outside an area will still be included if they are
within this many map
On Fri, Jan 28, 2011 at 11:00 AM, WanMil wmgc...@web.de wrote:
Hi
Anyhow here are my wishes to the ongoing splitter development (don't
know if this is a good place?):
I'm not likely to have time for splitter development for a while. I'm
putting my OSM work into implementing a new planet
On Thu, Jan 27, 2011 at 7:31 AM, Chris66 chris66...@gmx.de wrote:
Am 27.01.2011 03:55, schrieb Scott Crosby:
The problem is entirely with the pbf reader --- a 32-bit cleanness bug
that was only exposed on Windows made the reader erroneously sense
end-of-file.
Hi Scott,
is this a known java
On Wed, Jan 26, 2011 at 7:54 AM, Henning Scholland o...@aighes.de wrote:
Am 26.01.2011 13:54, schrieb WanMil:
Hi Steve, hi Scott,
I tried the new splitter build but it's not working for me.
I splitted the 4.6GB europe.osm.pbf using the default splitter
arguments. The output was 64 osm.gz
On Fri, Dec 24, 2010 at 3:40 PM, Henning Scholland
h.scholl...@googlemail.com wrote:
Yes, the file generated under windows was working well. 4GB problem can't
be, because of using 64bit java and also in the past I processed files
larger then 4 GB and the windows-generated pbf-file is also
Just a quick note.
This is the code for splitting the planet into thousands of areas in a
single pass based on the mkgmap splitter. I mentioned this code on
both osm-dev and mkgmap-dev.
This branch supports PBF, runs much faster, threads better, doesn't
have the 'node in too many areas' issue,
On Wed, Nov 3, 2010 at 6:32 PM, Marko Mäkelä marko.mak...@iki.fi wrote:
Hi Steve,
On Sun, Oct 31, 2010 at 10:39:27PM +, Steve Ratcliffe wrote:
I've built a complete splitter distribution from the pbf branch and put
it at http://files.mkgmap.org.uk/download/6/splitter-r161.zip
Thanks,
On Mon, Nov 15, 2010 at 2:03 PM, Danny Backx danny.ba...@scarlet.be wrote:
After a *lot* of messages like these :
Node 986712679 in too many areas. Already in areas 0xd0a0706, trying to
add area 0xe
Node 986712679 in too many areas. Already in areas 0xd0a0706, trying to
add area 0x11
Node
Try increasing the resolution. The resolution controls the minimum tile
size. Note that increasing the resolution by 1 quadruples the memory use of
one of the internal arrays used to determine split points. I suggest using
13 or 14. Alternatively, you can split the geographic extent of the
On Mon, Oct 18, 2010 at 3:38 PM, Adrian ar2988...@yahoo.co.uk wrote:
Marko wrote:
If I remember previous discussions correctly, splitter does not split
lines exactly at the tile border, but instead it includes all nodes
that are not too much outside the tile.
That is also what I
On Thu, Oct 21, 2010 at 5:30 PM, Adrian ar2988...@yahoo.co.uk wrote:
I have investigated further and this is what I have found.
- The output files from splitter contain the missing ways and they are
complete; i.e. the way has all its tags and a complete list of its node
ids. What is not
On Wed, Oct 20, 2010 at 3:17 AM, Marko Mäkelä marko.mak...@iki.fi wrote:
On Tue, Oct 19, 2010 at 04:22:18PM -0500, Scott Crosby wrote:
There's a branch in the splitter repository that supports reading pbf
files, along with significant improvements in scalability and
performance, but it still
On Tue, Oct 19, 2010 at 3:06 PM, Steve Ratcliffe st...@parabola.me.ukwrote:
On 19/10/10 15:58, Carlos Dávila wrote:
Yesterday I tested pbf input for mkgmap for the first time. Map was
built apparently without errors, but using the resulting map on
MapSource I get a suboptimal route,
On Wed, Sep 22, 2010 at 12:37 PM, aighes h.scholl...@googlemail.com wrote:
Hi,
On Geofabrik I found the new pbf-files. They ar much smaller, so I would
like to use them. Are there any ready-to-use files of osmosis, splitter and
mkgmap which can use the binary format?
For the splitter and
My advice is to wait a few weeks for new releases to come out.
Scott
On Wed, Sep 22, 2010 at 12:37 PM, aighes h.scholl...@googlemail.com wrote:
Hi,
On Geofabrik I found the new pbf-files. They ar much smaller, so I would
like to use them. Are there any ready-to-use files of osmosis,
On Tue, Sep 21, 2010 at 3:05 PM, Jeffrey C. Ollie j...@ocjtech.us wrote:
On Thu, Sep 16, 2010 at 4:59 PM, Scott Crosby scro...@cs.rice.edu wrote:
Well, technically two passes; the first pass is needed to figure out
where to split.
I was excited to see this, however I'm having some
On Thu, Sep 16, 2010 at 12:33 PM, WanMil wmgc...@web.de wrote:
Hi Steve,
that was a quick implementation!
I haven't tried so far the new binary format. I haven't found a download
for the osmprotobuf.jar. Is there any? Download links should be added to
the documentation and the website if
Ok, that means we cannot use the common planet dumps for this and a
separate step (geographical sorting) is needed which maybe eats up the
advantage to skip the tile splitter step. Just keep the idea in mind and
give it a try when the geographical sorting is available.
I designed the format
Well, technically two passes; the first pass is needed to figure out
where to split.
A new set of patches and line of development in my tree.
Features:
About 1/3 of the RAM usage. An entire planet can be split into 1200
areas in one pass with -Xmx5000m --max-nodes=100 in one hour.
No
On Mon, Sep 13, 2010 at 6:06 AM, Steve Ratcliffe st...@parabola.me.uk wrote:
Hi Scott
I am adding support for your binary format to mkgmap itself (not the
splitter).
Excellent! Thank you.
Now I've done enough refactoring of the XML reader to allow me to
start I have a few questions.
1.
On Mon, Sep 13, 2010 at 3:36 PM, Steve Ratcliffe st...@parabola.me.uk wrote:
Its needed because mkgmap takes all kinds of input files and I don't
want the user to have to say what the file format is, I just want
mkgmap to work out the file format and use the correct reader.
I do this by
On Sun, Sep 12, 2010 at 6:39 AM, Clinton Gladstone
clinton.gladst...@googlemail.com wrote:
On Sep 9, 2010, at 19:55, Scott Crosby wrote:
The format is stable, but I want to release one more RC, with a full
validation before I declare it stable. I expect no incompatible
changes
My internal repository has several independent development threads.
Only one of them is the binary format. The other development threads
included patches that are already in and some have not been
benchmarked/tested thoroughly.
* The binary format.
* Improved double writing for XML output.
*
On Wed, Sep 8, 2010 at 2:27 PM, Chris Miller chris_overs...@hotmail.com wrote:
Hi Jeff,
Scott Crosby posted a message to this list back in June asking for comment
on his binary format. My thoughts at the time were that it looked rather
promising and adding support for it to the splitter would
On Tue, Aug 17, 2010 at 7:12 AM, Chris Miller
chris_overs...@hotmail.com wrote:
Hello Francois,
It looks like this is a bug that was introduced by some patches I applied
for Scott last night. I've rolled back the changes for now until I get a
chance to debug the problem further. If you grab
Is there something wrong with this patch that kept it from going in?
Scott
On Thu, Jun 10, 2010 at 2:17 PM, Scott Crosby scrosb...@gmail.com wrote:
This patch to the splitter makes
this warning MUCH more rare. With this patch, I can split the entire
planet into 17219 areas with max-nodes
What is the URL for the SRTM data and the command lines you're using to
process it?
Scott
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
On Fri, Jun 11, 2010 at 4:17 AM, Chris Miller chris_overs...@hotmail.comwrote:
The limitation I see with a density map approach is that parts
of the planet that have the highest node density would by definition
contain
the smallest split areas. This means the density map would need to be
On Fri, Jun 11, 2010 at 6:52 PM, Chris Miller chris_overs...@hotmail.comwrote:
Hi Scott,
This probably explains why
no one from the mkgmap/splitter community noticed or commented on your
original
post on the osm-dev list - if they're anything like me they don't pay too
much attention to
and 550M nodes, that is
over 5 trillion bounds-checks that are
not run in parallel. An index that can can map a node to the regions that
may contain it could avoid 99% of these checks.
Scott
From 3d3d7275b8c83ecda4e71a59023c4f11485388db Mon Sep 17 00:00:00 2001
From: Scott Crosby scro
: Scott Crosby scro...@cs.rice.edu
Date: Fri, 19 Mar 2010 10:56:34 -0500
Subject: [PATCH 7/8] Fix infinite recursion bugs when finding tiles with the density map.
When running with a small node count limit, we hit various infinite
recursions. This fixes those bugs when splitting all the way down
The reason for this was the costs of initializing were showing up in
the profile.
Do you mean the cost of initializing the Element instances? If so then yes,
that's something that I'd caught previously in profiling too, hence why
they
were being reused and reset (prior to r109 that is :).
37 matches
Mail list logo
