mahmoud ghareebh | 13 Apr 12:43 2013
Picon

FW: question

hi 
i`m trying to install osmosis on windows 7 , i have jdk 6 , and i follow this instructions :
./gradlew assemble
success
Perform a complete build including unit tests:
./gradlew build
failure , and give me errors i`m attach the report , could u help me?
<!-- .ExternalClass .ecxhmmessage P { padding:0px; } .ExternalClass body.ecxhmmessage { font-size:12pt; font-family:Calibri; } -->
Attachment (tests.zip): application/zip, 36 KiB
_______________________________________________
osmosis-dev mailing list
osmosis-dev@...
http://lists.openstreetmap.org/listinfo/osmosis-dev
Paul Norman | 7 Apr 19:44 2013
Picon

Re: Problem with Windows 7

I find no mention of a –mapfile-writer task in the usage page. Are you using a plugin?

 

From: Malky [mailto:malky-D0VgoRl4D1jNcuzrQHMqQ9BPR1lH4CV8@public.gmane.org]
Sent: Sunday, April 07, 2013 5:48 AM
To: osmosis-dev-3+rWM/WnaLOn4i5uJCXUsti2O/JbrIOy@public.gmane.org
Subject: [osmosis-dev] Problem with Windows 7

 

When I try to create a map, I get a "Files was unexpected at this time" error!

 

I know it must be a variable error with the path name Program Files as I had something similar getting osmosis to run, but I can' figure out what or where?

 

I tried this osmosis

 

--read-xml file="C:\bulgaria.osm" --mapfile-writer file="C:\varna.map" bbox=42.185,27.063,43.463,28.103

 

before getting the error.

 

Any ideas are more than welcome as it's driving me mad.

 

Malky

_______________________________________________
osmosis-dev mailing list
osmosis-dev@...
http://lists.openstreetmap.org/listinfo/osmosis-dev
Malky | 7 Apr 14:47 2013

Problem with Windows 7

When I try to create a map, I get a "Files was unexpected at this time" error!

 

I know it must be a variable error with the path name Program Files as I had something similar getting osmosis to run, but I can' figure out what or where?

 

I tried this osmosis

 

--read-xml file="C:\bulgaria.osm" --mapfile-writer file="C:\varna.map" bbox=42.185,27.063,43.463,28.103

 

before getting the error.

 

Any ideas are more than welcome as it's driving me mad.

 

Malky

_______________________________________________
osmosis-dev mailing list
osmosis-dev@...
http://lists.openstreetmap.org/listinfo/osmosis-dev
Brett Henderson | 5 Apr 00:51 2013

Osmosis 0.43 Released

Hi All,

I've just released Osmosis 0.43.
http://bretth.dev.openstreetmap.org/osmosis-build/osmosis-0.43-RELEASE.tgz
http://bretth.dev.openstreetmap.org/osmosis-build/osmosis-0.43-RELEASE.zip

From changes.txt:
  • Update command line help to point to the correct wiki location.
  • Remove idTrackerType arguments to filtering tasks, only the Dynamic option is now available.
  • Fix the --write-apidb task to use 64-bit ids.
  • Upgrade to version 1.4 of the Gradle build tool.
  • Enhance the build scripts to support publishing to Sonatype OSS Repository and Maven Central.
  • Rename all projects to use an "osmosis-" prefix.
  • Included a copy of the PBF OSM Binary project in the source tree, and eliminated the pre-compiled osmbin.jar.
  • Remove pbfmarshall project due to the same functionality being provided by the osm-binary project.
  • Removed the internal Ivy repository due to all dependencies now being available on Maven Central.
  • Rename --read-empty short name --re to --rem to avoid clash with --report-entity.
  • Rename --read-empty-change short name --rec to --remc for consistency with --read-empty.

A significant change in this release is that the artefacts have also been published to Maven Central.  This will make it easier for people to include Osmosis libraries in their own projects.  One relatively minor downside is that I can no longer perform the build from the Jenkins server because I am signing builds with my personal GPG key.  The build has been performed off my own local desktop.  I don't expect this to cause any noticeable changes.
http://search.maven.org/#search|ga|1|g%3A%22org.openstreetmap.osmosis%22

Let me know if you see any issues.

Brett

