|
POST
|
Brian O'keefe - have there been any recent changes to the server? It appears requests are sometimes returning a web adaptor error:
... View more
04-17-2018
09:00 AM
|
0
|
0
|
1419
|
|
POST
|
Hi Jacqueline, would it be possible to share the layer where you're seeing this behavior? It sounds like something in the style json is causing the page to fail to load completely. If it's doable to share but needs to remain private - you can invite my account to a group. The username is cwwhitmore. Thanks, Chris
... View more
12-15-2017
04:08 PM
|
0
|
0
|
704
|
|
POST
|
Hi Charles, Is this a publicly shared layer? If so, possible to provide the link? Thanks, Chris
... View more
12-13-2017
02:00 PM
|
0
|
1
|
719
|
|
POST
|
Hi Erik, we have a patch going out tonight to resolve this issue. Sorry for the trouble. Thanks, Chris
... View more
12-08-2017
01:04 PM
|
2
|
0
|
1001
|
|
POST
|
Hi Malcom - answers inline below: I don't actually need to display all the field attributes, but if I cut it down to just one attribute field configured in the pop-up, then I still get no information returned. It looks like all fields are included in the query request even if only one field is configured...looking into this to see if this expected (and why). Would it help if I used shortened field aliases for the feature class, in the mxd underpinning the service? (and re-published) Or renamed the feature class in the mxd to a shorter name? I don't think either of these changes would help in this case. You could look at setting a definition expression to hide fields you wouldn't want in the popup (Shape_length, Shape_area for ex). Also how do you obtain the query code thats being sent to the server (that you've included in your reply above)? I used the browser's developer tools to capture the network traffic between the browser and the service. In my case, I used Chrome - you can access the developer tools by pressing CTRL+ SHIFT + i at the same time. There will be a series of tabs..click the network tab and then click on a feature in the map - you should then see the query request being made to the server. It will look something like this: Cheers Chris
... View more
11-01-2017
05:17 PM
|
1
|
1
|
2752
|
|
POST
|
Hi, It appears the server is rejecting the query to fetch the popup. https://mapping.dardni.gov.uk/arcgisra/rest/services/Test/PFRA2Fluvial/MapServer/0/query?f=json&returnGeometry=true&spatialRel=esriSpatialRelIntersects&maxAllowableOffset=305&geometry=%7B%22xmin%22%3A-694282.2388330628%2C%22ymin%22%3A7306613.19980384%2C%22xmax%22%3A-690613.2614753761%2C%22ymax%22%3A7310282.177161527%2C%22spatialReference%22%3A%7B%22wkid%22%3A102100%2C%22latestWkid%22%3A3857%7D%7D&geometryType=esriGeometryEnvelope&inSR=102100&outFields=OBJECTID%2CEasting%2CNorthing%2CFrismID%2CArea_Flooded%2CNonResNearFP_IC%2CNonResNearFP_IC_Depth_Min%2CNonResNearFP_IC_Depth_Mean%2CNonResNearFP_IC_Depth_Max%2CNonResNearFP_IC_Damage_Min%2CNonResNearFP_IC_Damage_Mean%2CNonResNearFP_IC_Damage_Max%2CNonResNearFP_IC_Damage_Min_Sum%2CNonResNearFP_IC_Damage_Mean_Sum%2CNonResNearFP_IC_Damage_Max_Sum%2CResNearFP_IC%2CResNearFP_IC_Depth_Min%2CResNearFP_IC_Depth_Mean%2CResNearFP_IC_Depth_Max%2CResNearFP_IC_Damage_Min%2CResNearFP_IC_Damage_Mean%2CResNearFP_IC_Damage_Max%2CResNearFP_IC_Damage_Min_Sum%2CResNearFP_IC_Damage_Mean_Sum%2CResNearFP_IC_Damage_Max_Sum%2CProject%2CRes_NonRes_Damage_Min_Sum%2CRes_NonRes_Damage_Mean_Sum%2CRes_NonRes_Damage_Max_Sum%2CSHAPE_Length%2CSHAPE_Area&outSR=102100 The above request is redirected by the server to an error page: http://corporate.nics.gov.uk/nigov-error/ The length of the request is what seems to cause the rejection. It's around 1100 characters in the url parameter which is typically allowed in GET requests. If you're able, check into the configuration at the web tier on the server hosting the service - that's where this seems to be happening. Thanks, Chris
... View more
10-31-2017
02:52 PM
|
0
|
3
|
2752
|
|
POST
|
Hi Thomas, The ArcGIS Online makes POST requests with the GetFeatures parameters included in the body of the request (rather than a GET request with url parameters appended). It appears that the parameters are included correctly in the request but the WFS server is returning a 404 error. If the server is updated to accept POST requests, the layer should work. This is what the request payload looks like: Which appears to return a 404 error: Thanks, Chris
... View more
10-23-2017
05:08 PM
|
0
|
0
|
798
|
|
POST
|
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:
... View more
08-22-2017
09:34 AM
|
1
|
0
|
477
|
|
POST
|
Hi Alessandro, this is a bug in the 4x JSAPI. Should be fixed with the next release (planned for Sept). thanks, Chris
... View more
08-10-2017
09:54 AM
|
1
|
1
|
2208
|
|
POST
|
Hi Devin, the editing types can be updated separately - in the edit dialog, you should see see a button in the lower right titled "Manage". That will open a panel for managing editing types and templates. From there, click the dropdown for each type you want to remove. Once the types are removed, you should see the editing experience reflect which types are available. Thanks, Chris
... View more
08-03-2017
02:31 PM
|
1
|
1
|
1228
|
|
POST
|
Hi Matt - Thanks for the details on the issue with zoom levels; I passed it on the folks working on VTPK authoring in Pro. You should be hearing from Support soon as well - I asked them to follow up on the differences you're seeing with the layers in Pro versus the resulting style on the vector tile layer. Thanks, Chris
... View more
04-24-2017
04:58 PM
|
0
|
0
|
704
|
|
POST
|
ok cool! ignore the second half of my post above then
... View more
04-21-2017
01:18 PM
|
0
|
2
|
4096
|
|
POST
|
For the label offset issue, it looks like it might be an authoring issue when the VTPK was created (as the style json doesn't seem to include the offset) - I'll look into it. But it can be added manually to the style, though: "text-offset" Positive values indicate right and down, while negative values indicate left and up. To the school layers, I added "text-offset": [5, 5], which moved the labels down and to the right. Here's how that looks for the layer (should be able to tweak the other text formatting options to make it look better if necessary): Here's the copy I made with the offset. If you search for "text-offset": [5, 5] in the style json, you can see where it needs to be added in the layout section. https://www.arcgis.com/home/item.html?id=cdabb056851c437b82da19b73b34d086 For the other issue, I seemed to be able to copy the new hosted layer successfully (this is the one I copied: http://linncounty-gis.maps.arcgis.com/home/item.html?id=dd4f63dd42834faabb2823d85f70dab4 ) The resulting layer had download available, etc without any manual tweaking. I do see the same issue on the copied layer though. Mind to try again? Everything seems ok now from what I can tell. Definitely shouldn't need to do any url updates or anything.
... View more
04-21-2017
01:17 PM
|
0
|
0
|
4096
|
|
POST
|
Hi Matt, it looks like there is an issue with parsing certain characters in the layer's style - the '<' and '>' characters aren't being handled correctly when copying the layer (it appears the layer names used to create the vector tile layer have the greater than / less than symbols: "source-layer": "Background, >9k" for ex). This is ultimately what's causing the issue. The workaround is to upload the style json file directly. That will bypass the systems handling of the style json (and subsequently the parsing issue when copying the layer). Attached is the "copied" json you can use to upload on the copied layer (and can be customized however you need first). It'll be easier to use this json rather than downloading directly from the hosted layer. The hosted layer's style has relative urls which won't resolve correctly if directly copied to a different layer (when copying in the map viewer, the viewer handles the updating of the urls to point to the correct resources. the json i posted has the updated urls). I was able to check out the initial layer you posted before it was deleted - it looks like this was the issue for that layer (relative url could not resolve correctly so the layer did not load at all). We'll look into fixing the parsing issue for < and > for the next release. If you need this same fix for other hosted layers (would think so since this one is a test), check out the urls in the attached json. There are three urls that will need to be updated to point to to the original source vector tile layer (effectively hardcoding the urls rather than persisting the relative urls), which hosts all the resources used for copies. Sorry for the hassle. Let me know if you run into issues or if this doesn't make any sense Chris
... View more
04-21-2017
08:08 AM
|
1
|
9
|
4096
|
|
POST
|
Hi Matthew, As you found, only the default value is supported in ArcGIS Online when adding the capabilities url. You can however still add any time value the WMTS supports by using an alternate workflow: When adding a layer from the web, instead of selecting the WMTS option, select the Tile layer option (Screenshot below). With the tile layer option, you can provide the specific time you want to see when inputting the url. Here are a couple examples (same structure as the parameterized url you posted from the capabilities doc): https://gibs.earthdata.nasa.gov/wmts/epsg3857/best/AMSR2_Snow_Water_Equivalent/default/2017-03-01/GoogleMapsCompatible_Level6/{level}/{col}/{row}.png https://gibs.earthdata.nasa.gov/wmts/epsg3857/best/AMSR2_Snow_Water_Equivalent/default/2016-03-01/GoogleMapsCompatible_Level6/{level}/{col}/{row}.png As for native support of dimensions (time and other), no estimate on when support might be added (though I saw you've submitted on the ideas site for future consideration). Thanks, Chris
... View more
04-04-2017
04:42 PM
|
2
|
6
|
4389
|
| Title | Kudos | Posted |
|---|---|---|
| 2 | 11-01-2024 03:09 PM | |
| 2 | 11-06-2024 06:58 AM | |
| 2 | 07-11-2024 09:18 AM | |
| 1 | 02-06-2024 08:21 AM | |
| 1 | 02-01-2024 11:42 AM |
| Online Status |
Offline
|
| Date Last Visited |
04-03-2025
09:40 AM
|