A GPS trace demonstrates that there is a path there. A satellite image may no show a path - e.g. covered by trees, shadowed by buildings.

A GPS trace may demonstrate that the satellite image has offsets .. and those offsets can vary in as little as 100 meters.

However, one GPS trace is an indication, but better are many GPS traces of the same path! I have single GPS traces that are ‘out’ by some 10 meters. How do I ‘know’ that? By having many GPS traces of the same path. So if you want accuracy .. don’t rely on one GPS trace, it is better than nothing but it could have its own error.

The Australian map does not appear to be up to date. For instance I entered some road names some weeks ago that don’t appear with mapsme the downloaded today, they do under locus and on the OSM editmap. Around -33.81016 151.07847.

The ‘mechanical’ rules/guide would be complied with if for each and every replacement you confirmed the replacement .. this can be done with some text editors, just don’t select the automatically replace everything button …

This is ‘good’ for abbreviations like Rd to Road, St to Street etc.

Quibble: British English … colour not color. :)

landuse=forest to me means there will be wood harvesting from this area.

nature=wood … means the area has plants of such a size that wood is present. There is an area in Australia called the Nullabor .. meaning no trees. You can find wood there for a camp fire but there are no large trees. So I’d still mark it natural=wood. nature=wood means there may not be wood harvesting in the area.

Origin of wooded vegetation … err no. Your thinking or the way it was planted rather that if it is native to the area, native to the country or non native. And I’d make the tag broader without loosing the essential information For example; planting=natural, manual, automated … I am certain there are many varieties of the planting method. by seed, tube stock, pot … for example.

Origin of vegetation could be taken as native (to the area, to the country) or non native. Oh and there are the cloned, hybrid, grafted… if you want to go that far. Again this could be applied to things like orchards .. not just forests/woods.

Managed… National Parks are managed .. and some of it is natural=wood. But the management is quite different from a tree plantation used for wood production.

Thanks for raising the issue.

If these things are permanent .. then by all means add them to OSM

If they are ‘cyclic’ .. say open/used every summer for example .. then it may be possible to map them using the open_hours tag to specify when they are usable.

If they only ‘pop up’ once then it is a one time map .. best to keep that out of OSM. By all means use OSM as the basis, no problem there .. a simple copyright notice for a paper map and your done.

Humm … the intention was good. Contacting both mappers may lead to better mapping in future by both of them.

The tag has been entered in the data base.

The size of text for a particular GPS, Phone or Computer depends on the ‘render’ (the maker of the map - they use the data base to get the data.. but the way in which they use it is up to them).

Some GPSes have the ability to change the size of the text, some do not. There may be renders that can change the size of the text too.

But there is no way of entering data into the data base to determine the size of the text nor when it appears (different zoom levels). It would be particularly difficult to do this considering the number of different hardware and software that uses the data.

So .. if you want a more detailed answer .. you ‘ll have to say what you are using - both hardware and software.

One solution to the shop= key is to allow a second entry for the products sold, similar to the text entry mode of the key opening hours. So for your example shop=food shop_products=greengrocer, bakery, cheese, dairy

I’d take the wheelchair as being an access item rather than a for sale item.

Arr .. I see your using it as an example of what goes wrong. And I agree. I have raised the scale model shop issue on the tagging group .. no one came up with a solution .. or at least I don’t recall it. I’d still trying to think of some way of doing it.

The capitals in a key … like FIXME … well I take the view that all OSM keys and values are lower case. Unless the value is a text entry.

The shop= key .. as an example of a good tag? No I don’t think so.

For example .. a scale model shop … sells

cars … in kit from and ready made aeroplanes … in kit from and ready made ships … in kit from and ready made railways … in kit from and ready made trains … in kit from and ready made parts for making models e.g. paint, bits of metal, plastic, wheels, small nuts and bolts, balsa wood, glues etc

… easy you just tag shop=scale_model But then there is a scale model shop that only sells railway/train models, another that only sells parts for making models…

