osm.wiki/DE:OSM_Map_On_Garmin osm.wiki/DE:Garmin

Die English Versionen haben mehr info. War das so schwer zu finden ?

Assisted GPS (aGPS) only helps to get the initial GPS position (“gps fix”) faster. It doesn’t improve accuracy, and having more mobile cells in the area doesn’t improve thins (as long as you have data coverage, you can use aGPS). Mobile phones generally don’t have great GPS quality, and narrow streets with high buildings are a challenge for any GPS.

I recommend one of the Garmin trekking GPS. The newest eTrex even support Glonass (an additional set of available satellites, which improves fix time and “deep valey” accuracy). They’re not as cheap as single-purpose trackers like the one Robert suggests, but you can view your osm maps on it, and they’ll last you a decade as they’re very sturdy. Some models even have a camera, but the price becomes hard to justify.

Plenty of work ahead of ye, but at least it looks well prepared. Good luck :)

Good for you :) Mapping on a bike is probably the most pleasurable way to do so. It gives you an extra incentive to go out, and takes you places you’ve never been to.

An of course countryside mapping is as valuable as in the city. A holey map is a map that people won’t trust, and on the contrary if people see a well-mapped remote area, they’ll get a better opinion of OSM. We need more rural mappers, sadly technology-inclined people who are likely to map are also likely to live in cities.

Simply learn to use the cadastre, there’s a josm plugin that makes things reasonably easy.

If that still feels too complicated, go ahead and map the usual way. Cadastre-import is not a fully-automated thing. When somebody eventually use the cadastre to map an area, he needs to account for already-mapped elements anyway.

GPs mapping isn’t a bad thing, really. I’ve mapped a lot of neighbourhoods in my area; when satellite imagery became available 1-2 years later I had another look and tweaked my original work, but it didn’t make a big difference.

Besides:

• You need to go on-site anyway, to survey street names and all the many, many details that are not visible on imagery.
• Having a lot of traces available in a area is very important to make sure that the imagery is alingned correctly before tracing from it.
• Imagery quality varys greatly, and since your area wasn’t deemed worthy of detailed imagery yet, chances are it won’t get the best-of-breed imagery when it eventually gets something.

You don’t need fancy software to gather traces, they are all provide the same basic needed functionality. Add some device to take a photo/video/audio, and you’re all set.

Osmi has a redaction bot layer that helps with remapping. http://rebuild.poole.ch/ is also usefull.

There’ll never be an automatic “redaction undo” for users who finally accept : conflicts are likely, and it’d be a lot of coding work for a rare/low_impact event. If an undo is ever performed, it’ll probably be a manual, case-by-case affair.

(Entshuldingung fur das English, ich bin zu jetz müde fur Deutch)

The “Remapping” wiki page was fairly clear that any object created by a non-agreer needed to be recreated from scratch. OSMI would have shown you that the way was still unclean.

The bot is actually doing its best to keep as much information as possible, but in the case of version-1-unclean data, there isn’t much choice.

I can imagine how frustrating it is that your remaping work was thrown away, but there’s not much else the bot could do. Again, checking the available documentation and tools would have shown that the remapping you did wasn’t sufficient.

At least you’ve already done the surveying and thinking for those areas; readding them should be less work than earlyer ?

Wenn du sicher bist, dass diese Strassen ODBL-clean waren, solltest du sofort osm-dev (Irc oder Email) kontactieren, so dass sie die fehlern corrigieren können. Möglisherweise waren diese Strassen eigentlich nich ODBL-clean. Was sagte OSMI ?

There’s going to be plenty more like this to take care of. It’s a pain, but a necessary one and we’ll be glad to be on the other side.

Once the bot has finished processing the area, go ahead and “remap” the broken bits as well as you can.

Remember that nearly all trekking devices have an “average waypoint” feature that will wait for a bit until it’s sure that the measured position is correct. And you can take extra measurements a few hours or days appart.

It may not be as good as those overly-expensive professional GPS, but it’s more than enough for mapping in most cases. You won’t trace a road with it, but it’s perfect for alingning imagery.

Si tu as lu le wiki et que tu sèche encore, il va falloir poser des questions plus précises sur ce qui te pose problème. Je te conseille d’aller sur le channel #osm-fr d’IRC, tu y trouvera des utilisateurs de cadastre qui sauront te guider.

“Very quiet” ? There’s 7000-8000 distinct contributors uploading one or more changesets every week. A good chunk of those are in the UK. It’s more likely that there are too many edits for yours to be commented on, rather than nobody being interested in your area :)

Bloging is only one way to get chatty on OSM. There are a few others, mainly IRC and mailing lists.

Good work linking the Monmouth Wikipedia project with OSM. Keep it up :)

I don’t really see any problem here. Everybody has to pay some bills, and if a large proportion of OSMF member have their own company, it’s probably because the kind of people who volunteer for a foundation is also the kind of people who would start their company.

Does it cause a conflict of interest ? Yes and no : if their business is OSM-based, they’ll want OSM to trive, just like the rest of the community. Commercial use of OSM is a perfectly valid use-case (if not, we’d have a different licence). It’s even an important use-case, because commercial use brings sponsoring and visibility.

A conflic of interest would arrise if somebody pushed for something that’s detrimental to the rest of the community. If you spot one, then certainly go ahead and denounce it. But I dont see any here.

DB bloat is always something to keep in mind (throwing more hardware at it only works to a point), and Frederik Ramm’s comments about buildings is not about deleting it, but about thinking of ways to deal with it (also, it is not an example of DB bloat).

I have no idea what you are trying to say about the license bot (that it is progressing slowly ? we know that) or about http://openstreetmapdata.com/ (he shouldn’t have a donate button ?).

Nice, it’s going to be usefull.

One false-positive I’m seeing all around though: in a residential area or commercial area, it is common (and correct) to have the street named the same as the area. There’s also the case of “name=Foobar House” which is arguably both the name of the building and the area around it.

Not sure how to remove those false-positive without creating false-negatives, though.

C’est le genre d’info qui n’est pas affiché sur une carte, mais qui est utilisé par les moteurs de routage.

En plus des tags max*, je suggèrerais aussi l’utilisation de lanes, car un “lanes=1” est une bonne indication que cette route est déconseillée pour un camion.

Siehe auch wheelmap, eine Karte die speziel für Behinderte geeignet ist (Toiletten, Restauranten, etc).

Fixing OSM data is needed and important (in fact it’s the whole point of being an OSM contributor), but it sounds like your over-enthusiasm causes two problems :

1. You’re going too fast when deciding wether something is an error, and make generalizations when you should proceed on a case by case basis. For example, is_in is valid and good in many places, and the S/N in south america deserves surveying/imagery (as opposed to anthing automatic) to be fixed properly.

2. You try to bypass the community advice in order to go faster. It’s true that discussion slows things down, but it’s necessary to avoid big mistakes.

Dont take this as a “me VS the others” chalenge. We’re all working together to improve the map (and we need all the manpower we can get). The temporary block you got is just a warning that you’re doing it wrong, and risk making as much of a mess as you intended to fix. Learn from that warning :)

Sorry for answer in English, my german is lacking :

Why not simply use your browser’s “view -> zoom” feature (with “zoom text only = false”) ? I use this regularly (even on the same website/screen, depending on tiredness and ambiant light), there’s no way any given website’s pre-set size coult suit me every time anyway.

Bienvenu au club, amuse-toi bien.