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

2011-09-26 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: [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

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

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