optional geo support

[fgregg]

@jcarbaugh what do you think about this approach?

[fgregg]

New methods are documented here: https://github.com/datamade/census_area/blob/master/README.rst

[fgregg]

Relates to #28

[ljwolf]

fyi, geo support is provided over in cenpy.

I've looked into the machinery here, and what we're doing is quite different; cenpy automatically discovers & wraps all endpoints exposed by api.census.gov, but could use help customising commonly-accessed data products & integrating the discovered geo stuff with the api.census.govendpoints.

[ljwolf]

There's now a ton more geo support and a better, place-oriented API over in cenpy. Would be great to get development efforts on the US Census Bureau's APIs consolidated in Python, so that we can all push together on common problems :smile:

[MaxGhenis]

Is there a comparison between cenpy and census features? How actively are the two being developed?

[loganpowell]

❤️

[fgregg]

To me, the big difference is that cenpy is built around pandas, and this project will not be.

[hancush]

For folks interested in geo support via census_area, there is now expanded documentation, here: https://census-area.readthedocs.io/en/latest/