- The location I entered is showing the wrong information
- The location I entered wasn't found
- The location I entered went to the wrong place
- You're showing a location as a county instead of a city (and similar type problems)
- I went through the list above and read the text below, but there are still problems
DataPlace was built to take publicly available data sets and make them easy to use and view. Our information comes from the original providers, always linked from the
icon near the data set or indicator. For instance, a lot of data comes from US
Census 2000. Many communities have grown substantially since then; therefore,
our data may not match with your actual population today. The location I entered wasn't found
We don't have every location found by other web products. The list of locations we have available comes from locations with data reported to Census, HMDA and so on. In the future, we might find ways to bring known location names into DataPlace, but it's not available now.
The location I entered went to the wrong place
When you enter in an address, we go back to the same freely available set of information that powers DataPlace as the indicators. That said, some of the exact addresses don't match to the actual locations of the address. This is something we can potentially fix in the future, but actually, it works rather well for most locations throughout the nation.
You're showing a location as a county instead of a city (and similar type problems)
The definitions we use for classifying a location, for instance the City of Baltimore, come from our publicly available data sets. For a number of reasons, which we're happy to answer individually in the DataPlace forums, a location, such as the City of Baltimore, may appear as a county. We understand that Baltimore is a city and not a county, but for complete coverage of the state, in Baltimore's case, it's treated as a county for the purposes of having the county populations across the state of Maryland tallying the state population. It's a convention used by Census, therefore it is a convention used on DataPlace.
I went through the list above and read the text below, but there are still problems
It's possible in the billions and billions of combinations of locations mapped to indicators that something's awry. It's also possible that the enormous computing power brought together to make a dynamic site like this run may suffer from a few glitches. For any problem you see, we want to fix it and we'd like your help. DataPlace, as a product of the Fannie Mae Foundation, is geared to be community driven and responsive. If there are errors, feature requests, whatever, we want to hear from you, partner with you, and/or respond to you as best we can.