[OSM-dev] java.lang.NumberFormatException: null error with osmosis 0.30.3
mdeen at xs4all.nl
Wed Apr 29 18:43:36 BST 2009
Karl Newman wrote:
> On Wed, Apr 29, 2009 at 9:54 AM, Maarten Deen <mdeen at xs4all.nl
> <mailto:mdeen at xs4all.nl>> wrote:
> Ok. I downloaded the node from the api and I see the difference. I
> got this from
> one of the xapi servers. Guess they're not yet fully 0.6 compliant then.
> Or is there a way of getting osmosis to disregard the fact that
> there is no
> version attribute?
> Well, I know there's currently no way to make Osmosis ignore a missing
> version attribute, but it's certainly possible to program that
> functionality as an option. It could just create a synthetic version
> number (0?) for use in the rest of the pipeline. This would likely
> prevent it from being uploaded (without further manipulation, anyway).
> I'll leave it to others to debate the wisdom of providing such an option
> for non-compliant files, though.
I've found that osmosis will still read a (xapi) 0.6 file in 0.5 mode. It does
complain that the version number does not match, but it reads it fine. So no
More information about the dev