Python Forum
FCC API: addressing unexpected error
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
FCC API: addressing unexpected error
#4
Bingo!:

Trying this (this is your data above):
http://data.fcc.gov/api/block/find?format=json&latitude=32.35204448&longitude= -106.77485461&showall=true
Gives:
Output:
{"Block":{"FIPS":"350130001041007"},"County":{"FIPS":"35013","name":"Doña Ana"},"State":{"FIPS":"35","code":"NM","name":"New Mexico"},"status":"OK","executionTime":"1004"}
With the ñ conveniently in columns 72.
Looking at the JSON standard, Unicode characters are accepted, and the response seems to be proper UTF-8, so it would be your code that doesn't handle UTF-8 properly (assumes ASCII only?).
Unless noted otherwise, code in my posts should be understood as "coding suggestions", and its use may require more neurones than the two necessary for Ctrl-C/Ctrl-V.
Your one-stop place for all your GIMP needs: gimp-forum.net
Reply


Messages In This Thread
FCC API: addressing unexpected error - by kiton - Jun-26-2017, 05:53 PM
RE: FCC API: addressing unexpected error - by kiton - Jun-26-2017, 07:09 PM
RE: FCC API: addressing unexpected error - by Ofnuts - Jun-27-2017, 08:28 PM
RE: FCC API: addressing unexpected error - by kiton - Jun-27-2017, 11:41 PM
RE: FCC API: addressing unexpected error - by kiton - Jun-28-2017, 06:21 PM
RE: FCC API: addressing unexpected error - by kiton - Jun-29-2017, 07:44 PM

Possibly Related Threads…
Thread Author Replies Views Last Post
  Addressing with np.where pberrett 0 1,604 May-19-2019, 12:45 PM
Last Post: pberrett

Forum Jump:

User Panel Messages

Announcements
Announcement #1 8/1/2020
Announcement #2 8/2/2020
Announcement #3 8/6/2020