Changeset No. Date Contributor Comment
12018-03-13 08:45:24 UTChighflyer74 Hi Dave!

Can you check please? There are still some non-OSM tags on it.

Greetings from across the pond!
22018-03-13 14:02:57 UTCAlaskaDave Got it, extra tags removed. Thanks!
12018-03-12 12:04:34 UTCmueschel Hi,
could you please check the rivers? It looks like they overlap with previously mapped rivers. And I guess these tags shouldn't have been uploaded:
RIVERCATEG = Federally Administered
SHAPE_LEN = 5.50073159877
STATE = Alaska
22018-03-12 14:23:42 UTCAlaskaDave Thank you for the note. I forgot to clean up the original tags and left some extra tags on one section. I removed those. But I don't see any "overlap" with previously mapped rivers. Can you explain more fully what you mean?
32018-03-12 14:37:24 UTCmueschel Looking more closely, it's just a glitch of the rendering server - when I checked both the new and the old (coarse) river way were shown simultaneously. The database is clean though.
12018-01-13 07:13:09 UTCAlaskaDave Somehow, portions of 1211 including this one, got renamed Den Ha (1211). Mapper did not give source. I renamed it to what it was previously, Sunwichai Road, which is a translation of the Thai name tag.
22018-01-13 07:45:34 UTCAlaskaDave I checked Google, and it gives Den Ha Dong Mada Road as the name. Thai street names are notoriously hard to map properly because signs bearing the name are rare. Many times the name is just a best guess and might be based on one road sign many km distant.
12017-10-23 15:13:10 UTCimagico Hello Dave,

i would advise against trying to map features where you have nothing even close to verifiable position data for.

The location of node 5125769091 is a highly unlikely position for an islet or even a gravel bar based on the sea ice movement in the area - ice would not be able to move...
22017-10-23 23:58:03 UTCAlaskaDave Ordinarily, I would agree with you. I came across Shea's description through a newspaper article I read that mentioned Stray Dog West. When I searched for it on OSM, nothing came up and I wanted to at least put a findable entry into Nominatum. The uncertainty of the position is why I added the fixme...
32017-10-24 08:29:42 UTCimagico This is just my assessment of the situation - i won't insist on changing anything here. But i am pretty sure the position is wrong, not wrong by a few hundred meters but wrong by likely many kilometers - either much closer to the shore or much further to the east (that is the problem with secondary...
12017-09-14 15:18:02 UTCHarald Hartmann Hello AlaskaDave. At you have tagged `l=0`. Sould it be `level`? #newkey
22017-09-14 22:23:18 UTCAlaskaDave Definitely. It was purely accidental. Working with OSMAnd on a phone can be tricky for a person with big fingers. I'm at a loss to explain just how it happened but I'll fix it pronto.
12017-09-13 05:43:21 UTCAlaskaDave Source should be ESRI World
12017-08-23 13:06:58 UTCGerdP Hi!
I found 3 ways with hihway=fof , one created in this CS, all created by you.
What does it mean?
Just a typo for footway?
22017-08-23 14:44:25 UTCAlaskaDave Sorry, It is a typo, caused by JOSM "remembering" a bad value. I cannot locate any place in JOSM that contains the text "fof" that I used by mistake over a year ago but JOSM insert it sometimes still. It's supposed to be "footway".
32017-08-23 14:50:55 UTCGerdP Maybe search for key=properties.recent-tags
in your preferences.xml and check if you find "fof"
42017-08-23 15:05:15 UTCAlaskaDave Tried that already. It's not there. This is an annoying issue but one I cani' seem to rid myself of.
52017-08-24 05:24:36 UTCGerdP OK. Strange. Please check also
Can't see much on sat images and the way crosses a river.
62017-08-24 12:20:12 UTCAlaskaDave I changed that one to highway=path - it is much more visible on the new DigitalGlobe imagery. I have no way to tell what the "trail" actually looks like and because of its remoteness I never will, so that's only a guess. I'll work on it again and check the stream crossings when I have more...
12017-04-22 02:02:14 UTCTheOutpost Hi Dave, the rendering in OSM around these islands looks very odd. You know what's up?
22017-04-22 10:14:26 UTCAlaskaDave It's a rendering issue of some sort. I added Shuyak Island State Park using rough boundaries back in January. Coastllnes seem to be invisible with the current tagging using leisure=park although I can see them fine in my custom maps.
Just now I altered the tagging a bit to use boundary=protected_ar...
32017-04-25 19:42:55 UTCAlaskaDave I have spent the morning fixing errors in multipolygons and guess what? I redrew a portion of the coastline of Shuyak Island when I fixed up the Perevalnie Islands but forgot to add that new section to the coastline multipolygon. Rendering looks right now.
42017-05-01 20:17:08 UTCTheOutpost Hmm, still looks odd, though I wonder if the tiles are stale. Looks ok at certain zooms.
52017-05-02 01:33:21 UTCAlaskaDave It's most likely some sort of caching or currency problem with the OSM server. I'm sure it will render okay eventually.
12017-04-22 02:03:45 UTCTheOutpost Hi Dave,

