OpenStreetMap logo OpenStreetMap

Changeset When Comment
116474947 almost 4 years ago

Priisle selver is under construction. You can add "construction:" prefix to fix it.
construction=*

115848540 almost 4 years ago

>I think the general conclusion from that and the way things are is that both scrub/grass scheme and simple man-made=clearcut tag are insufficient for given purpose.

There is no "general conclusion". On the same man_made=clearcut there is lot of arguments for it. I think that it's the best approach given the tags we have today, while obviously not ideal.

115848540 almost 4 years ago

*obviosly meant "not implying" in the first sentence.

115848540 almost 4 years ago

I'm implying that opinions have no value or that you have no point. I'm saying that opinions are DIFFERENT. And as long as we don't have a stricter tagging scheme in OSM, they should coexist and allow a bit of leeway.

Clear-cut in a landuse=forest filled with "scrub" can be interpreted as a (very) young forest area. You may not like it, you may have points against it, but today that's how it is.

The solution may be that you stop arguing with one person and use your energy to help define a better standard.

This is going nowhere. Don't expect me to reply anymore. I understand your position, you aren't attempting to understand mine.

I'm sorry if I made you feel bad.

115848540 almost 4 years ago

>I'd also use common sense, but I don't get why you'd consider forest of about 1 m tall trees against common sense.

I'd consider removing scrub against common sense.

Everything else you wrote is again opinions, which can be different. Estonian goverment does not govern OSM and does not define which tags should be used.

Sadly, it would be hard for us to create a big enough discussion in Estonian OSM community to accept some local standard.

115848540 almost 4 years ago

>I'd say a clear-cut rather falls in the temporary category as it's expected to develop into something else quite shortly, in a few years time.

This is your peronal opinion which has nothing to do with best practices you mentioned.

>Small forest surrounded and managed grasslands exist, but I don't think anyone on the other hand would really consider a clear-cut filled with stumps a grassland. Most of given clear-cuts here also are no longer dominated by grasses. Due to sparse canopy and bare crowns, it may not show well on an orthophoto, but these "grasslands" are filled with (small) trees.
>Note that man_made=clearcut tag exists. It's not rendered on osm.org and it could be used to sort of work around grassland-scrub.

I'll add man_made=clearcut you mentioned. But this tag is not exclusive to the vegetation. And the areas with small trees which are mistagged can be mapped as scrubs like it's mentioned on the man_made=clearcut wiki page.

>how does a mapper know at all that it's no longer something less than a forest and that area can be removed?

There is no clear standard on this. I'd wait until the trees are at least 3m in height. Someone else may have a different opinion and I won't be against it as long as he uses common sence and doesn't consider 1m trees grown. As with many things on OSM, common sence should be used and different approaches to tagging may exist until a stricter and more exact standard is implemented. Which highway tag value should be used for a combined foot and cycleway - footway, path or a cycleway? Can a small group of trees be tagged as natural=wood or landcover=trees? How sparse can they grow until they stop becoming one? Can you precisely answer these questions without bringing your PERSONAL opinion? Probably not.

Overall, I get your point and I'm not against having just a landuse=forest with man_made=clearcut, but I also don't agree that it's the only way and think that clearcuts can be descibed in more detail.

115848540 almost 4 years ago

>I wouldn't say that any one these areas is a grassland only because grasses were dominant for a couple of years.

But this is what a grassland is...

>As for scrub, I realize that OSM mappers interpret it very differently, but it'd probably be more intuitive to consider it as a habitat where shrubs are more or less persistent (not very common in our climate, but juniper shrubbery might be a good example), rather than just young forest.
>based on what criteria would you consider a young forest simply a forest again then?

I agree that definition of a scrub is a bit fuzzy, but it is sometimes used for any small trees. I think it's ok to use it here - trees there are very distinct from the surrounding forest.
natural=scrub
The only reference to height you can find here is "less than 5 meters tall" here. I'm not really strict about (as with many things in OSM, it's hard to objectively tag) BTW, notice that the next sentence on linked page mentions young trees.

> Then again such clear-cut areas are expected to be temporary and it generally isn't considered a good practice to map temporary features.

Buildings are temporary too. Trees don't grow overnight, Considering that it's a place not far from the capital, it's unlikely to be abandoned by mappers and get too outdated. What this good practice means is "Don't map cars, festivals or weekly markets".

