Convert DBF to JSON
Turn DBF documents into JSON. An array with one object per record, keyed by the field names, with numbers typed, dates as YYYY-MM-DD and logical fields as the text TRUE or FALSE.
Converted in an isolated sandbox on our serversDeleted after 24 hours
Drop DBF files on the dialor turn it to pick what to do
Every record as a JSON object.Each row of the DBF table becomes one object, keyed by its field names.
What you get
One JSON file holding an array. Each record in the table is one object in that array, and the keys are the field names.
Numbers are typed as numbers. Dates are written as YYYY-MM-DD. Logical fields come out as the text TRUE or FALSE, not as JSON booleans.
How text is read
Text is decoded with the code page the file names. If the file names none, it is read as Western European.
What is not carried over
Some FoxPro fields have no JSON form here. Currency, date-time and memo fields come out as an unsupported-field note instead of a value. Double fields come out as 0.
When it fails
If the file cannot be parsed, the conversion stops with
input_corrupted.
DBF and JSON.What each format is.
The formats
dBase Table
dBase tables, the attribute tables of shapefiles and many legacy databases.
- Extensions
- .dbf
- MIME type
- application
/x -dbf - Kind
- Documents
JSON
JSON, the data format of every API.
- Extensions
- .json
- MIME type
- application
/json - Kind
- Text and data
In your code.The same DBF to JSON conversion through the API, for your app or your agent.
$ cv convert sheet.dbf sheet.json$ cv convert sheet.dbf sheet.jsonQuestions.What people ask about DBF to JSON.
It is an array with one object per record. Each object uses the table's field names as keys.
No. They are written as the text TRUE or FALSE.
Numbers are typed as numbers. Dates are written as YYYY-MM-DD.
Double fields come out as 0 in the JSON. FoxPro currency, date-time and memo fields come out as an unsupported-field note.