On Thu, Dec 10, 2009 at 11:24:00AM +0100, Hakan Tandogan wrote:
If it is possible, I'd love to share admin responsibilities on the box you
are already get access to.
Send me your preferred login name and a ssh key and I'll create the account for
you.
All users are in the same group 'osm' and
Hi,
On Wed, Dec 9, 2009 at 2:55 AM, Hakan Tandogan hakan at gurkensalat.comwrote:
Hi Brett,
I finally got postgis-1.3.2 synched to repo1.maven.org (creating accounts
at sonatype, signing artifacts and POMs, etc. etc. etc.)
I can't check the ant resolve part in ivy till I later tonight,
[ivy:resolve]
http://repo1.maven.org/maven2/org/postgis/postgis/1.3.2/postgis-1.3.2.pom
[ivy:resolve] -- artifact org.postgis#postgis;1.3.2!postgis.jar:
[ivy:resolve]
http://repo1.maven.org/maven2/org/postgis/postgis/1.3.2/postgis-1.3.2.jar
[ivy:resolve]
Peter
Here's an implementation of the first item on your list (ways not
relations):
http://osmxapi.hypercube.telascience.org/api/0.6/way/#id/#version/full
The following example, for Pharaoh's Island in the River Thames shows a
series of edits with different versions of nodes depending on which
http://osmxapi.hypercube.telascience.org/api/0.6/way/8136261/8/full
http://osmxapi.hypercube.telascience.org/api/0.6/way/8136261/9/full
http://osmxapi.hypercube.telascience.org/api/0.6/way/8136261/10/full
http://osmxapi.hypercube.telascience.org/api/0.6/way/8136261/11/full
This should work
2009/12/10 Peter Körner osm-li...@mazdermind.de:
http://osmxapi.hypercube.telascience.org/api/0.6/way/8136261/8/full
http://osmxapi.hypercube.telascience.org/api/0.6/way/8136261/9/full
http://osmxapi.hypercube.telascience.org/api/0.6/way/8136261/10/full
On Wed, Dec 9, 2009 at 00:04, Lars Francke lars.fran...@gmail.com wrote:
I'd take a look at it if no one else is working on it but if someone
else is interested I'd gladly step back :)
As no one has stepped forward with any ideas or offers to implement
this I'll take a shot at it. This also
What about deleted nodes/ways/relations, but instead of giving an ID
how about a bounding box so you can undo a delete?
For the moment I'm thinking about a changeset revert. In a changeset
you'll get deleted objects marked as such. Finding a deleted node (or
better: the changeset in which a
There are requests in JOSM's trac to improve the handling of API
errors. To do that JOSM needs to get a better understanding on what
is wrong with the data.
Currently, JOSM is parsing the error strings the API is returning.
This is far from ideal because they are not structured, not documented
On Thu, Dec 10, 2009 at 10:16 AM, Matthias Julius li...@julius-net.netwrote:
There are requests in JOSM's trac to improve the handling of API
errors. To do that JOSM needs to get a better understanding on what
is wrong with the data.
Currently, JOSM is parsing the error strings the API is
On a related note, I would be very interested in seeing a progress of
some kind being returned when doing a osmChange upload. I realize that
it is difficult (because it could fail after spitting out lots of
seemingly valid IDs), but if it was documented it would be doable.
Are you talking
On Thu, Dec 10, 2009 at 10:52 AM, Peter Körner osm-li...@mazdermind.dewrote:
On a related note, I would be very interested in seeing a progress of some
kind being returned when doing a osmChange upload. I realize that it is
difficult (because it could fail after spitting out lots of seemingly
On Thu, Dec 10, 2009 at 16:20, Ian Dees ian.d...@gmail.com wrote:
On Thu, Dec 10, 2009 at 10:16 AM, Matthias Julius li...@julius-net.net
wrote:
There are requests in JOSM's trac to improve the handling of API
errors. To do that JOSM needs to get a better understanding on what
is wrong with
You mean showing upload progress in JOSM as opposed to the current
cylon impression? That could be implemented by counting the number of
bytes of the osmChange request that have been successfully sent over
the wire. That's how upload progress bars are usually implemented.
Obviously the
On Thu, Dec 10, 2009 at 17:01, Peter Körner osm-li...@mazdermind.de wrote:
You mean showing upload progress in JOSM as opposed to the current
cylon impression? That could be implemented by counting the number of
bytes of the osmChange request that have been successfully sent over
the wire.
On Thu, Dec 10, 2009 at 10:55 AM, Ævar Arnfjörð Bjarmason
ava...@gmail.comwrote:
On Thu, Dec 10, 2009 at 16:20, Ian Dees ian.d...@gmail.com wrote:
On Thu, Dec 10, 2009 at 10:16 AM, Matthias Julius li...@julius-net.net
wrote:
There are requests in JOSM's trac to improve the handling of
For JOSM, the structured data currently embedded in the error message is
important. Examples are object ids of already deleted objects (410 Gone) or
a date (the close date of a changeset in a 409 Conflict).
I'd prefer a parseable error document in case of http error codes,
preferably in XML. This
You mean showing upload progress in JOSM as opposed to the current cylon
impression? That could be implemented by counting the number
of bytes of the osmChange request that have been successfully sent over the
wire. That's how upload progress bars are usually implemented.
It's not the
There is alreay ProgressInputStream
http://josm.openstreetmap.de/browser/trunk/src/org/openstreetmap/josm/io/ProgressInputStream.java
in the JOSM code base and a ProgressOutputStream could be built easily.
But again, I don't think this would help much. If we really wanted to display
progress
Hello,
I have about 4 million addresses that I need to geocode. These addresses are
mostly in the US, but about 200K of them are in Europe and a smattering
elsewhere. I already have an approach for geocoding US addresses, but I'd like
to try using Nominatim for geocoding the non-US addresses.
On Thu, Dec 10, 2009 at 17:25, Karl Guggisberg
karl.guggisb...@guggis.ch wrote:
You mean showing upload progress in JOSM as opposed to the current cylon
impression? That could be implemented by counting the number
of bytes of the osmChange request that have been successfully sent over the
On Thu, Dec 10, 2009 at 11:39 AM, Ævar Arnfjörð Bjarmason
ava...@gmail.comwrote:
On Thu, Dec 10, 2009 at 17:25, Karl Guggisberg
karl.guggisb...@guggis.ch wrote:
You mean showing upload progress in JOSM as opposed to the current cylon
impression? That could be implemented by counting the
I just noticed the Geocoding mailing list. My bad. I will repost there.
Thanks!
Jason R. Surratt
SPADAC
email: jason.surr...@spadac.com
From: dev-boun...@openstreetmap.org [mailto:dev-boun...@openstreetmap.org] On
Behalf Of Jason Surratt
Sent: Thursday, December 10, 2009 12:38 PM
To:
On 10/12/09 17:39, Ævar Arnfjörð Bjarmason wrote:
2. process on the server - this takes most of the time, no feedback here
Yup, PostgreSQL can't tell you where it's at in the query:
http://wiki.postgresql.org/wiki/Query_progress_indication
Um... It's not like it's a single query. It will be
Am Donnerstag, den 10.12.2009, 15:56 +0100 schrieb Dirk Stöcker:
On Thu, 10 Dec 2009, Dieter Muecke wrote:
Instead of restarting JOSM by hand after plugin update the code snippet
below does it programmatically. It works on Mac OSX but before I submit
a patch I would like know how do the
Hi,
I've created a small Python tool which buffers the polygon in a polygon
file (for Osmosis), and creates a new polygon file. It can be found
here: [1]. For the buffering PostGIS is used. All Canadian polygon files
from [2] have been tested and are working.
Requirements: Python (2.6, but
Jason Surratt schrieb:
I just noticed the Geocoding mailing list. My bad. I will repost there.
Please also post here if you got a solution.
Peter
___
dev mailing list
dev@openstreetmap.org
http://lists.openstreetmap.org/listinfo/dev
On this note, has anyone here played Puzzle Pirates?
I mention this because the game is written in Java, and has an online update
capability.
You down load a Java loader application (small) that fetches the latest
version of the code from the server. When the upload is complete it runs the
On Thu, 10 Dec 2009, Dieter Muecke wrote:
Instead of restarting JOSM by hand after plugin update the code snippet
below does it programmatically. It works on Mac OSX but before I submit
a patch I would like know how do the same on Windows and Linux.
Why do you want restarting JOSM after
Dirk Stöcker openstreet...@dstoecker.de writes:
On Thu, 10 Dec 2009, Dieter Muecke wrote:
Instead of restarting JOSM by hand after plugin update the code snippet
below does it programmatically. It works on Mac OSX but before I submit
a patch I would like know how do the same on Windows and
Lennard wrote:
Paul Johnson wrote:
created_by= tags get stomped by Potlatch, JOSM leaves it alone if it's
already set (unless, of course, a JOSM user deliberately deletes the
existing created_by tags). This would give severely skewed results in
favor of Potlatch.
You would be correct, if
On 10 Dec 2009, at 15:41, Matthias Julius wrote:
Dirk Stöcker openstreet...@dstoecker.de writes:
On Thu, 10 Dec 2009, Dieter Muecke wrote:
Instead of restarting JOSM by hand after plugin update the code snippet
below does it programmatically. It works on Mac OSX but before I submit
a
32 matches
Mail list logo