_______________________________________________
osmosis-dev mailing list
osmosis-dev@...
http://lists.openstreetmap.org/listinfo/osmosis-dev
Martin Schafran | 3 Apr 20:52 2013

duplicate key value violates unique constraint

 

hi,

 

i'm trying to import the apidb v06 and get this unique constraint error.

my db is postgresql 9.1 and i use osmosis 0.42.

 

the database is after running rake db:migrate empty except the migration table.

 

ERROR: duplicate key value violates unique constraint "current_nodes_pkey1"

Detail: Key (id)=(21402303) already exists.

 

 

I tried the import from two different xml files.

the first node entry in the file a.osm is 21402303 and is reported as violated constraint.

the first node entry in the file b.osm is 12 and is reported as violated constraint.

it seems as the first node has been already inserted some where else or the database is buggy.

 

current_nodes are populated from nodes with this statement in ApidbWriter:

"INSERT INTO current_nodes SELECT node_id, latitude, longitude, changeset_id, visible, timestamp, tile, version"

+ " FROM nodes WHERE node_id >= ? AND node_id < ?";

 

 

and in nodes there is only one entry where id=21402303,

so duplicates are impossible.

 

any ideas, what is going on?

 

martin

_______________________________________________
osmosis-dev mailing list
osmosis-dev@...
http://lists.openstreetmap.org/listinfo/osmosis-dev
Brett Henderson | 31 Mar 14:27 2013

OSM Binary (ie. PBF) Changes

Hi All,

I've just changed how the PBF support is provided in Osmosis.  Up until now there was a pre-compiled jar called osmpbf.jar checked into the Osmosis source tree.  It was compiled from Scott Crosby's github project here:
https://github.com/scrosby/OSM-binary

The problem with this is that it prevents me from publishing Osmosis to Maven Central because people trying to download Osmosis would be unable to use PBF without also getting a copy of that library.

To get around this I've repackaged the OSM-binary project to build as part of the Osmosis source tree.  The resultant jar is called osmosis-osm-binary, and it lives in a package called org.openstreetmap.osmosis.osmbinary.

I've tried to do this in a way that allows me to keep up to date with the upstream project.  I've forked the original repository on Github, and created an Osmosis branch:
https://github.com/brettch/OSM-binary/tree/osmosis

When changes are made to upstream, I should be able to merge master across to my osmosis branch.  The resultant tree is then checked directly into the Osmosis source tree.  On my local machine I actually have both git repositories acting on the same source files so it isn't too painful.  I have the Osmosis source checked out normally (ie. a .git directory at the root), and the osmosis-osm-binary project is also a clone of my forked OSM-binary project (ie. I have a .git directory in there as well).  So far it seems to work well enough.

If the original OSM-binary project ever gets published to Maven Central directly then I can stop these shenanigans and depend on it directly.

If anybody has any questions, issues, suggestions, etc let me know.

Brett

PS. I'm getting close to publishing to Maven Central now.  There are no major blockers left that I'm aware of.
_______________________________________________
osmosis-dev mailing list
osmosis-dev@...
http://lists.openstreetmap.org/listinfo/osmosis-dev
Brett Henderson | 30 Mar 12:41 2013

Publishing Osmosis to Maven Central

Hi All,

This may be of interest to some of you.  I've just begun the process of publishing Osmosis artefacts to Maven Central (ie. http://repo1.maven.org/maven2).

My current snapshot build is available here:
https://oss.sonatype.org/content/repositories/snapshots/org/openstreetmap/osmosis/

For those who are not familiar with Maven Central practices, it is not possible to publish directly to Maven Central itself.  The simplest way is to publish via the OSS Sonatype repository which then gets sync'd with Maven Central.

