4 ms·
I've been dabbling with GIS data for many years without being even remotely aware of this issue. I now realize how much of a sandcastle GIS data is. So, thanks
by jillesvangurp 7y ago
I've been dabbling with GIS data for many years without being even remotely aware of this issue. I now realize how much of a sandcastle GIS data is. So, thanks for posting this because I learned something.
There is a lot of data out there that is effectively user generated. What this means is that someone with a phone goes to a some place and than posts some content (photo, tweet, restaurant check in, etc) with some kind of coordinate. All this stuff ends up in databases. This stuff was never very accurate. If you collect POI data from different sources about the same POI, the coordinates are going to vary by tens of meters. Worse if users manually enter the coordinates because people lie. Also, real world places are not points but have geometry, sometimes that can be tens to hundred of meters. E.g. the coordinate of the Louvre in Paris is meaningless because the place is huge. Also the whole of open street maps is basically many different users contributing what they think should be the coordinates of things.
Proximity is a good signal when de-duplicating POIs but not reliable by itself. E.g. in many Japanese cities, some bars are on the n-th floor of some sky scraper and there may be dozens of restaurants and bars in the same building. Also, they close and re-open as something new regularly; so there's a lot of stale GEO data out there like reviews of restaurants that no longer exist or that just opened and get tagged to the wrong POI, buildings that got demolished, or new buildings and streets that got constructed recently in what formerly was a field.
So, GIS data is messy and the coordinate system is helpful for getting close enough that you can figure it out once you are near enough to see the signs but generally not very precise.
But then, there are more elaborate things like indoor maps that are geo-referenced; or 3D building models that are shown on a map. These things are usually modeled separately and then manually or automatically aligned with a map. Most data sets specifying coordinates have no notion of anything else than a pair of doubles that are generally referred to as the WGS 84 coordinates. This includes open street maps; which mostly consists of user generated data by users with no clue about this issue using inaccurate gps signals and either some local knowledge about stuff is relative to other stuff in OSM or some satellite imagery.
So, the implication of this article is that most of that data is only valid in the context of whatever it was geo-referenced to. Which, in most cases is simply unknown since it is typically not recorded in datasets or even known by whoever records the data.
This explains a lot of things about some stuff I've been seeing in 3D scenery for flight simulators like x-plane where if you have e.g. some satellite imagery and 3D objects for real world buildings, airports, etc. it is quite common for them to be slightly misaligned since the data comes from lots of different sources, all lacking meta information about what their coordinate system actually is supposed to be, that are combined automatically.