After putting in the state park with an area covering the islands and a lot of water, the islands don't render right. Is this an official boundary of the state park?
12017-04-19 14:01:24 UTCAlaskaDave 2017-04-19 The original CanVec imports used many individual nodes labeled name=Kaskawulsh Glacier and natural=glacier. I removed those and added the name to several existing natural=glacier multipolygons. Recently reported changes in this glacier mean its present outline is not the same as shown.on ...
12017-03-22 05:44:06 UTCTaniaak In case you're searching for some online networking apparatuses to help make your procedure run all the more easily, then look at this article offers numerous proposals 16 Social Media Tools The Experts Swear By.
see more
12017-03-07 03:10:28 UTCmuralito Hi AlaskaDave:

Some tags of the elements you added doesn't have any meaning in OSM.

It's probably an import that you did it unadvertedly, and could be improved to be more useful.
22017-03-07 04:53:20 UTCAlaskaDave Yep, you're right. I used a list from the USFWS website and didn't bother to clean up the old tagging. It's on my todo list.
32017-03-07 05:22:32 UTCAlaskaDave Done.
12016-10-16 10:55:45 UTCAlaskaDave This changeset actually included many edits to the streets in Dillingham. Reworked and relocated, simplified horrible existing Tiger data. This is a work in progress. I saved it but forgot to change the comment to reflect what was done.
12015-10-31 11:11:22 UTCGerdP please review way 365943695:
the tag highway=junction is rarely used.
Consider using nodes with highway=motorway_junction, see
22015-10-31 12:40:53 UTCAlaskaDave No problem. I was looking for a way to record the name of this historical junction and came up with highway=junction, admittedly a bad idea. The two ways no longer cross - consequently there is no longer a junction - 1317 now crosses 11 on bridges. I'll just leave its name on the area and remove the...
32015-10-31 12:45:12 UTCGerdP okay, thanks
12015-01-31 03:20:51 UTCstephankn regarding mini hydro: I think the main reservoir is a bit upstream. It it a pump storage plant? so maybe the empty reservoir is the lower basin?
22015-01-31 06:00:52 UTCAlaskaDave I don't know. I merely moved an existing reservoir to where I thought it might be when more water is present. I think the reservoir you tagged is probably the actual location.

I think the original reservoir should be deleted. By the way, are you sure the name is spelled Meatian? I think it is Mae...
32015-01-31 08:34:12 UTCstephankn It is a wrong spelling on their sign. I put in both spellings and removed the riverbank.
42015-01-31 09:07:55 UTCAlaskaDave Sounds good.
12014-12-11 03:06:23 UTCAlaskaDave This comment is from the one I saved previously. It should read: Adding some POIs in my neighborhood of Chang Phuak. source=Bing, survey, GPS
16 changeset(s) created by AlaskaDave have been discussed with a total of 39 comment(s)