A few changes have been made to the Osmosis build to allow this to work (I'm still in the process of pushing these changes).  The most noticeable change is that most projects have been renamed to have an "osmosis-" prefix.  If you have an existing Eclipse workspace, you'll need to re-run "gradle eclipse" and re-import your projects.

The main blocker to publishing release artefacts is that I have two dependencies on libraries not available in Maven Central.  These are the scrosby PBF lib, and the BZip2 library which I built manually but which is based on Apache source code.  Both should be fixable by building and publishing them along with the rest of Osmosis, but I need to find time to do so.

Brett

_______________________________________________
osmosis-dev mailing list
osmosis-dev@...
http://lists.openstreetmap.org/listinfo/osmosis-dev
Daniel Kerkow | 21 Mar 13:34 2013
Picon

Osmosis 0.42 Installation on Ubuntu 12.04

Hi, 
I want to use the following python script that extracts the OSM boundaries and does some additional stuff with them. 


This script also calls osmosis, but needs version 0.42.
The Ubuntu repositories don't provide this  version.

How do I exactly install osmosis to be called from system, not from commandline?

Thanks in advance,
Daniel

_______________________________________________
osmosis-dev mailing list
osmosis-dev@...
http://lists.openstreetmap.org/listinfo/osmosis-dev
Nicolas Colomer | 12 Mar 10:28 2013

OSM entity processing order

Hi Osmosis community!

When I manipulate an OSM file (compressed or not) using Osmosis, can we assume that entities will systematically be processed in this order: 1.bound, 2.node, 3.way, 4.relation?

This seems logical since the OSM file format guarantees that "blocks come in this order" (see the OSM XML #File format wiki page).

In addition, I reach a post where Brett told:

> This is due to the way Osmosis processing works because it finishes processing nodes before it sees the ways.

I just want to make sure my impression is good :)

Thank you very much!

Best regards,
Nicolas
_______________________________________________
osmosis-dev mailing list
osmosis-dev@...
http://lists.openstreetmap.org/listinfo/osmosis-dev
Brett Henderson | 17 Feb 04:05 2013

Osmosis 0.42 Released

Hi All,

I've just released Osmosis 0.42.  It was easier to create a new release than to continue responding to limitations in 0.41 :-)
http://bretth.dev.openstreetmap.org/osmosis-build/osmosis-0.42.tgz
http://bretth.dev.openstreetmap.org/osmosis-build/osmosis-0.42.zip
http://dev.openstreetmap.de:23457/hudson/job/osmosis-release/8/

From changes.txt:
  • Fix PostgreSQL timestamp bugs in apidb replication logic.
  • Fix replication file merging boundary corrections.  Occurs when catching up after outages.
  • Replication logic correctly honours the max timestamp parameter.
  • Prevent replication file downloader from reading beyond maximum available replication interval.
  • Prevent replication file downloader from stalling if interval is too long.
  • Improve error reporting when an unknown global option is specified.
  • Disable automatic state.txt creation for --read-replication-interval.
  • Add --tag-transform plugin and task.
  • Reduce number of file handles consumed by file-based sorting.
  • Make the default id tracker Dynamic for --used-node and --used-way.
  • Use Gradle for the automated build scripts instead of Ant/Ivy.
  • Fix PostgreSQL ident authentication.
  • Remove obsolete debian build scripts.
  • Eliminate use of deprecated Spring SimpleJdbcTemplate.
  • Improve handling of invalid geometries in --pgsql-xxx tasks.
  • Default keepInvalidWays option on --pgsql-xxx tasks to true.
  • Enable keepInvalidWays functionality for --pgsql-xxx replication.
  • Fix pgsnapshot COPY load script to use ST_ prefix for all PostGIS functions.
    Let me know if you see any issues.

    Brett

    _______________________________________________
    osmosis-dev mailing list
    osmosis-dev@...
    http://lists.openstreetmap.org/listinfo/osmosis-dev
    
    Ilya Zverev | 6 Feb 10:05 2013
    Picon

    32-bit limit in IdTrackers

    Hi! As some of you have read 
    (http://lists.openstreetmap.org/pipermail/dev/2013-February/026495.html), 
    in three days node ids are expected to surpass 2147483647, and this 
    method
    
    https://github.com/openstreetmap/osmosis/blob/master/core/src/main/java/org/openstreetmap/osmosis/core/util/LongAsInt.java#L30 
    will throw an exception "Cannot represent " + value + " as an integer." 
    It is used in every IdTracker implementation, so id trackers will become 
    unusable.
    
    This will affect tag and area filters. Regional extracts that are made 
    with osmosis will break. There is a comment at the start of each 
    IdTracker class: "The current implementation only supports 31 bit 
    numbers, but will be enhanced if and when required." I guess, now is the 
    time. Can anybody fix that? There must be a reason why this hasn't done 
    sooner.
    
    IZ
    

    Gmane