The shop= key is not a good example of OSM tags. There are a lot of single use values in shop= as an example.

I too support the rendering of a ‘footway’ that has the same tags as a ‘path’ to be the same. After all the tags say they are the same!

highway=footway surface=paved width=1

is the same as

highway=path surface=paved width=1

Good Luck with that! :))

A sign on your door saying “Not the Hotel De Pluimpapaver” may cause some to pause?

While you will get cloud coverage on a satellite photo … a different satellite photo taken at a different time won’t have the same clouds. So if your looking at a Bing photo .. try looking at a Mapbox photo .. you may find the things you need.

Glad you like it.

It would be of more interest to some to add your favorite restaurants, pubs, parks … if they are not there already?

I have not mapped my house … but restaurants, shops, parks .. the ones I like go in.

Yes.. mapping landuse is ‘boring’!

It is also seen as less usefull than mapping roads and POIs.

However it does give a good impression as to what goes on in areas when zoomed out. I’m presently trying to map the landuse=residential around Sydney. Boring. But it will better give an impression as to the size of Sydney when zoomed out (I hope).

Hi,

Path and footway … I too view this as stupid. I view both as the same thing. I belive it is a British thing .. where there is a legal difference between the two.. and that should have been handled with a tag like access rather than make a new tag.

Road … not a legal tag .. I’d not render it. Consider it a kind of ‘fixme’ tag?

Planned … again I’d not render it. Not ‘on the ground’ = not verifiable, not confirmed, financed … may not happen. Under construction is much more usefull as there may be interference with other traffic.

Just my ideas.

Hi, Thanks for getting the information. Entering them into OSM will depend on what kind of water source they are …

A tap? man_made=water_tap … with drinking_water=yes,no A spring? .. natural=spring … with drinking_water=yes,no A well? man_made=water_well … with drinking_water=yes,no A bubbler/drinking fountain? amenity=drinking_water Note that this tag doesn’t provide specific information on the type of the water source and implies potability! amenity=water_point waterway=water_point For supply of large quantities of water. emergency=fire_hydrant

Not all of these are rendered.

Updates for me happen quicker on Andosm …

However .. I now don’t look for my changes so much on my device. I do look back at them to check for errors (mine!) using the main web map.

Precision. Well yes to some degree. However it is more important to convey what is on the ground with a reasonable relationship between them. For example … a road curve might be represented as a single node precisely located at the apex. The map would then be a very sharp junction of two lines. Precise - yes, representative? Probably not .. needs more points to represent the curve that is there. Even if those points are not precise, they are a better representation of what is there. So don’t be too concerned with the precision, representation is more important.

I mean it does not like “oneway=no” . IIRC.

And a few other things … like vehicle=yes

… These are default values… most of the time they are not tagged. Sometimes they are, and sometimes there is justification for using these tags.

Humm .. just checked.. presently it does not throw warnings on these things .. it still does throw a warning for oneway=-1. I think that is a change from my memory of its behavior in the past. So either things have changed or my memory is faulty? Maybe I’m better off not knowing the answer to that… :)

The removal of valid data … errr (to ‘fix’ rendering, explicitly stating implied tags)… who is doing that? And why? … There is is some being ‘desired’ by editors .. JOSM validation for example does not ‘like’ oneway=no so there is a temptation to ‘fix’ that. That maybe the source of these kind of deletions. Perhaps this is driven by an effort to reduce the size of the data base.

Changing tags is a problem. Lot of inertia. There will always be opposition to change. “The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore, all progress depends on the unreasonable man.” George Bernard Shaw

Making new tags is also a problem… well making GOOD tags. The present ‘rules’ for tagging consensus is 75% (or 8 votes only 8 votes all for the tag). Lot of ‘I don’t like it’ .. without any thought of the need for a tag to describe this thing and how best to do it. People can, of course, make tags without consensus .. ending up with a tag like dog_bin … when dog excrement is meant rather than a bin for dead dogs.

Tag ‘ownership’? There is an original proposer .. but they could have left OSM.