Changeset 115632320 fixes various errors where these paths crossed roads and streams. Did Joe’s Trail get extended south? I retagged these other paths as informal paths, assuming they aren’t part of Joe’s Trail or any other official trail. (It isn’t appropriate to map an ordinary footpath alongside railroad tracks where it would require special care or trespassing.)

Good idea, thanks!

For the record, most of the building geometries have been replaced by professionally digitized CAGIS geometries (with addresses) in changesets 115414253, 115465635, 115487649, 115490252, 115508314, 115510643, and 115511220. All that remains are around 250 tiny toolsheds and doghouses, many of which are already perfectly fine: https://overpass-turbo.eu/s/1eF9 .

Separately, local mappers have been manually improving building geometries in the area in changesets such as 100121624, without the need for the disruptive editing that was seen here.

Thanks for adding these floor counts and roof shapes; they make 3D renders of Loveland look a lot more recognizable. Note that the floor count should normally exclude the attic, but you can explicitly specify the attic by setting roof:levels to 1.

Ah, I hadn’t noticed that earlier appearance. In any case, this syntax is disputed in osm.wiki/Talk:Key:charge#Proposed_advanced_usage so I’ll throw my 2¢ into the talk page.

You’re the expert on key order, so I’ll defer to you on that point. 😉 Fixed in changeset 115399765.

By the way, I don’t mean a fixed price per axle; there are sections that have unrelated prices depending on the number of axles on the vehicle: osm.org/node/3248852590 These signs are newer than the signs showing prices by vehicle type that I saw in Bing Streetside, so the latter may have been replaced by per-axle signs anyways.

Unfortunately, the access keys as units would be inconsistent with the differing prices per axle along other sections of the highway, which require conditional tagging. There would still need to be charge:txtag for the TxTag-specific prices too. It looks like there is precedent for keeping the prices in separate keys, so if possible, I would prefer to stick with that for prices based on the standard TxDOT signs for toll roads.

Access-as-unit was only very recently documented in osm.wiki/Special:Diff/2188260 and usage appears to be largely limited to Brazil and Malaysia, which may have very different needs around pricing than toll roads in the U.S.

Hi, thanks for asking. Based on the DirecTV logo visible in the window in https://www.mapillary.com/app/?pKey=478695443574475 , I surmised that it’s the office of a satellite TV dish installation business. I’m aware of shop=telecommunication and office=telecommunication, but those tags don’t quite connote this kind of business. It’s much closer to an electrician’s office (craft=electrician), but you can stop by to learn about all the wonderful TV channels they offer.

Anyhow, newer imagery in https://www.mapillary.com/app/?pKey=220088529593251 shows that the business has been replaced by something called “CMB”, though I can’t figure out what kind of business it is. I retagged it as shop=yes in changeset 115368832.

Hi, do you recall why the U.S. 62 designation needed to be moved to the end of the list of route numbers in these ref tags? Comparing osm.org/way/255092322 to https://www.mapillary.com/app/?pKey=1919723721518855 and osm.org/way/197144648 to https://www.mapillary.com/app/?pKey=528759105199990, I don’t see any evidence that it normally goes last in a route marker assembly or in other contexts. Did New Mexico or Texas do something different at the time? Just trying to verify my long-held assumption that route number ordering can be idiosyncratic.

Parallel lines would represent these standalone curbs too similarly to curbs that surround a traffic island, but anyways Bing imagery doesn’t have high enough resolution to distinguish the gaps in the curbs that allow stormwater to pass through, let alone the edges of the curbs.

In changeset 114597028, I split up the ways so that they don’t double back on themselves. That should satisfy any validator for topology, though there are still coincident curbs.

They’re more like curbs than walls, hence the kerb:height=6" tags. They’re tapered so that emergency vehicles and delivery vans can back in directly from the through lanes. Here’s what they look like on the ground:

https://commons.wikimedia.org/wiki/File:Frontage_lane_on_South_11th_Street_before_San_Fernando_Street,_San_Jose,_California.jpg

It’s awkward because barrier=kerb was defined with the assumption that a curb separates a sidewalk from the street, oblivious to this kind of divider. There’s some additional discussion on this topic on the wiki:

osm.wiki/Talk:Key:kerb#.22Double_sided.22_kerbs

Maybe it would be better to add a tag indicating that it’s double-sided?

Are these county roads actually ever referred to by prefixed route numbers like “CR 600 E”? I’m afraid you might’ve copied some mistaken tagging I did years ago in counties to the south. I even blithely ignored the north–south part of the street names because they didn’t fit my mental model of how route refs worked. These street grid–based numbered county roads should just be named, unless there’s a clear reason why they should be modeled as routes too.

For context, I brought up this issue in https://lists.openstreetmap.org/pipermail/talk-us/2021-November/021466.html . Please weigh in there with your observations if you can.

I deleted the charging station in changeset 114034899.

Well, it’s your driveway in a free country. If naming it motivates you to stick around and help us build out coverage of the East Side, then there are bigger fish to fry, like all the missing subdivision names around here. And if you really do care about this name, you can probably get a custom sign printed at a number of nearby shops (which are also missing).

I’m sorry your experience so far has been battling to get edits to stick, but we’re trying to hold the line against pranksters, you know?

If you’re interested, lots of mappers hang out on Slack and Discord. It’d be a better way to get to know the community than a changeset comment thread: https://slack.openstreetmap.us/

Technically, it would be more difficult to remove than the name tag on this driveway. 😛

However “vanity street names“ are usually posted is fine – it doesn’t have to be a standard street name sign, but it would have to be posted in a permanent way. In general, roadways are only named in OSM if the name can reasonably be used for wayfinding. Otherwise, someone getting directions to your Airbnb would be told to look for a street by this name and likely miss it.

This was caused by https://github.com/openstreetmap/iD/issues/2657, which has since been fixed.

Which roads are you referring to? This is an ancient changeset based on imagery that’s no longer available online, so I don’t think I can really answer your question without more information.

TIGER represents divided roads as single lines, so we have to manually split them into parallel ways. I did that for the remainder of St. Andrews in changeset 113645057.

👍