On Sat, Sep 19, 2009 at 7:42 PM, Jochen Topf joc...@remote.org wrote:
(I beleive it used to vacuum, but I don't immediately see it in the
current source).
I always disabled autovacuum for this kind of database. It tends to always
come at the wrong time. Its better to do the vacuum once after
The majority of Australian postcodes have been converted from shape
files to osm files, however there is a couple of complex/big areas
that I'm having trouble dealing with in JOSM as a result, is there a
simple way to simplify these files from a command line util?
I think osmosis would help you.
In any case, I have been splitting osm files in perl.
they are just xml files.
you need to look into things that are referenced however...
mike
On Sun, Sep 20, 2009 at 1:47 PM, John Smith deltafoxtrot...@gmail.com wrote:
The majority of Australian postcodes have
John Smith wrote:
The majority of Australian postcodes have been converted from shape
files to osm files, however there is a couple of complex/big areas
that I'm having trouble dealing with in JOSM as a result, is there a
simple way to simplify these files from a command line util?
What
2009/9/20 Emilie Laffray emilie.laff...@gmail.com:
John Smith wrote:
The majority of Australian postcodes have been converted from shape
files to osm files, however there is a couple of complex/big areas
that I'm having trouble dealing with in JOSM as a result, is there a
simple way to
2009/9/20 jamesmikedup...@googlemail.com jamesmikedup...@googlemail.com:
I think osmosis would help you.
In any case, I have been splitting osm files in perl.
they are just xml files.
you need to look into things that are referenced however...
They are boundaries and simplifying the number of
John,
John Smith wrote:
The majority of Australian postcodes have been converted from shape
files to osm files, however there is a couple of complex/big areas
that I'm having trouble dealing with in JOSM as a result, is there a
simple way to simplify these files from a command line util?
Let
2009/9/21 Frederik Ramm frede...@remote.org:
I have not checked this but given the ignorance that speaks from the above,
I didn't asked to be insulted, if you don't want to help that's fine
by cut out the name calling.
I neither created the file, nor did I intented to import it
automatically,
1. Doing a vacuum immediately after the import isn't useful, there is
nothing to vacuum by definition.
While this is true an ANALYZE should still be done to initialize the statistics.
2. Doing a vacuum after a diff is also useless, since the vacuum will
probably takes much much longer than
On Sun, Sep 20, 2009 at 6:16 PM, Lars Francke lars.fran...@gmail.com wrote:
1. Doing a vacuum immediately after the import isn't useful, there is
nothing to vacuum by definition.
While this is true an ANALYZE should still be done to initialize the
statistics.
Which it does, but ANALYZE is
Hi,
Lars Francke wrote:
On a related note: There was a change between PostgreSQL 8.3 and 8.4
which increased the default_statistics_target from 10 to 100 and its
maximum from 1.000 to 10.000 which makes ANALYZE runs take longer but
at least for me it helps a lot.
Have you, too, noticed the
Hello,
I have been hacking the current version of polyshp2osm for the Corine
import. This version is adding the following things:
- Support for 0.6
- Support for multipolygons
- Added new parameter to start numbering at a specific number
- Refactoring of the code to handle better
On Sun, Sep 20, 2009 at 7:43 PM, Frederik Ramm frede...@remote.org wrote:
Hi,
Lars Francke wrote:
On a related note: There was a change between PostgreSQL 8.3 and 8.4
which increased the default_statistics_target from 10 to 100 and its
maximum from 1.000 to 10.000 which makes ANALYZE runs
Hi everyone,
For the past few days I've been experimenting with PostGIS, trying to
create some basic support for it from Kosmos. I've managed to setup the
DB, import the UK data and even had some moderate success with accessing
the data from Kosmos code.
Since I'm not very good at SQL (having
Frederik,
full agreement to all this arguments. but one of the problems is none of
this is documented. the import page in the wiki is old has no best practice
like you recommend here. and we have no tools which makes it easier to deal
with such data.
If others agree the wiki should be updated.
Hi there!
Some time ago I told you that I'm developing a label placement optimizer
for SVG maps created with Osmarender (OSMLabelOptimizer, see [1]). What
I noticed while coding the tool was that Osmarender removes some
information from the original osm data when converting to SVG. For
example it
Apollinaris Schoell wrote:
Frederik,
full agreement to all this arguments. but one of the problems is none of
this is documented. the import page in the wiki is old has no best
practice like you recommend here. and we have no tools which makes it
easier to deal with such data.
If others
On Sun, Sep 20, 2009 at 4:40 AM, Ľubomír Varga lu...@plaintext.sk wrote:
AFAIK this is possible right now. Just use PostGis database of world, connect
GeoServer like renderer / transformer to WMS / WFS / WSC and add WMS layer to
JOSM. So in JOSM you could view whole world from PostGis
Hello,
please do not develop or checkin new stuff in next time so code can mature
a bit (but do bugfixes instead :-). If no larger bugs show inbetween I
would say the next tested version should be released next weekend.
Translators please continue translating - I fixed lots of typos in the
Hi Dirk,
I have checked in a new Address Interpolation plugin into SVN - I hope it
doesn't qualify as new since it doesn't change the JOSM code itself.
Let me know if something doesn't look right.
Thanks,
Mike Nice
--
From: Dirk
Ulf Lamping schrieb:
Hi!
Some days ago, I came across the Java portable package on
PortableApps.com [1].
That made me think if it might be possible to install JAVA and JOSM on
an USB stick and run JOSM on any suitable Windows machine without any
further installation on the target
Hello,
as I still do not like to introduce context based translation for josm,
but on the other side we have conflicting strings in JOSM I now
implemented the middle way:
When a string starts with ~ everything between ~ and the next : is
stripped from it when displayed. This allows to make
22 matches
Mail list logo
