I was browsing the map for Pennsylvania looking for the campground at Nemacolin called Maggie Valley. There is a listing for the campground, found here, but it does not show up on the map. The address for it seems to be correct, and it is still open. Also, a website can be added to this listing: http://www.nemacolin.com/accommodations/maggie-valley Not a place I would stay, but it may be helpful to some.
I'm pretty sure that the map pins shown on the state maps are generated by Google Maps using the names of the parks. In this case, if you use Maggie Valley, Farmington PA as the subject for a Google Maps search you will discover that Maps doesn't correlate that name with the Nemacolin Woodlands Resort and your search won't find what you are looking for. OTOH if you search Google for the same thing it will be successful because it has indexed a page within the Resort's website on which the RV park is described. I'll report the situation, but it is rather unique and probably doesn't affect more than a handful of parks. Thanks for your help. I have added the URL you provided and I have changed the park's listing to read Maggie Valley RV Park at the Nemacolin Woodlands Resort which more accurately describes what it is.
The reason you could not see a pin for this park at its location in Farmington, PA, is because the pin was located in South Dakota. I have moved the pin to the correct location and it is now visible on the state map. There is only one review listed for this place and it is from 2007 so the coordinates for this park must have been entered wrong at that time. We apologize for any inconvenience.
I'm very confused by this. I had opened the map app on the park's listing and it clearly had the pin set to the Nemacolin Resort which is how I learned that the park is part of the resort. What did you do to find the pin in SD? Are there two different pins in use in these map displays?
This is strange because I never saw the pin in the correct location. Just as you did, all I did was open the map on the park's listing, and the pin was in South Dakota, so I just moved it to the correct place.
I've now realized that the South Dakota pin placement is simply the "default" location that the system uses when it doesn't know where a park is. For the park in this case, I had already mentioned that Google Maps didn't know where the park was located, therefore, the pin was placed in South Dakota. It's a placement due to omission, rather than intent.
The default for the map pin used to be off the coast of Africa. It was changed to North Dakota (look closely and you will see it is just inside that state boundary) some time ago. I was under the impression that the default map pin was set by the RVPR tech team and not Google.
