source: subversion/misc/64bit_testdata/README @ 29543

Last change on this file since 29543 was 29136, checked in by frederik, 7 years ago

+bbox thanks mazdermind

File size: 2.0 KB
Line 
1
2--------------------------------
3DO NOT UPLOAD THESE FILES TO OSM
4--------------------------------
5
6Test data for 64bit node IDs
7
8This directory contains three sets of files which you can use to
9test-run the OSM software you are using and see if it supports IDs
10larger than the signed 32bit integer range (2^31-1).
11
12It is expected that OSM node IDs will break this barrier in early
132013.
14
15The test data is a small sample from OSM data and depicts the area
16around V. C. Bird International Airport on the Caribbean island of
17Antigua, and covers the following bounding box:
18
19minlon=-61.8114 minlat=17.1255 maxlon=-61.7733 maxlat=17.1542
20
21
22The files are:
23
24base-X.osm
25base-X.osm.pbf
26   - basic OSM data for the sample area.
27
28diff-X.osc
29   - a diff that adds the Stanford Cricket Ground to the data.
30
31full-X.osm
32full-X.osm.pbf
33   - sample area including the Stanford Cricket Ground.
34
35There are three sets of files with different "X":
36
37X = s32
38   - signed 32bit id range; these files should work correctly
39   with all existing software. Contains some nodes in the 1...1000
40   range and some in the 2**31-2500 range.
41
42X = u32
43   - unsigned 32bit id range; if your software works with these
44   then you're probably good for another year. Contains some nodes
45   in the 1...1000 range and some in the 2**31...2**31+1000 range
46   so that they would wrap to 1...1000 if you were limited to 2**31.
47
48X = 64
49   - 64bit id range; if your software works with these then you
50   you're ok for quite a long time to come. Contains some nodes
51   in the 1...1000 range and some in the 2**32...2**32+1000 range
52   so that they would wrap to 1...1000 if you were limited to 2**32.
53
54There is also a file called broken.osm which depicts what happens
55if you do indeed have an integer overflow; it contains lots of nodes
56twice. There's also a "correct.png" showing how the data looks like
57in JOSM, and "broken.png" which is something you'll see if you have
58an integer overflow.
59
60--------------------------------
61DO NOT UPLOAD THESE FILES TO OSM
62--------------------------------
Note: See TracBrowser for help on using the repository browser.