You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
where it just throws the following error:
Could not parse arcgis buffer. Please check the url you requested. (mapbox-gl-arcgis-featureserver.esm.js:297 )
I think this might be due to some problem with the data on that service and the decoding of the 'pbf' format, but I don't think I can easily get that checked / fixed with the provider / maintainer of that service, particularly without more specific details on the exact cause of the problem.
I am curious if it would be possible to force the calls to this endpoint to use geojson format instead of pbf, and if that wouldn't have the same issue with parsing, but there doesn't seem to be an option / parameter I can pass for that, or if you could maybe have more insight on why this pbf parsing is failing and how that could be fixed (at the source).
I think I still have the fallback option of using that layer as a WFS service, but that is a bit more convoluted to implement so I would rather stick with this FeatureServer / MapServer approach if possible.
The text was updated successfully, but these errors were encountered:
Hi, I have an implementation of Mapbox using this package where I can load features from a FeatureServer without issue (i.e.: https://basisregistraties.arcgisonline.nl/arcgis/rest/services/BGT/BGT_objecttypen/FeatureServer/4 ).
I read in the docs that it should also support MapServer URLs, however I am having issues with a specific service I need to use:
https://diensten.rotterdam.nl/arcgis/rest/services/SB_Infra/Container/MapServer/0
where it just throws the following error:
Could not parse arcgis buffer. Please check the url you requested. (mapbox-gl-arcgis-featureserver.esm.js:297 )
I think this might be due to some problem with the data on that service and the decoding of the 'pbf' format, but I don't think I can easily get that checked / fixed with the provider / maintainer of that service, particularly without more specific details on the exact cause of the problem.
I am curious if it would be possible to force the calls to this endpoint to use geojson format instead of pbf, and if that wouldn't have the same issue with parsing, but there doesn't seem to be an option / parameter I can pass for that, or if you could maybe have more insight on why this pbf parsing is failing and how that could be fixed (at the source).
I think I still have the fallback option of using that layer as a WFS service, but that is a bit more convoluted to implement so I would rather stick with this FeatureServer / MapServer approach if possible.
The text was updated successfully, but these errors were encountered: