In ArcGIS Online, when adding a csv file from a URL (Add Layer from Web), the system doesn't recognize the columns, it only shows _html_. But my csv file contains the following columns: FID, ISO-3166 alpha-2, NS deployed
Take out the hyphens and spaces. Put in underscores for your field names.
I agree with Adrian, you need to remove any spaces or special characters from the columns in the excel and try and have the columns names to start with a letter and not a number.
Thank you very much for your feedback.
We did try as you said but still the same message show up. It might come from our Share Point (linked to some security process). We are enquiring on our side. We will let you know when we find a solution.
Can you share the CSV layer publicly here so others can test it?
Unfortunately the file is on our Share Point Organization, I cannot share it. I can send it to you if you'd like to test it. But it looks like that (saved as csv) :
Do you have location data for it to be located on the map?
This article may help:
CSV, TXT, and GPX files—ArcGIS Online Help | ArcGIS
I have "only" these two fields. I use this file to make a join (ISO) with another one ("World Countries (Generalized)")) to display the countries in the join. As this file can be updated once in a while I would like that someone can update the file on share point and then automatically the map gets updated.
The CSV has to have location data in order to be displayed on a map. See the above link for details.
Actually you're right if I wanted to display something on the map, but in my case I "only" want to make a join. In the link you mention it is also written :
You can also add a CSV file that doesn't contain location information to Map Viewer as a table. This is useful when you want to join nonspatial data—for example, property damage claims related to a recent tornado—to spatial data such as a ZIP Codes layer using the Join Features analysis tool.
Hi Sébastien - one thing to check is the response from the server providing the csv. The headers that are returned when the request is made from the map viewer may be causing the CSV to be interpreted as something other than text (which would potentially cause parsing to fail, etc).
You can check this out using a browser's developer tools (Chrome has a great set). Esri technical support can assist as well. In the response headers from the request for the CSV, you should see content-type as a property. This is an example from the USGS for their recent earthquakes feed:
Retrieving data ...