I found some odd data in the tags on some sampled ways, including ways with the same id, tstamp, version with slightly different tag data (like space insertion or char(127) insertion) between the 2021 and 2022 data.

One example is way 129970575 with a tstamp "2021-07-28 18:10:02" version 9.
You notice the insertion of two chr(127) in the tag value for tiger:cfcc,A21 in the most recent data.

My older data from 12/2021 includes tags: "{HFCS,""Minor Arterial"",name,""Walton Way"",lanes,3,oneway,yes,highway,primary,tiger:cfcc,A21,tiger:county,""Richmond, GA"",tiger:reviewed,no,tiger:zip_left,30901,tiger:name_base,Walton,tiger:name_type,Way,tiger:zip_right,30901}"

But the newer data from 3/2022: "{HFCS,""Minor Arterial"",name,""Walton Way"",lanes,3,oneway,yes,highway,primary,tiger:cfcc,A21,tiger:county,""Richmond, GA"",tiger:reviewed,no,tiger:zip_left,30901,tiger:name_base,Walton,tiger:name_type,Way,tiger:zip_right,30901}"

asked 19 May, 14:32

gcapilot's gravatar image

gcapilot
41134
accept rate: 0%


I might be wrong, but there are definitely a couple of extra characters in front of A21 that don't copy/paste as spaces if you view the way history https://www.openstreetmap.org/way/129970575/history and as you post above the most recent edit was July 2021, so however you got the data in December must have removed them, and no longer does.

permanent link

answered 19 May, 16:40

EdLoach's gravatar image

EdLoach ♦
19.1k15154278
accept rate: 22%

Looking back in the history, the non-printing characters were added in version 8 in 2015. Like you said, if these weren't present in gcapilot's December 2021 data, that must have been a result of the tool-chain used to retrieve the data. The "correct" state of the data should include these characters (though they obviously shouldn't be in the database at all).

(19 May, 17:09) alester

Thanks very much! I need to learn how to view history in that way.

I used osmosis in both cases and it is entirely possible that those [DEL] characters got scrubbed somewhere along the line!

It looks like there were several instances of the chr(127) being inserted in various places in the current OSM ways that I'm using -

the following list of way-id and versions all have this chr(127) character embeded :

382363986 4 15025131 14 20143848 6 129970575 9 14664038 11 52109740 6 356378230 7 374035295 11 420904921 5 611000788 3 562474719 2 699814543 2 883155980 2 858385263 2 776387551 2 883155981 1 894524157 2 12289973 4 11466281 7 11466289 7 5584156 9

permanent link

answered 19 May, 17:10

gcapilot's gravatar image

gcapilot
41134
accept rate: 0%

edited 19 May, 18:49

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×225
×184
×1

question asked: 19 May, 14:32

question was seen: 276 times

last updated: 20 May, 14:53

powered by OSQA