| <g>
|
|
Grin uses a U-blox ZED-F9P and is willing to answer questions on it from OSM users.
|
|
|
Grin uses a Xiaomi MI10T and is willing to answer questions on it from OSM users.
|
|
|
Grin uses a Xiaomi MI9 and is willing to answer questions on it from OSM users.
|
|
This user submits data to OpenStreetMap under the name
grin.
|
|
Grin submits data to OpenStreetMap using JOSM.
|
|
Grin submits data to OpenStreetMap using Potlatch.
|
|
Grin submits data to OpenStreetMap using iD.
|
|
Grin has mapped in Nepal.
|
|
Some details in english or hungarian Wikipedia. Guess what, I'm Hungarian.
Maybe later I'll repeat some of it here. ;-)
I edit OSM since May, 2008.
Equipment
I am a lucky owner of an uBlox F9P RTK board, which is an extremely precise GPS with a multichannel external antenna resulting 10-50 centimeters accuracy in lucky measurements (within 100km to a fixed base station) and 1-3 meters in not so lucky environments. This results a significantly different survey method since the GPS unit gives a precise signal usually without the need to offset it to a known-to-good point; it marks the same point with the same position even after hours or days. It requires a powerbank and a phone with internet connection (for real-time data; technically I could record the raw data and use RTKLIB later) and the app on the phone shares the location with other programs, like OsmAnd.
As one measurement is no measurement I usually use several Android based device for parallel track recording, mainly a Xiaomi MI10T and a Xiaomi Mi9. Both phones are able to see Russian (GLONASS, ГЛОНАСС) and Chienese (BDS, 北斗衛星導航系統) satellites, along with GALILEO, and they are dual-channel for added reliability.
I mainly use OsmAnd's recording, rarely Locus.
I postprocess using (gps)prune, which helps to create both geolocated imagery (correlating known position with known image) and compressed/simplified tracks (which get uploaded).
Finally JOSM for everything mappingy.
Imagery is created usually either with the phone (later model phones have a fairly reliable compass which is a blessing when using the images) at hand or with a Panasonic DMC-GX1 which gets synched to a key image with known position.
Lately I got a grab on an "action camera" (SJ4000 clone) -- then it self-destructed after a year or so, and I was lazy to replace the non-replaceable battery; but got a Yi Cam which actually have a pretty nice 2k imagery and replaceable battery [and a pretty good image stabiliser, mind you; but it have hard time with fast brighness changes] and realised that JOSM have no working video mapping plugin. Or anyone else. Damn. So I usually either set it to timelapse aka. image every second or cut the movie to 1s resolution imagery and geocorrelate them with tracks -- JOSM geocoded imagery plugin works well (and in the recent years there was only negative progress on video plugin, so no luck for movies yet).
Retired tools
- Garmin eTrex Vista (gps)
- OnePlus 1 (phone)
- Samsung S7 (phone)
- Desire HD (phone)
- Motorola Atrix (phone)
- Samsung Galaxy Tab (tablet)
- Canon A720IS (cam)
- SJ4000 (cam)
- Holux M-1000C (gps logger)
Move along, citizen.
| Bing |
bing |
mapbox |
digitalglobe
|
|
|
|
|
|
Hungary, big boundary: (bbox=15.6,45.5,23.5,48.9); smaller: (bbox=16.1139,45.7371,22.8975,48.5853)
