A question a friend emailed me with recently: I was visiting the Chelsea Physic Gardens today, doing the tourist thing, and figured a bit of mapping might be in order... until the GPS lock put me consistently at least ten metres off point, in various directions. Given that the place is surrounded on three sides by medium rise blocks of flats, ten foot walls, and myriad trees, is it likely to be a forelorn hope to get any decent fixed lock signal there? Oh, and forget trying to map it manually, the place is an absolute nightmare to quarter on paper, GPS tracks are the only way I can see it being done with any reliability! asked 03 Sep '15, 11:54 Harry Wood |
Different people will give you different advice and mapping techniques for this kind of thing. The way I would do it is basically walk around the park in some logical order, taking a load of photos, then when I get home, map the basic layout of the park based entirely on bing imagery. We can see the paths etc in the imagery but of course, surveying is still important. I'd use my photos to add details and typology of things which you would not be able to see from the imagery, and to double check things which might be out of date in the imagery. ...and normally I wouldn't bother to use GPS for anything at all (apart from placing the photos in vaguely the right place while I'm working in JOSM. Now some might say this is cheating, but it's more accurate than GPS, as I will explain. There is always the awkward question of imagery "offset". I think some OSM mappers are far too ready to assume that their GPS trace is accurate and everything else is wrong. As a result there's some patches of data in London with different offsets, as people have attempted to correct the imagery. My usual approach to these is to assume that previous mappers have known what they were doing with offsets. So I shift my imagery layer in JOSM to match the existing OSM data. Where that is not possible due to two competing offsets, I... try to pick an offset which is sort of half way between. You can see my vague hand-wavy demonstration of this at the beginning of this video But it is frustrating because (although I generally assume it) I actually consider it highly unlikely that prior mappers did know what they were doing with offsets. The imagery does have an incorrect offset from reality, and this varies from place to place in London, but a single GPS trace is definitely not sufficient to establish what the offset is (particularly if there's tall buildings around). To create a "ground reference point" is a lot of effort. You need to pick a clearly visible very precise point on the ground or something like a fountain in the middle of the park to walk around, and I would say you need to take at least five different GPS traces on different days to zero in on a correct offset. I went through this process in the park outside my house. I had about seven different traces, but discarded two of them as being wildly wrong (must have just got a bad GPS fix that day for some reason), the remaining traces all seemed to agree within about a metre or two. The little loops as I walked around a statue in the middle of the park, were all looping in almost the same place. And taking the average positioning of those as ground truth, I established the exact offset of the bing imagery outside my house. ...A lot of effort. Which is why I consider it highly unlikely that mappers have gone to that level of hassle in many other parts of London. Most awkward offsets you see in the data in London, will be most likely somebody placing too much trust in a single GPS trace. The most correct thing we can realistically do, would actually be to abandon such efforts and shift all data to align with bing imagery, unless we have some sort of widely publicised procedure and a push to create lots of ground reference points. But it would be a lot of hassle. But there's the "correct" offset, and then there's the best way to treat offsets in order to avoid annoying other mappers :-) answered 03 Sep '15, 11:55 Harry Wood |
Also a very relevant question in places not covered by WAAS / EGNOS - GPS traces can be substantially further out there.