On Mon, Mar 09, 2009 at 12:35:48PM +0100, Stefan Baebler wrote:
> I consider my contributions so minor that i hereby give you all the
> power to relicense them as you please.
Same from me.
Jochen
--
Jochen Topf joc...@remote.org http://www.remote.org/jochen/ +49-721-
h ressources would you need? Tomcat and the Osmosis dev stuff ?
I guess the whole thing could be swapped out most of the time and only
needs a few resources for the actual build every few hours? Do several
people need access? root access?
Jochen
--
Jochen Topf joc...@remote.org http://www.remote.
shouldn't affect the rest of the application.
If somebody doesn't like the functions, please complain. :-)
Jochen
--
Jochen Topf joc...@remote.org http://www.remote.org/jochen/ +49-721-388298
___
osmosis-dev mailing list
osmosis-dev@openstr
group 'osm' and this way you can work on the same
stuff. If needed we can also create sudo scripts, special users, etc. as
needed.
Jochen
--
Jochen Topf joc...@remote.org http://www.remote.org/jochen/ +49-721-388298
___
osmosis-de
or do you just call CLUSTER after the import?
When I tested CLUSTER it helped with reads, but creating the cluster was
very expensive.
Jochen
--
Jochen Topf joc...@remote.org http://www.remote.org/jochen/ +49-721-388298
___
osmosis-dev mailing lis
-node way? A
> *way* is composed by at least two nodes.
>
> That's a mapping error, IMHO.
Of course it is. But those errors tend to happen so you need to deal with
them. And thats what this thread is about.
Jochen
--
Jochen Topf joc...@remote.org http://w
nd/or a
> > step-by-step guide to reproduce this? Like the osmosis command line you're
> > using, the kind of data you're trying to put in the database - that would be
> > very helpful.
> >
> > Regards
> > Igor
> >
> __
gt; > When a one node way is present in the database and osmosis creates a
> >> > >> linestring geometry for it the resulting geometry is something like
> >> > >> LINESTRING(139.386972 37.095865)
> >> > >>
> >> > >> When we process this li
Sorry, that was a bit unclear. You can't just look at the node ids, you have
to look at the geometries of those nodes, too.
Jochen
On Sat, Apr 09, 2011 at 02:36:36PM +0400, Kirill Bestoujev wrote:
> Date: Sat, 9 Apr 2011 14:36:36 +0400
> From: Kirill Bestoujev
> To: Jochen Topf
Osmium (https://github.com/joto/osmium
either to use it or to steal ideas from. It can read and write XML and PBF,
assemble multipolygons, do several passes over the input, filter data, create
shapefiles, and many other things. :-)
Jochen
--
Jochen Topf joc...@remote.org http://www.remote.org/joc
rmalized so Osmosis can still make
those checks.
The Map could be connected to some registry for the strings
(or the strings would be objects instead with some extra information.) For
each one you would have at least the two options:
If a tasks encounters an object of this type in the pipeline
those can be quite large. The PBF spec
says that an uncompressed block can be a maximum of 32 MBytes. Thats not the
only buffer you need. I'd have to look a the source code to check the overall
buffer size you need, but in any case its not negligable if you have many files
open.
Jochen
--
Jo
limit, but is a good starting point for now.
>
> Cheers,
> Brett
> ___
> osmosis-dev mailing list
> osmosis-dev@openstreetmap.org
> http://lists.openstreetmap.org/listinfo/osmosis-dev
--
Jochen Topf joc...@remote.org http://www.remote.org/jochen/ +49-721-388298
___
osmosis-dev mailing list
osmosis-dev@openstreetmap.org
http://lists.openstreetmap.org/listinfo/osmosis-dev
On Wed, Nov 14, 2012 at 10:33:43PM +1100, Brett Henderson wrote:
> Jochen Topf was the one who originally introduced the checks in
> WayGeometryBuilder to ensure a Way contained at least two nodes. He might
> have some thoughts on whether we can remove the checks. Perhaps it was
> osmosis-dev mailing list
> osmosis-dev@openstreetmap.org
> http://lists.openstreetmap.org/listinfo/osmosis-dev
--
Jochen Topf joc...@remote.org http://www.remote.org/jochen/ +49-721-388298
___
osmosis-dev mailing list
osmosis-dev@openstreetmap.org
http://lists.openstreetmap.org/listinfo/osmosis-dev
ntations are, I don't know. Reading PBF files is not so
simple, there are undocumented details that can trip you up. So using either of
these might be more difficult than with Osmosis.
Jochen
--
Jochen Topf joc...@remote.org http://www.jochentopf.com
/oss-parent/5/oss-parent-5.pom
Download http://repo1.maven.org/maven2/antlr/antlr/2.7.7/antlr-2.7.7.pom
...
I don't know gradle at all. Is there a list of those dependencies somewhere?
Any suggestions how to disable all this and tell gradle where to search for its
dependecies locally?
Jochen
to be parsed by as many threads as
you want. This way you already get a nice speedup without any changes to
the file format.
Jochen
--
Jochen Topf joc...@remote.org http://www.jochentopf.com/ +49-351-31778688
___
osmosis-dev mailing list
osmosis-dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/osmosis-dev
reetmap.org
> > https://lists.openstreetmap.org/listinfo/osmosis-dev
>
> ___
> osmosis-dev mailing list
> osmosis-dev@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/osmosis-dev
--
Jochen Topf joc...@remote.org http://www.jochentopf.com/ +49-351-31778688
___
osmosis-dev mailing list
osmosis-dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/osmosis-dev
create those shapefiles, why
don't you do the splitting in this step *after* creating the geometries and
before writing them into shapefiles? That is probably much easier to do than
based on the PBF due to the structure of the OSM data files.
Jochen
--
Jochen Topf joc...@remote.org http://www.joc
On Mo, Apr 18, 2016 at 11:52:24 +0200, Sylvain Melin wrote:
> On 18/04/2016 11:00, Jochen Topf wrote:
> >On Mo, Apr 18, 2016 at 10:10:06 +0200, Sylvain Melin wrote:
> >>My plan is to :
> >>- exploit a planet sized pbf file
> >>- cut it into 1° tiles using osmos
sed and md5sum verified originals, but still got
> the same error.
You are confusing "changeset" files with "change" files. Those are
different beasts. Change files contain the actual changes, they end in
.osc or .osc.gz. Changeset files contain the meta information about t
ove support from our apps for PBF files without this information
> (thus the need to detect if the file has way nodes).
Osmium sets "LocationsOnWays" as an "optional feature" string in the
header to signify that there are locations on the ways.
Jochen
--
Jochen Topf jo
n't come up there.
> Long story short, rather than make changes directly to the file in Osmosis
> and create a fork, should we apply them to upstream first and then re-sync
> Osmosis with that?
Yes, we should do this upstream in https://github.com/scrosby/OSM-binary.
If somebody creat
ferent type of
> entities and the bounding box of all those entities
>
> thanks much in advance,
> Andrew
> ___
> osmosis-dev mailing list
> osmosis-dev@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/osmosis-dev
--
Jochen Topf joc...@remote.org https://www.jochentopf.com/ +49-351-31778688
___
osmosis-dev mailing list
osmosis-dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/osmosis-dev
84 ((57117152 + 21434884) / 2
> = 39276018), uid: 109452 ((57550 + 109452) / 2 = 83501 =>
> https://www.openstreetmap.org/api/0.6/user/83501), version: 5
> ___
> osmosis-dev mailing list
> osmosis-de
26 matches
Mail list logo
