I thought I’d ask, this time, instead of doing my usual thrash around and come up with some totally unworkable way to do what I want…
I ride a dual-sport motorcycle (on/off road) with a GPS. I’ve recently switched GPS units and now run an Android device instead of Garmin. With the Garmin, I built my own custom maps that do things like take my regular routes and make them very obvious… stuff like making them toll expressways instead of the dirt paths they really are… anything to make them really stand out on a little map screen while I’m riding fast. I also have a habit of tracing out potential riding routes via Google Earth or any other map-source I can find. In other words, not stuff that should ever make it into the OSM project. I’ve got a pretty decent workflow with Garmin… mapedit ect…
Now, with the Android-based GPS, it looks like my custom Garmin-format maps are useless and I have to start over. It also looks like I’m going to be dealing with tile-based maps instead of vector. So far in my research it looks like it will be something like: JOSM → Maperitive → MOBAC → Orux on the GPS. I’ve tested and can get data all the way through this chain.
What I’m wondering is:
- is there a better way?
if not…
- how can I break up the data in JOSM such that I can actually edit it without the system bogging down? I can cover a lot of ground on my bike and doing things like downloading everything around a gpx track adds up pretty quick (it didn’t help that the first track I tested happened to have the route to a local lake AND my flight to Japan – oops). Are there bite-sized vector files of OSM data? …something like the Garmin img files?
I really like OSM and the data is getting great. I think I can add a lot to it as I get way, way out there, down some pretty obscure tracks. But, I need a way to keep my hacks separate from the clean data.
Any suggestions?
David...