Opened 5 years ago

Closed 5 years ago

Last modified 5 years ago

#5363 closed defect (invalid)

7135 S Decatur Blvd, Las Vegas, NV 89118 not resolving.

Reported by: tom.sommer@… Owned by: geocoding@…
Priority: minor Milestone:
Component: nominatim Version:
Keywords: Cc:


I am trying to resolve the address of the Switch 7 Data Center in Las Vegas. The summary is the address straight from their web site. Other mapping systems are able to resolve this address, but OSM for some reason is not. The problem for us is that our Solarwinds network management system has a mapping feature that uses Open Mapquest to resolve the addresses which uses OSM on it's back end. And since Switch 7 is where we have our main data center, then it is a pretty important address for us have show up on our Solarwinds Orion map.

I did try adding this address to OSM, but I am not sure if it actually took. Please assist me to have this address resolve correctly.

I am new at requesting a correction with OSM, so please excuse me if I am not asking using the proper procedure.

Thanks! Tom Sommer

Change History (4)

comment:1 Changed 5 years ago by floscher

I investigated this a bit and found, that Nominatim is stumbling over Las Vegas, because the building is not inside the OSM-border of the city Las Vegas, but rather inside the border of the unincorporated town Enterprise.

So all of the following strings are resolving correctly with Nominatim:

  • 7135 S Decatur Blvd, Enterprise, NV 89118
  • 7135 S Decatur Blvd, NV 89118
  • 7135 S Decatur Blvd, Clark County
  • 7135 South Decatur Boulevard
  • 7135 S Decatur Blvd

I see two ways of resolving the issue: Either Nominatim takes into account, that Enterprise has a tag saying alt_name=Las Vegas and that the building has a tag addr:city=Las Vegas. Or someone extends the border of Las Vegas in OSM-data, so it surrounds everything belonging to the city of Las Vegas.

The latter solution should only be carried out by an OSM-user with experience in editing administrative boundaries and proper knowledge of the correct extent of the city of Las Vegas.

comment:2 Changed 5 years ago by tom.sommer@…

Ok, I see what you mean. Funny, I never knew it was actually not in the city of Vegas. Not even the strip is in the city of Vegas.

Since it seems many of the other mapping systems are able to resolve the address with the city set as "Las Vegas", what avenue should I use to approach OSM to make a change to align with the other systems? Sorry, again, I am new to this and do not know the proper protocol.

Oh yes, is Nominatim simply a front end to OSM?

Thanks for all of your help with this!

comment:3 Changed 5 years ago by Sarah Hoffmann

Resolution: invalid
Status: newclosed

There is indeed not much Nominatim can do about this until the admin borders in the US get sorted out in OSM.

One interesting thing to note: the boundary of Enterprise is currently broken and therefore missing in nominatim: Once it gets repaired the alt_name actually will be resolved (you can already see it on the details page) and the address will be found if you type 'Las Vegas' as the city. The display name will still show Enterprise, though.

Closing here because it is a data problem.

comment:4 Changed 5 years ago by floscher

Thank you lonvia for the tip with the broken relation. I fixed the relation and now the string 7135 S Decatur Blvd, Las Vegas, NV 89118 is correctly geocoded:

@tom.sommer: Nominatim is the most popular geocoder in the OpenStreetMap-world, which is e.g. also used for the search on . This bugtracker is for bugs in the software (in this case the geocoder). For other things like e.g. data-issues that you can't resolve on your own, the forums, one of the mailinglists or are the ideal places to get in contact with experienced mappers. And for individual things missing from the map there are also Notes. But don't be afraid of not following a protocol. There are not many irrevocable rules in OSM, so as long as you respect the other mappers ("the community") and are willing to discuss with and learn from them, there's not much you can do wrong.

Note: See TracTickets for help on using tickets.