[OSM-dev] ODbL full history planet

[Stephan Knauss]

Hello Jochen,

thank you for this explanation. Explains what I'm seeing with an osh.pbf

On 30.10.2012 10:46, Jochen Topf wrote:
> PBF files don't have a way of storing non-existing coordinates. When PBF was
> invented this couldn't happen and nobody ever thought of adding it.

could specifying MAXINT as the value for non-exisiting lat/lon values in 
a full history pbf be a solution?

I still have no stock tooling for reading either the xml file and grep 
for a node nor pbf tools to inspect how the version history of a 
redacted node looks like.
So unfortunately can't simply try to see what's happening.

> Osmium uses MAXINT (boost::integer_traits<int32_t>::const_max) to mark invalid
> positions internally. This will show up as 214.7483647 externally if whatever
> code you have doesn't check the result of the defined() method.

I used your osmium_convert example to convert the osh.xml into osh.pbf. 
As you said, it does not include any checks for defined(), so it all 
ends up in PBF.

I did not see anything special about lat. Both fields would be MAXINT, 
right?
Maybe it's limited in osmconvert. Can't follow that code :(


O:\>osmconvert.exe --out-statistics history_2012-10-13_13_35.osh.pbf
timestamp min: 2005-04-18T14:12:45Z
timestamp max: 2012-10-13T11:35:31Z
lon min: -,.),(-*,(
lon max: 214.7483647
lat min: -90.0000000
lat max: 90.0000000
nodes: 2325354854
ways: 273053641
relations: 6210920
node id min: 1
node id max: 1962486877
way id min: 35
way id max: 185598826
relation id min: 2
relation id max: 2474614
keyval pairs max: 7838
keyval pairs max object: way 17441262
noderefs max: 49189
noderefs max object: way 29310085
relrefs max: 69643
relrefs max object: relation 82682


Stephan