> Also, a young forest by most definitions in common use is also a forest.

I'm not mapping landuse with grassland and scrub, I'm mapping what's there in addition to landuse.

115848540 almost 4 years ago

I agree that landuse should be fixed, thanks for pointing that out. I'll still map these areas separately, but they will be under landuse=forest

104315818 almost 4 years ago

Some time ago you asked opinion about your imports. Well, I've noticed that you've put e-cigarette shop INSIDE McDonalds and a pharmacy in an empty field. :(

Clearly could use some basic manual validation.

112326718 about 4 years ago

Hello, I recommend you to use aerial imagery from Maa-amet. It has a lot higher resolution and accuracy than Bing, especially cadastre map. These parking lots could have been a lot more accurate. (While this changeset is old, I see that you are continuing to use Bing)

114332567 about 4 years ago

Good job!

BTW,

bicycle=designated
foot=designated
highway=cycleway

is not in any way different from

bicycle=designated
foot=designated
highway=path

but may be incorrectly interpreted by some data consumers, such as cyclosm.org

we can also mark it as

bicycle=designated
highway=footway

I find that path is a good middle ground for combined pedestrian/bicycle roads.
See also osm.wiki/Path_controversy

109641254 over 4 years ago

Thank you for participation.

The crossing you've added is not a bicycle crossing, but a usual one, so there is no sense in tagging it as a bicycle crossing.

Also, the nodes were not connected to paths. While it may look ok on a map, a routing software would not be able to find a route if ways are not connected.

I've fixed these problems.

110758768 over 4 years ago

Also, bus routes are broken on all intersections Aulo has touched :(
route=roads are often broken or work in one direction only / road names missing on some parts.

110714281 over 4 years ago

I've finally got to updating it. Turned out quite ugly, I've tried different approaches, but all of them don't look good.

Also, there is some route Vana-Narva maantee which seems to start too early and contradicts Maaamet and osm name tags. Maybe should be fixed too.

110758768 over 4 years ago

Another discussion created by @Pikse
changeset/110759541

110759541 over 4 years ago

@Pikse there are multiple changesets by @Aulo which uglified roads. Lanes should not be mapped as separate roads.

I think that @Aulo should fix it back.

Another discussion
changeset/110758768

110714281 over 4 years ago

Thanks for this thorough analysys, fghj753.

>This means that routing engines will direct drivers to the residents via parking lot and sometimes via Irusilla.

Did you mean Iru tee? Anyway, it can be expected that a good routing engine could allow routing to an access=destination residential road, but routing by a highway=cycleway may be a bit questionable.

>That is technique often used with temporary road construction signs to indicate that restrictions are not applied at the moment.

Or maybe it's vandalism. Actually correct technique:
https://www.google.com/maps/@59.4262229,24.7569369,3a,41.5y,101.37h,88.53t/data=!3m6!1e1!3m4!1sHkLLPyCu6d6wuaEsvZ62QQ!2e0!7i13312!8i6656
Btw, they added an exclusion there, yay!

What is your opinion on making this a residential street?

Some more questionable combination of a do not enter and a bicycle way, seems like it's ok to assume things:
https://www.google.com/maps/@59.4683898,24.8678497,3a,45.2y,18.92h,89.94t/data=!3m6!1e1!3m4!1srfmjNFmN87cKBR6VhsdkTQ!2e0!7i13312!8i6656

110714281 over 4 years ago

Or not, I don't remember what turns are allowed from that road.

If I remember correctly, it has contradicting signs
1) Combined pedestrian/bicycle road sign
2) Do not enter sign with exclusion for residents (btw, do not enter sign applies to cyclists too, round red circle with a white background excludes them)
3) Residential road sign

The signs are kind of confusing there, but you have cut if off for cars completely. I'd say we should go for what practically is expected of this road.

In my opinion, this should be attached back to the Narva mnt and made residential. highway=residential is better than a cycle way as cyclists are often allowed on the road, but the routing software may completely ignore cycleways for cars. Also pedestrians may expect cars there.

Please fix it if you can, unless the signs changed or share your thoughts.

110714281 over 4 years ago

Hello, route way/129226648/history
is a residential road. Changing it back.

110758768 over 4 years ago

Noticed the same thing. I agree with fghj753. This makes the map a lot harder to read and contradicts convetion of making separate highways for physically separated roads.