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
Copy file name to clipboardexpand all lines: doc/notes.txt
+29-1
Original file line number
Diff line number
Diff line change
@@ -179,4 +179,32 @@ Show only ways (from a given list of ways) which are part of a bicycle route
179
179
way for our task is to select only the parent ways for all nodes from the input
180
180
set with *way(bn*);
181
181
182
-
182
+
Thu 10 Jul 16:04:02 CEST 2014 (and before) -MM
183
+
==============================================
184
+
Problems fixed:
185
+
• Ways without node-changes have no spatial information in diff file, so get removed by crop
186
+
· pick a node for each way missing spatial information
187
+
· download them via overpass in bulk
188
+
· there was need to limit the download to only 1000 nodes at once, and merge the results later
189
+
· merge them into osm-file before crop
190
+
191
+
• filter out non-highway ways with osmosis instead of overpass → reduces load on overpass server
192
+
· allow only highway types with --tag-filter that are allowed for bicyclists
193
+
194
+
• added handling of deleted ways: osmosis removes deleted items when converting osc→osm
195
+
· regex <deleted> → <modified> in osc after simplify change → fixed it.
196
+
197
+
Testcases:
198
+
• ./regional-diff.py -f minutely-796.osc.gz
199
+
this includes changeset http://www.openstreetmap.org/api/0.6/changeset/24005065 from user species
200
+
there should be 89 ways and 2 relations (all from this changeset)
201
+
• ./regional-diff.py -f scripts/637.osc.gz
202
+
there should be 5 ways and 2 relations
203
+
204
+
Notes for the future :
205
+
206
+
• overpass API does NOT return deleted nodes.
207
+
· for ways without spatial information, some nodes (if deleted meanwhile on the server) will not come back on overpass quere → way gets removed (wrongly) on crop
208
+
But: this should happen only (rareley) on fresh changesets.
209
+
210
+
• if a relation modified is only sorted or tag-changed without having modified members in the changesets, this is not reported.
0 commit comments