Vote up to Idea wildcarding geo values
Voting Disabled
Vote down to Idea wildcarding geo values

Rank54

Idea#25

This idea is active.
API Technical Discussions »

wildcarding geo values

this applies to block groups, but others as well ... '+county:*+tract:*' with acs5 is not set to operate with the * wildcarding (using the above selects the first BG in each county only) but would be immensely valuable if county and tract can accept wildcarding rather than specific values. For most users, looking up a tract code is infeasible and generally not desireable (multi tracts being the norm).

Thank you and keep going!

Submitted by Community Member 2 years ago

Vote Activity Show

Events

  1. The idea was posted
    2 years ago

Comments (5)

  1. This post has me confused on one point. Why would a user be looking at the query string? The main idea behind the API is that developers can use these queries to get data back for use inside an app.

    It should be feasible that you could draw back the tract names along with the counties and states they reside in without ever exposing the tract code to a user (or state and county codes for that matter).

    I do see the merits of adding this functionality, and will suggest it to the members of the API development group.

    2 years ago
    0 Agreed
    0 Disagreed
    1. Community Member Idea Submitter

      re 'Why would a user be looking at the query string?' - agreed; it may be that they will not. My comment should have been structured a different way.

      2 years ago
      0 Agreed
      0 Disagreed
    2. Considering this is an Application Programming Interface, an end user should *never* see what is being done on this level.

      2 years ago
      0 Agreed
      0 Disagreed
  2. Community Member,

    Thank you for your feedback.

    With respect to allowing additional wildcards.

    This is a feature that others have asked for as well and it is something we (the developers) have discussed. It's a good idea. There is a trade-off between flexibility and performance that we need to consider. For example, we would never allow:

    get=P0010001&for=block:*&in=state:*+county:*+tract:*

    because that returns over 11 million records. If you need bulk access to the data like that then you're far better off downloading it from the FTP site. However, we may allow something like:

    get=P0010001&for=block+group:*&in=state:02+county:170+tract:*

    This was an example that Jan Vink asked for during the beta test. This returns 49 records and can do in one call to the API what would otherwise take 24 separate calls.

    The first step for us is to determine what combinations of wildcard and non-wildcards make sense for each level of geography. Once we've done that we can make the relevant changes to the software.

    We have the feature request in our internal developer database, so it is on our radar. We'll post a message back here once we have things working.

    Thanks again for the feedback. It is very much appreciated.

    2 years ago
    2 Agreed
    0 Disagreed
  3. That would be very valuable to be able to retrieve wildcard records for tract/blockgroup by county. I am able to use the API to create cloropleth map by tract for a county with a single API call, but not able to create a cloropleth map at the block or block group level without multiple seperate calls.

    1 year ago
    2 Agreed
    0 Disagreed