You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: Malmis [Submitted to the original trac issue database at 1.33pm, Friday, 24th February 2012]
I have some problems with osm files that misses version and timestamp attributes after converting shape files to osm files with ogr2osm.
osmosis asks if the file is a 0.5 file, but it's a 0.6 file.
"org.openstreetmap.osmosis.core.OsmosisRuntimeException: Way -128 does not have a version attribute as OSM 0.6 are required to have. Is this a 0.5 file?"
The text was updated successfully, but these errors were encountered:
Author: JoshD [Added to the original trac issue at 6.58pm, Friday, 24th February 2012]
See #1683, #2620, and [http://lists.openstreetmap.org/pipermail/osmosis-dev/2010-August/000707.html]. I've also used osmosis after ogr2osm, by using sed to add then strip fake metadata. I believe it would be useful to allow osmosis to process streams without metadata, however it should be enabled with a special flag like allowMissingMetadata.
Author: Harry Wood [Added to the original trac issue at 1.55am, Friday, 22nd February 2013]
Just had this error message because OverpassAPI also gives results without a version attribute. I guess these day there's probably more examples of software using/creating .osm formatted files, but without version attributes. Not just JOSM.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Reporter: Malmis
[Submitted to the original trac issue database at 1.33pm, Friday, 24th February 2012]
I have some problems with osm files that misses version and timestamp attributes after converting shape files to osm files with ogr2osm.
osmosis asks if the file is a 0.5 file, but it's a 0.6 file.
"org.openstreetmap.osmosis.core.OsmosisRuntimeException: Way -128 does not have a version attribute as OSM 0.6 are required to have. Is this a 0.5 file?"
The text was updated successfully, but these errors were encountered: