POST
|
That's odd. I did not personally figure it out, one of my team members did. When he's back in the office later this week, I'll ask him to respond with any insight.
... View more
07-27-2020
01:39 PM
|
0
|
3
|
1075
|
POST
|
Keary, since I posted this question in 2015, we have a workflow set up to use Collector on a Windows 10 laptop. ArcGIS Collector is in the Windows Store for download and we have an AGOL map set up for editing the data and downloading it for offline use in the field.
... View more
07-27-2020
07:50 AM
|
0
|
5
|
1075
|
POST
|
Thank you Klara, for your insight. I will recommend the alert header, however ultimately that will not satisfy our lawyers who insist we need an acknowledged disclaimer that our data won’t be used for commercial purposes and we can’t be held liable otherwise. Looking forward to when something can be implemented to address this need!
... View more
07-10-2019
07:43 AM
|
0
|
1
|
793
|
POST
|
I'm attempting to add a disclaimer pop-up to our Open Data hub. I added the below code to a Text Card per the instructions, but I'm not sure how to get it to pop-up on page load. Apparently javascript code isn't allowed on a Text Card. Has anyone been able to make something like this work on their data Hub? <div class="modal fade" id="myModal" tabindex="-1" role="dialog" aria-labelledby="myModalLabel">
<div class="modal-dialog" role="document">
<div class="modal-content">
<div class="modal-header">
<button type="button" class="close" data-dismiss="modal" aria-label="Close"><span aria-hidden="true">×</span></button>
<h4 class="modal-title" id="myModalLabel">Commercial Purposes Disclaimer</h4>
</div>
<div class="modal-body">
(1) RCW 42.56.070(9) prohibits the release of l....
</div>
<div class="modal-footer">
<button type="button" class="btn btn-default" data-dismiss="modal">I Agree</button>
</div>
</div>
</div>
</div>
... View more
07-08-2019
03:29 PM
|
0
|
3
|
909
|
POST
|
Has anyone implemented some kind of display, perhaps a pop-up, on their Open Data site that requires the user to read a disclaimer and Accept it before accessing the rest of the site? Maybe it would cache a cookie that tracks that acceptance but displays the pop-up on any page of their organization's site if the cookie doesn't exist? If so, can you provide some guidance on how to implement this? Our organization's management is implying we have to shut down access to our data until something like this is implemented. Thanks for any insight!
... View more
06-11-2019
04:27 PM
|
0
|
9
|
1974
|
POST
|
Thank you for your response, Rex! Of course now that I have a chance to revisit this issue this week (I was out of the office last week), it appears to have resolved itself. I did not know about the Clear Workspace Cache tool, but if it crops up again, I'll try that first. To answer your questions: We do a Delete/Append via python script every night on most of our FCs in Published from Production. Both 10.3.1 geodatabases are on the same server. We did try it from another PC, each running differing versions of Windows (10 and 7) and had the same issue. No, the attribute query did not work in Published when that SQL statement was missing -- it failed. I'll mark your comment as answered -- maybe it was a caching issue that cleared up after some time passed -- but reopen if it acts up again.
... View more
05-29-2018
01:54 PM
|
3
|
0
|
310
|
POST
|
I have a feature class in a 10.3.1 SDE (called Production) used for editing and overnight that FC is copied over to another SDE (called Published) for displaying in map services (this is done to avoid locks). However, a recent copy of the FC from the Production SDE in Published has resulted in odd behavior. See the screenshots below. When querying on the Attribute table, the SELECT * FROM doesn't display the table name in the Published data, but does in the Production data. I deleted the FC from Published and had it regenerate a copy from the Production and same behavior. Any ideas what might be causing this or how to fix it?
... View more
05-14-2018
11:07 AM
|
0
|
2
|
386
|
POST
|
That must be what I did wrong -- missed your update. It looks like it works, though it zooms way too far in now, so I'll adjust. Thank you!
... View more
08-17-2017
04:38 PM
|
0
|
1
|
2670
|
POST
|
Thanks guys, just got a chance to dig back in today. I broke the zoom: function zoomTo(response) {
//var parcel = response.features[0];
var parcelExtent = response.features[0].geometry.getExtent().expand(0.5);
view.goTo(parcelExtent);
return (parcel);
}
... View more
08-15-2017
05:15 PM
|
0
|
3
|
2670
|
POST
|
I have some JavaScript that queries for a parcel in a feature layer, successfully, and then zooms to the parcel using view.goTo(). It works great, except it zooms a little TOO close into the parcel. I'd like to have it fully display the parcel on the map, not go too far in. Any ideas? Using ESRI's JavaScript 4.4 API view.then(function() {
var url = urlUtils.urlToObject(document.URL);
//make sure we have parameters
if (url.query) {
var parcelNumber = url.query.PID;
return parcelLayer.then(function() {
var query = parcelLayer.createQuery();
query.where = "PID_NUM = '" + parcelNumber + "'";
query.outSpatialReference = view.spatialReference;
return parcelLayer.queryFeatures(query);
});
}
})
.then(zoomTo)
.then(highlight);
function zoomTo(response) {
var parcel = response.features[0];
//var parcelExtent = response.features[0].geometry.getExtent().expand(0.5);
view.goTo(parcel);
//map.setExtent(parcelExtent);
return (parcel);
} Here is my zoomed map with the code above -- as you can see, it's not showing the full extent of the polygon I need to have zoomed into: Here is a more preferable view one click zoomed out (though I'd rather have the polygon fill the space, but be completely visible in the map): Thanks for any ideas.
... View more
08-14-2017
11:56 AM
|
0
|
8
|
5602
|
POST
|
I am still trying every which way from Sunday to make this work and keep hitting walls. I'm now able to run the query from the REST and here is the JSON result: Here is my code that is failing: var upadalLayers = new MapImageLayer({ url: "http://[myServer]/arcgis/rest/services/EnvironmentalServices/UPadal_MiniMap/MapServer" }); var parcelLayer = new FeatureLayer("http://[myServer]/arcgis/rest/services/EnvironmentalServices/UPadal_MiniMap/MapServer/41", { mode: FeatureLayer.MODE_SELECTION, outFields: ["*"] }); var map = new Map({ basemap: "topo", layers: [upadalLayers, parcelLayer] }) var view = new MapView({ container: "viewDiv", map: map, zoom: 10, center: [-117.42, 47.65] }) var urlParams = urlUtils.urlToObject(document.URL); if (urlParams.query){ var urlParcelIDParam = parseFloat(urlParams.query.PID); selectParcel(urlParcelIDParam); } function selectParcel(urlParcelIDParam) { if (urlParcelIDParam) { var queryParcelsTask = new QueryParcelsTask({ URL: parcelLayer.URL }); var query = new Query(); query.where = "PID_NUM = '" + urlParcelIDParam + "'"; query.returnGeometry = true; query.outFields = "PID_NUM"; queryParcelsTask.execute(query).then(zoomparcel); } function zoomparcel(result) { var AOI = result.features; view.goTo(AOI); } Here is the Developer Tools/F12 result that says nothing about my query, but still doesn't zoom to the parcel -- i get the same results when I throw in Ken's example for the promise: I've tried FeatureLayer.createQuery() or FeatureLayer.queryFeatures() and get nowhere. I've tried converting to JS 3.16, 3.21 and 4.3; I couldn't get the map to even display with the first two and had troubles finding documentation for 4.3. I'm back on 4.4 at the moment. Any other suggestions? I've been told I need to find a way to just select from the existing layer in the map rather than querying, but from all examples, it looks like that's what's being done here with the newer QueryTask library and the REST query is working which I'm trying to emulate in code.
... View more
08-07-2017
05:09 PM
|
0
|
0
|
541
|
POST
|
Hi David, Thank you for the response! I'm still banging my head against a wall with this, even after trying to make your example work with my code. It simply doesn't want to work. I'm considering demoting my JavaScript version back to something where I have .selectFeatures and highlighting, since querying doesn't seem to work with my map service at all even at the REST url. I appreciate the advice you offered!
... View more
07-31-2017
07:11 PM
|
0
|
1
|
541
|
POST
|
Now that I think on this, the JS 3.16 is actually selecting from a feature service. It's using query.where, but not querying the rest endpoint in the same way. I wonder if I need to set up the rest URL differently to allow it to be queried against.
... View more
07-31-2017
11:50 AM
|
0
|
3
|
541
|
POST
|
I see. Thank you. So here's what DT says with JS 3.16, which is working: Here's what DT says with my code in JS 4.4, which is failing to execute: Here is that where clause in the rest endpoint query:
... View more
07-31-2017
11:45 AM
|
0
|
4
|
541
|
POST
|
Here's what the app that is querying properly in JS 3.16 shows for that query URL: http://[myServer]/arcgis/rest/services/[myMapServiceName]/MapServer/0/query?f=json&where=PID_NUM%20%3D%20'55203.0405'&returnGeometry=true&spatialRel=esriSpatialRelIntersects&outFields=*&callback=dojo.io.script.jsonp_dojoIoScript3._jsonpCallback
... View more
07-31-2017
11:19 AM
|
0
|
0
|
541
|
Title | Kudos | Posted |
---|---|---|
3 | 05-29-2018 01:54 PM |
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:23 AM
|