hi,
I tried to report integrity
osmosis --rs host=localhost database=osm user=postgres password=?
validateSchemaVersion=yes allowIncorrectSchemaVersion=no outPipe.0=db --dd
inPipe.0=db outPipe.0=dataset --ri inPipe.0=dataset
and got this error
SEVERE: Thread for task 1-rs failed
That integer is just on the wrong side of what you can represent in 32
bits. You probably need to upgrade to an osmosis version that supports
64 bit integers, as the ids in OSM space have crossed the 32 bit
boundary recently.
On Fri, May 3, 2013 at 3:23 PM, Martin Schafran mar...@ampelmeter.com
Hi,
Le 02/05/2013 22:30, Michael Spreng a écrit :
This problem comes from the diff, when an object is deleted, the Version
is not incremented. But for logical reasons, it should. This
incrementation is missing in osmosis as well as osmconvert, so at the
moment, custom diffs can't be merged
Perhaps - is there any specific reason you need to use simple instead
of snapshot?
i want to have the option left open to use hibernate.
as far as i know hibernate doesn't support hstore.
with custom types I could only read the key=values.
___
Paweł Paprota wrote:
Currently I am on a two-month work trip in Germany with not much
free time but I really miss OSM and OWL development so I plan to
get back to it some time in June when I'm back at home.
\o/
When you look at it, there is really not a lot of stuff to be done
before OWL
Pawel, i do not understand how the New History Tab will scale and how it
will be fast. Right now it's slow.
The old owl fell over b/c of scale problems and my understanding is that
the underlying technical challenge of how to make massive changesets
browsable in rev chronological order on a map
What exactly do you mean by slow? OWL API response is slow or
client-side Javascript is slowing down the browser (likely because of
the number of GeoJSON features displayed at once)?
The OWL API performance issues is indeed the most challenging problem to
solve here. There are couple of things:
Sorry, I did not finish one of the sentences properly - about knn in
Postgres:
* PostgreSQL now supports k nearest neighbors indexing[1][2] - the
distance function/operator could be defined for OSM changesets so that a
query for given tile (or tile range) uses the knn index and at the same
time
On 05/03/2013 02:21 PM, Alex Barth wrote:
Pawel, i do not understand how the New History Tab will scale and how it
will be fast. Right now it's slow.
Since the solution you made doesn't scale either. (Try browsing any
city/town in The Netherlands.) How is it an improvement?
--
---
m.v.g.,
Since the solution you made doesn't scale either. (Try browsing any
city/town in The Netherlands.) How is it an improvement?
Well while http://osmlab.github.io/latest-changes is not fast right now
there's a clear and scalable path to make it fast. Speeding up
/latest-changes is much simpler as
Btw, I forgot to mention that we've got a very similar browsing interface
on OSM.org - we just don't break it down by changesets
http://cl.ly/image/09421k3A0G0b
On Thu, May 2, 2013 at 11:18 AM, Alex Barth a...@mapbox.com wrote:
At this weekend's Chicago hack weekend Tom and I worked on a
On Thu, May 2, 2013 at 11:18 PM, Alex Barth a...@mapbox.com wrote:
At this weekend's Chicago hack weekend Tom and I worked on a prototype
that could be a viable solution for our currently broken history tab. It is
taking a very different approach in comparison to Pawel's history tab [1]
by
On Fri, May 3, 2013 at 1:03 PM, Eugene Alvin Villar sea...@gmail.comwrote:
On Thu, May 2, 2013 at 11:18 PM, Alex Barth a...@mapbox.com wrote:
At this weekend's Chicago hack weekend Tom and I worked on a prototype
that could be a viable solution for our currently broken history tab. It is
On May 3, 2013, at 11:23 AM, Ian Dees wrote:
On Fri, May 3, 2013 at 1:03 PM, Eugene Alvin Villar sea...@gmail.com wrote:
On Thu, May 2, 2013 at 11:18 PM, Alex Barth a...@mapbox.com wrote:
At this weekend's Chicago hack weekend Tom and I worked on a prototype that
could be a viable solution
On Sat, May 4, 2013 at 2:27 AM, Michal Migurski m...@teczno.com wrote:
Would it be silly to suggest that changesets get their own geometries in
PostGIS and an associated spatial index, consisting of every way and node
deleted, moved, etc.?
Isn't this similar to what Paweł's New History Tab
On Sat, May 4, 2013 at 2:23 AM, Ian Dees ian.d...@gmail.com wrote:
On Fri, May 3, 2013 at 1:03 PM, Eugene Alvin Villar sea...@gmail.comwrote:
At least the current system will show you the deletion changeset.
... after paging through dozens of big changesets. This is by no means
perfect,
On May 3, 2013, at 12:22 PM, Eugene Alvin Villar wrote:
On Sat, May 4, 2013 at 2:27 AM, Michal Migurski m...@teczno.com wrote:
Would it be silly to suggest that changesets get their own geometries in
PostGIS and an associated spatial index, consisting of every way and node
deleted, moved,
On Fri, May 3, 2013 at 2:31 PM, Michal Migurski m...@teczno.com wrote:
On May 3, 2013, at 12:22 PM, Eugene Alvin Villar wrote:
On Sat, May 4, 2013 at 2:27 AM, Michal Migurski m...@teczno.com wrote:
Would it be silly to suggest that changesets get their own geometries
in PostGIS and an
Hi,
On 03.05.2013 20:27, Michal Migurski wrote:
Would it be silly to suggest that changesets get their own geometries in
PostGIS and an associated spatial index, consisting of every way and node
deleted, moved, etc.?
The current OSM API doesn't even use PostGIS and therefore no spatial
Hi!
Tonight a very stupid question. I got interested in the new ID editor and
I've been trying to find out more about it, but without success.
Potlatch2 has a wiki page with getting started info, how to set it up,
customize etc. and a mailing list. JOSM has its own Wiki with technical
stuff and
On Fri, May 3, 2013 at 2:29 PM, NopMap ekkeh...@gmx.de wrote:
Tonight a very stupid question. I got interested in the new ID editor and
I've been trying to find out more about it, but without success.
Hi Nop,
If you're looking for technical information, you want to look at the GitHub
Hi Nop,
By virtue of being new, iD doesn't have quite as much docs for different
use cases as Potlatch 2 or similar. But there are a few resources to get
started with:
* http://mapbox.com/osmdev/ (dev blog w/ series of posts about architecture)
*
tmcw wrote:
As far as documentation for _using_ the editor, there's help
documentation embedded in it as well as an intro tour for new users.
and it's a zillion times more accessible than the equivalent in P2, let
alone JOSM or anything else.
cheers
Richard
--
View this message in
Second that. The in-app new user introduction is great. Everyone
should try it, even if you think you know what you are doing. Just to
appreciate what an amazing job it is.
This will make mapping parties go so much smoother, too.
On Fri, May 3, 2013 at 3:47 PM, Richard Fairhurst
Actually, my fork of the openstreetmap-website repository only contains
the UI part of the new history tab.
Heavy lifting (including creating and indexing geometry) is done by OWL
which is here:
https://github.com/ppawel/openstreetmap-watch-list
Paweł
On Fri, May 3, 2013, at 22:23, Eugene
On Sun, Apr 28, 2013 at 9:26 AM, Dirk Stöcker openstreet...@dstoecker.dewrote:
On Sun, 28 Apr 2013, Felix Natter wrote:
One concern is: Could you consider making JMapViewer releases with
version numbers? That would make the Debian packaging easier / more
meaningful.
Hmm. Open a ticket
On Thu, 2 May 2013, colliar wrote:
Finally I do not understand match:
Is it possible to have a entry only active for certain type of object
and/or certain other tag on the objects ?
E.g.:
* have combo tag=service values=... only active if
highway=service is already chosen/tagged.
* have text
27 matches
Mail list logo
