Here’s something I learned today, which might be interesting for other people working on mapping or on improving user experience for map editors.

I recently found that when I searched for Isla Vista Elementary School, its place name listing included “Ellwood” as the neighborhood, which is incorrect - the school is in the neighborhood of Isla Vista (as you can probably guess from the name), not in the nearby Ellwood neighborhood. I wanted to fix this, but I was confused about where this Ellwood place name was coming from - I couldn’t find a tag on the school that mentioned Ellwood, and I couldn’t find a boundary/border/area for Ellwood that included the school. Part of the weirdness to me is that Ellwood is in the city of Goleta, and Isla Vista is in unincorporated county land outside of Goleta.

Then I asked about this on #osm IRC, and a person explained that to figure out what’s going on here, I could look up the school on Nominatim (which I hadn’t heard of before other than seeing a mention of it in the search interface and didn’t know what it was!), which said that Ellwood was a nearby node. Then #osm told me the next thing I needed to know: that Nominatim was probably using the Ellwood node as a guess for the neighborhood since it didn’t have anything better, such as a closer node or an area.

Ah ha! So I put in a neighborhood node at the center of Isla Vista with the name “Isla Vista”. Now if you search for Isla Vista Elementary School, the generated address includes “Isla Vista” in the place name listing. It now also includes “El Encanto Heights” though, since that’s another nearby neighborhood node - which is incorrect as a place name for the school’s area. So it looks like I’ll need to figure out how to put in an area boundary for Isla Vista if I want this to be more reliably accurate.

… See full entry

Writing this down since it may be useful for other beginners:

My biggest confusion at first was that my edits didn’t show up right away, and the interface provided no hint about why that was happening (so I wondered if I was doing something wrong). I googled it and found out that delays are normal, but the estimate in the FAQ said “a few minutes”, which hasn’t seemed accurate for me - my edits often seem to take hours to show up. So I just have to do my edits and then check back on them later; as a newbie, it’s important to me to verify my edits to make sure I did them correctly. Eventually I read the extended technical explanation for delays on the Q&A site, and it helped me be patient with the process; I’m not a programmer, but I work with software, and I can appreciate descriptions of complicated caching systems. :)

My next stumble was when I found editing a set of park boundaries difficult to do properly (since attempting to fix the boundaries seemed to delete the adjoining streets). I asked the OSM IRC channel for help (which I found by googling “OSM IRC”, since I’m familiar with IRC and like using it), and their comments suggested trying a different editor - which worked! Fixing the boundaries was much easier in iD than in Potlatch (which I’d been using since it’s the default editor), even though I’ve stuck with Potlatch for most edits since it provides lots of point-and-click options for adding and annotating points of interest and other details. I learned that if something is hard/tricky, I should try a different editor.

I only ran into the Good practice wiki page and Bing wiki page by accident (when trying to help an even-newer person on IRC), but they’re very helpful. On the “good practice” page, “One feature, one OSM element” confirmed for me a best practice I’d guessed about, and I appreciated learning why it was OK to trace from Bing (I’d been wondering about that).

… See full entry