Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: Had a problem with parsing the file "it_dati_territoriali.json", is it a JSON file? TypeError: e[1].map is not a function #3

Open
LorenzoStucchi opened this issue Aug 24, 2021 · 3 comments

Comments

@LorenzoStucchi
Copy link

I'm trying to convert a working file for TerriaMap v7 to v8 but I have this generic error, there is some more detailed description for the error?

The file is also here.

I saw from another file that the field "dataUrlType" and "dataUrl" are not working so I already removed them.

@nf-s
Copy link
Contributor

nf-s commented Aug 24, 2021

Hi @LorenzoStucchi

Thanks for reporting the issue!

The error is caused by the availableStyles transformation here

https://github.com/TerriaJS/catalog-converter/blob/fb4827ad46479974a8c23ab17024f1e2034eb9e6/src/converters/WmsCatalogItem.ts#L43-L61

I believe we have incorrectly structured the transformation, and we should also add better error messages!

I have created issues in our https://github.com/TerriaJS/catalog-converter repo:

For the moment, if you remove the availableStyles properties - you will be able to convert your catalog file.

Cheers,
Nick

@LorenzoStucchi
Copy link
Author

Hi @nf-s, thanks for the reply, I will follow the others issues waiting for the correction.
Our website is still in development, so I will wait.
Thanks for all the work.
Best,
Lorenzo

@LorenzoStucchi
Copy link
Author

For testing, I removed the field availableStyles, but the same errors persist. I understood that the issue was with the field styles, which displayed the same error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants