QuadBuckets also happen to implement Collection<Node>. So, we can
just plug it in for Collection like in the DataSet class.
---
core-dave/src/org/openstreetmap/josm/data/osm/DataSet.java | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff -puN src/org/openstreetmap/josm/data/osm/DataSet.java~QuadBuckets-as-node-storage src/org/openstreetmap/josm/data/osm/DataSet.java
a
|
b
|
import java.util.List;
|
16 | 16 | import java.util.Set; |
17 | 17 | |
18 | 18 | import org.openstreetmap.josm.data.SelectionChangedListener; |
| 19 | import org.openstreetmap.josm.data.osm.QuadBuckets; |
19 | 20 | |
20 | 21 | /** |
21 | 22 | * DataSet is the data behind the application. It can consists of only a few points up to the whole |
… |
… |
public class DataSet implements Cloneabl
|
37 | 38 | * All nodes goes here, even when included in other data (ways etc). This enables the instant |
38 | 39 | * conversion of the whole DataSet by iterating over this data structure. |
39 | 40 | */ |
40 | | public Collection<Node> nodes = new LinkedList<Node>(); |
| 41 | public Collection<Node> nodes = new QuadBuckets(); |
41 | 42 | |
42 | 43 | /** |
43 | 44 | * All ways (Streets etc.) in the DataSet. |