I've got an OSM tile server based on the Ubuntu instructions that I've
been running and updating with Minutely Mapnik for over a month now. I
just noticed that southern Australia has issues like incomplete roads,
lack of large rivers, no green spaces, and no city labels. I have no
idea how or
The Toronto Hack Weekend is coming up in two weeks. It's going to be
pretty darn good. We've got a super venue, with tons of space and
rock solid wifi; The Ryerson University Geography department is
hosting us.
Should you join us in Toronto? Absolutely. Sign up on the wiki now.
http://wiki.op
On 1-3-2012 15:28, Sven Geggus wrote:
Quite in contrast to multipolygon relations, there is almost no computation
in route relations, their member ways are just added to the planet_osm_lines
table, they are not even concatenated.
They are concatenated, up to a maximum length. Still, that's sti
On Thu, Mar 1, 2012 at 9:13 AM, Josh Doe wrote:
> On Thu, Mar 1, 2012 at 9:00 AM, Mike N wrote:
>> On 3/1/2012 6:59 AM, Josh Doe wrote:
>>>
>>> Last night I checked in a minimally-functional (and definitely
>>> experimental) conflation plugin, appropriately called conflation.
>>
>>
>> I re-downl
Hi
I generated a new charge of history extracts, based on the 120213 full
history dump. They have been created from the latest
full-experimental-dump [1] using my history splitter [2], based on
Jochen Topfs really great osmium framework [3]. They contain multiple
versions of an object. If you
> their member ways are just added to the planet_osm_lines
> table, they are not even concatenated.
> Sven
Are you sure ? I might be mistaken, but thought they were concatenated and
then split again if in exces of 1°x1°
(line ~1080 in output-pgsql.c )
I haven't fully checked what does the build
"sly (sylvain letuffe)" wrote:
> Reading that thread, I remembered that I don't need type=route either, I've
> commented that part of osm2pgsql but the speed gain is hardly noticeable (if
> at all)
Quite in contrast to multipolygon relations, there is almost no computation
in route relations,
> I know that there are precedents, but I am highly averse to coding
> specific relation types into osm2pgsql.
So do I, as you mentionned below, the problem is not osm2pgsql specific, but
will need work in every tool to maintain support for ever changing relation's
way of tagging, and every new
Le jeudi 1 mars 2012 11:30:03, Sven Geggus a écrit :
> You could just skip the code following "if( strcmp(type, "route") == 0 )"
> in output-pgsql.c, but I doubt that this will increase your processing
> speed significantly because most of the hard processing work is for
> multipolygons relations a
Skye Book wrote:
> Thanks for the clear explanation.. That meshes well with what I understood
> from reading the wiki and cursory looks at source code
http://wiki.openstreetmap.org/wiki/Tirex/Overview has a nice diagram about
how the different modules communicate.
It is possible to run differen
Darafei Praliaskouski wrote:
> I am not using route= relations in osm2pgsql. Is there a way to skip their
> processing, to get more speed than 4 relations/sec?
You could just skip the code following "if( strcmp(type, "route") == 0 )" in
output-pgsql.c, but I doubt that this will increase your p
11 matches
Mail list logo
