Getting 404 errors #3
Comments
|
I sent an email to usagov-developers at gsa.gov about this 6 days ago and I haven't heard back. I'm going to tweet them and see if that works. |
|
Seeing the same issue in a project I had been using this data. Did you ever get an update? |
|
I am getting this error too. I sent an email but haven't heard back. I need list of all agencies and their parent agencies so that I can create a hierarchy for a project. |
|
Anyone ever get any resolution to this? |
|
No man. I have sent multiple emails but never got a reply. |
|
Wow. Did you find an alternate source for the data or did you just give up? I'm mostly looking for the hierarchy in machine readable format. Ideally with contact email and office addresses too. I thought I hit the goldmine with this thing. :(
…Sent from my iPhone
On Feb 5, 2017, at 11:28 AM, MayankSingla13 ***@***.***> wrote:
No man. I have sent multiple emails but never got a reply.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
I have a static list from about a year ago with this information. I can
share it as a Google.doc next week when I'm working again if you want.
On Sun, Feb 5, 2017, 12:52 PM Ted Henderson <[email protected]>
wrote:
… Wow. Did you find an alternate source for the data or did you just give
up? I'm mostly looking for the hierarchy in machine readable format.
Ideally with contact email and office addresses too. I thought I hit the
goldmine with this thing. :(
Sent from my iPhone
> On Feb 5, 2017, at 11:28 AM, MayankSingla13 ***@***.***>
wrote:
>
> No man. I have sent multiple emails but never got a reply.
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub, or mute the thread.
>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#3 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AGe8zT5H5rIl5PUnFB9yUvk6qLq9Z1ZLks5rZgxAgaJpZM4KORlB>
.
|
|
I used this: https://www.federalregister.gov/developers/api/v1/ Hey @cooperfellows can you please share that? |
|
Hey @cooperfellows -- definitely would be great if you're willing to share that. @MayankSingla13 Thanks for the Federal Register link. It would work for me if it had address or email fields, but it doesn't have either. There is a main website field that I might be able to regex email domains out of, but my god that doesn't sound fun. What I find really frustrating is that clearly this API still exists and functions because their own website is clearly using it. That's our government for you.... Thanks for your help guys. |
|
Hey @thedore17 attached is a static list from around Mid September of last year. It's not the complete set of data for each agency, but it's a good chunk of it. I want to be clear that this data could be out of date/incorrect, as I found the API to be lacking in accurate data now and then, but its certainly better than nothing. |
|
@cooperfellows I cannot, just cannot believe the luck that I just came to this place and you posted that file. Made my day. Thanks! |
|
@osnofas Glad you will find it helpful, but again, I take no responsibility for the accuracy of all that data. It's what the API returned in mid-September of 2016, and as noted, the API was not always accurate. |
|
I see what you mean - apparently it thinks that Washington is in Arkansas. |
|
Yep, we wound up using "Zip" instead of the "Statter" field because AK (which is Alaska) kept showing up for Agencies in Washington DC. The Zip field tended to be more reliable, when it was available, because not every record had one :), depending on your use case, you could use a geo lookup API to get the correct state based on that Zip. My guess is that "AK" is the default value for the "Stateter" field in whatever system people used when entering this data into the API (AK is the first state if abbreviations are listed alphabetically) |
|
Could you use the full address and geo-lookup that way? Or are the address
records spotty too?
…On Tue, Feb 7, 2017 at 10:49 AM, Cooper ***@***.***> wrote:
Yep, we wound up using "Zip" instead of the "Statter" field because AK
(which is Alaska) kept showing up for Agencies in Washington DC. The Zip
field tended to be more reliable, when it was available, because not every
record had one :), depending on your use case, you could use a geo lookup
API to get the correct state based on that Zip.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADzaViJGs3CTNaMq_c0hQWTJ2e3HzmgBks5raJJ8gaJpZM4KORlB>
.
|
|
I didn't work with the data too much myself, handed it off to someone else on the team for import into another system. The "stateter" and "Fed Branch" columns provided the most trouble for him from what I could dig up. Not sure about the Address field. It wasn't a big enough problem that I heard about it, so I guess that's good? |
|
Hey Folks, I went through the doc kindly provided by @cooperfellows to clean up all the errant AK's. Interestingly enough there was only one accurate AK out of the entire 474 office list. I am sharing it as a Google Doc here. I also made this data more hacker friendly by converting it to JSON. Please let me know if you find any issues: https://github.com/thedore17/FederalData/blob/master/FederalAgencies-2016-9-14.json |
|
Quick update: Combing through the data has yielded other data anomalies and inconsistencies. Many of the address 1 fields are messed up, so I am fixing those to the best of my abilities while maintaining as much of the original data as I can. |
|
A year later and I am getting the same errors. Was it taken down or is it experiencing a problem? |
|
It was shut down. I got what data I could, and wrote some data massagers in
order to improve the quality. There are still many holes though:
https://github.com/thedore17/FederalData
…On Tue, Oct 10, 2017 at 10:21 AM, carltoncolter ***@***.***> wrote:
A year later and I am getting the same errors. Was it taken down or is it
experiencing a problem?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADzaVnb2GnPCHH1jS4ZEmlC3w_xnQ8Bbks5sq31ngaJpZM4KORlB>
.
|
Looks like even the example URLs are getting 404 errors:
The text was updated successfully, but these errors were encountered: