Re: [osmosis-dev] Problem creating pbf data with osmosis 0.39

2011-09-21 Thread Igor Podolskiy
Hi Michael, On 21.09.2011 00:04, Igor Podolskiy wrote: On 20.09.2011 22:50, Michael Prinzing wrote: Now, there is an empty bounding box, and the timestamps are far in the past (looks like an integer of -1 converted to a timestamp to me). [...] I could reproduce the empty bounding box problem,

[OSM-dev] OSM XML declaration, JOSM, Osmosis et al.

2011-09-21 Thread Roland Olbricht
Hello everybody, A question to all maintainers of OSM XML processing software: What combinations of root tag attributes do you expect for XML with and without meta data? If I deliver from Overpass API to JOSM the XML data with meta data and with a plain osm tag, JOSM crashes with a

Re: [OSM-dev] Osmium - Corruption when writing PBF

2011-09-21 Thread Jochen Topf
Hi! You already asked this on Sep 1, and I told you then that we might be able to help you if you post your code. We are not magicians you know! Jochen On Wed, Sep 21, 2011 at 12:57:15AM -0400, Pris Matic wrote: Date: Wed, 21 Sep 2011 00:57:15 -0400 From: Pris Matic

Re: [OSM-dev] Osmium - Corruption when writing PBF

2011-09-21 Thread Pris Matic
Sorry! I totally forgot I had already asked this :) http://pastebin.com/GjtgqzkP - osmium handler header http://pastebin.com/75JUT824 - osmium handler source http://pastebin.com/bSpGj0Ez - main.cpp It should be possible to just run this on any map file as long as you set the bounding box

Re: [OSM-dev] OSM XML declaration, JOSM, Osmosis et al.

2011-09-21 Thread Serge Wroclawski
On Wed, Sep 21, 2011 at 2:12 AM, Roland Olbricht roland.olbri...@gmx.de wrote: Hello everybody, Hi. Please don't cross post. If I deliver from Overpass API to JOSM the XML data with meta data and with a plain osm tag, JOSM crashes with a NullPointerException on the first version attribute.

Re: [OSM-dev] OSM XML declaration, JOSM, Osmosis et al.

2011-09-21 Thread Erik Johansson
On Wed, Sep 21, 2011 at 8:12 AM, Roland Olbricht roland.olbri...@gmx.de wrote: JOSM and Osmosis both complain about the absence of version attributes on the individual OSM elements for data without meta data. Having OSM data with or without meta data is really a useful feature. The same data

Re: [OSM-dev] OSM XML declaration, JOSM, Osmosis et al.

2011-09-21 Thread Frederik Ramm
Hi, On 09/21/11 13:13, Erik Johansson wrote: A bit off topic: I just tried overpass and was surprised that the default seems to be to strip the version and date, I'm not so keen on that feature. Thinking about this, I like the stripping of the version number. We're having a lot of trouble

Re: [OSM-dev] OSM XML declaration, JOSM, Osmosis et al.

2011-09-21 Thread Serge Wroclawski
On Wed, Sep 21, 2011 at 7:18 AM, Frederik Ramm frede...@remote.org wrote: Not serving the version number on XAPI, Overpass and others would send a clear signal that these services are not to be used for editing. Doing so also precludes merging results with any existing OSM database though.

Re: [OSM-dev] OSM XML declaration, JOSM, Osmosis et al.

2011-09-21 Thread Frederik Ramm
Hi, On 09/21/11 14:01, Serge Wroclawski wrote: Doing so also precludes merging results with any existing OSM database though. You can't have an extract then update via a service which strips version numbers. If you need versions in your extract. If your extract is supposed to contain only

[OSM-dev] Version numbers in downstream data

2011-09-21 Thread Serge Wroclawski
I'm concerned that there's a view that we should be stripping out data from these resources in order for them to be crippled in one way or another as per another thread. I'm surprised at Frederik's view that this is a good idea. Will Geofabrik start stripping out this information from the

Re: [OSM-dev] OSM XML declaration, JOSM, Osmosis et al.

2011-09-21 Thread Richard Fairhurst
Serge Wroclawski wrote: OSM objects are identified by three identifiers: Object Type, ID and Version Those three identifiers are necessary when talking about an OSM object. Absence of one of them means the data isn't valid. The type and ID are obvious, but the version number appears to be

Re: [OSM-dev] OSM XML declaration, JOSM, Osmosis et al.

2011-09-21 Thread Paul Norman
-Original Message- From: Frederik Ramm [mailto:frede...@remote.org] Thinking about this, I like the stripping of the version number. We're having a lot of trouble with people doing mass edits by using XAPI etc. to download e.g. everything with name=McDonalds world-wide and

[OSM-dev] Fwd: [Talk-kosovo] I need help

2011-09-21 Thread Mike Dupont
I think this might be the right list for this. mike -- Forwarded message -- From: Besfort Guri besig...@gmail.com Date: Wed, Sep 21, 2011 at 1:07 PM Subject: [Talk-kosovo] I need help To: talk-kos...@openstreetmap.org, t...@openstreetmap.org Hi I am trying to see the reverse geo

[OSM-dev] US data source for offline geocoding

2011-09-21 Thread Michael Katz
A requirement of my application is to be able to do geocoding (street address to lon/lat) and reverse geocoding (lon/lat to nearby street address) without an internet connection, mainly for the United States. I am trying to find the best source of data for this. I can use the 2010 TIGER files,

Re: [OSM-dev] OSM XML declaration, JOSM, Osmosis et al.

2011-09-21 Thread Toby Murray
On Wed, Sep 21, 2011 at 1:44 PM, Paul Norman penor...@mac.com wrote: -Original Message- From: Frederik Ramm [mailto:frede...@remote.org] Thinking about this, I like the stripping of the version number. We're having a lot of trouble with people doing mass edits by using XAPI etc. to

Re: [OSM-dev] OSM XML declaration, JOSM, Osmosis et al.

2011-09-21 Thread Roland Olbricht
Is Overpass so geared for tools that don't care about uid/date/version/visible etc? Actually, yes. Note that these tools include map rendering, routing, location based search and probably every other tool that consumes the data. The data model is: the state of the Planet database (or an

Re: [josm-dev] pixel per degree

2011-09-21 Thread Paul Hartmann
On 09/19/2011 05:33 PM, Dirk Stöcker wrote: On Mon, 19 Sep 2011, Paul Hartmann wrote: Why is it called pixelPerDegree in ImageryInfo? Apparently, the value is in pixels per unit in projected space (pixelPerEastNorth). Which is nonsense as well. It should not be relative to projected

Re: [josm-dev] pixel per degree

2011-09-21 Thread Dirk Stöcker
On Wed, 21 Sep 2011, Paul Hartmann wrote: Why is it called pixelPerDegree in ImageryInfo? Apparently, the value is in pixels per unit in projected space (pixelPerEastNorth). Which is nonsense as well. It should not be relative to projected coordinates. What is the alternative? I don't