POST
|
Heath: It seems that the further we go down this rabbit hole the more difficult this task becomes. I'm wondering if this is something that can be set in ArcGIS Pro before publishing?
... View more
05-27-2019
09:01 AM
|
0
|
0
|
1002
|
POST
|
Heath: Thanks for the response...it's good to know I'm not alone . I am wondering if this is something that may need to be resolved using JavaScript...but that is just a guess on my part.
... View more
05-21-2019
08:20 AM
|
0
|
2
|
1002
|
POST
|
George: This discussion got me thinking about upgrades...and then I discovered that our enterprise geodatabase has never been upgraded. I thought it was automatic when GIS Server was upgraded...apparently not. I'm in the process of upgrading this right now, and when done I will certainly explore the option of updating the compatibility to SQL Sever 2016. I think the reason it was set to 2012 because that was the limitation of that version of enterprise geodatabase...perhaps with an upgrade some of these other issues will go away. I will post the results here. Thanks
... View more
05-07-2019
09:35 AM
|
1
|
0
|
1383
|
POST
|
George: Our network speed here is 10 GB, and although we do have a wireless network this is mainly for consultants and staff using laptops for meetings, and for other mobile devices. My workstation is definitely wired. I'm not sure if I would be allowed to install ArcGIS on our SQL Server machine though...they have learned how some geoprocesses can drag the system down LOL. I have a lot of software installation privileges here, but that is one of the more guarded servers. I can ask though.
... View more
05-06-2019
09:19 AM
|
0
|
2
|
1383
|
POST
|
Asrujit: Thanks for the help...I think you're right about the File Geodatabase object size...I was just hoping I guess :-). I'm the only one here with ArcGIS on my desktop, but I have not installed it on any other server. We have it installed on a VM in case we have a consultant come here to do periodic work though. Our version of SQL Server is 2016, but I have noticed that our enterprise geodatabase is set to use 2012 (probably because that was the latest setting available in ArcGIS at that time.
... View more
05-06-2019
09:15 AM
|
0
|
0
|
1383
|
POST
|
George: Thanks for the response...most helpful. I had to test this with our IT manager here and it took a little longer :-). We were able to access all of the data in our largest data set (9-million + records) using SSMS, and scroll through it without issue. I also noticed that we only had 12 GB RAM on that server, so we then upped that to 32 GB. Closing either ArcGIS (10.6.1) or ArcGIS Pro (2.3.2) and then relaunching them doesn't help. I did find some online help that indicates that there is an Enterprise Geodatabase setting somewhere that allows one to adjust constrictions, but this had more to do with file size. Apparently the default setting constricts the geodatabase to 1 TB, but can be adjusted to be as much as 256 TB. Our data is nowhere near 1 TB, but I'm wondering if wherever that setting is located if there are other constraints that can also be adjusted (like number of records etc.).
... View more
05-03-2019
01:01 PM
|
0
|
6
|
1383
|
POST
|
I am having some issues with a large data set in our enterprise geodatabase, and would like to learn if this is simply a limitation of the technology, or if perhaps I have a setting incorrectly applied. I have a large point data set (close to 3.8-million records) that we have been able to successfully use as a stand-alone file geodatabase to create heat maps. I can even create an individual heat map from that one file geodatabase feature class and publish that directly to Portal (10.6.1) from ArcGIS Pro (2.3.2). However, a manager here would like to be able to query the data itself using Portal, and create heat maps based on those queries, and with smaller data sets this does indeed work. However, when I imported that large data set into our enterprise geodatabase (so I could get it ready for publishing), and then opened the attribute table to make sure all of the records were there, I suddenly started to run into ODBC driver connection errors, as per below: I do have other smaller feature classes (linear mostly) that are in the 0.5-million records range and there are no problems opening these attribute tables and populating any of these with all records. The plan is to eventually vector cache this data set to make it less cumbersome to use, but I will cross that bridge when I solve this issue first. So does this ODBC Driver 17 failure mean that the enterprise geodatabase has limitations, or is there perhaps a way I can fix this? I'm also wondering if I could just put this data set into a registered folder on our server and then add it to Portal that way instead. Thanks
... View more
05-03-2019
11:53 AM
|
0
|
8
|
1695
|
POST
|
Luke: Thanks for your advice. I will most definitely give these suggestions a try and see how it works, and post again as soon as I have done this. I have been putting the image into a GDB with success in the past...I just for the life of me couldn't get my head around why something as simple as a clip was not working. The original data are in GeoTIFF, and I used that to successfully create a Mosaic, and a static image as well...it's just the clipping, or masking that seems to be giving me grief. I will plug away at this this morning though. Thanks
... View more
03-11-2019
08:43 AM
|
0
|
0
|
2036
|
POST
|
Vicky: Thanks for the help. I had made a dozen of these templates and for the life of me I could not figure out why this one template was missing the title in Portal. But your suggestion is exactly what it was...I was missing the title code in that one dynamic text box. It's strange how we can sometimes miss the obvious, even when it's right there in front of us . Thanks again.
... View more
03-08-2019
08:29 AM
|
0
|
0
|
893
|
POST
|
Jay: I have 192 original TIFF files that pieced together form our orthophoto. Each TIFF is simply named after the NW corner of a UTM coordinate, so it was fairly simple to find the right TIFF files (there are 9 of them for the area I was trying to clip). Why I cannot clip or export the raster to a new GDB is beyond me. So what I did was create a new Mosaic using those 9 TIFF images, but instead of using an 8-bit unsigned pixel type I used a 64-bit instead, and it works perfectly. The new image is virtually indistinguishable from the original: Now I have a format that I can share with our 3rd party...a clip would have been so much easier though. The one thing that bothers me about Mosaics though is that periodically the Mosaic path gets corrupted, and then one has to fix that, which can be a pain as it doesn't always work. I tried clipping this image, exporting it as a GRID file, and using that Mosaic to New Raster tool, and none of them worked (i.e. they all produced the same coarse imagery as I was experiencing before). It looks like I will have to go with this Mosaic and hope for the best.
... View more
03-07-2019
08:21 AM
|
0
|
0
|
2036
|
POST
|
Jay: Thanks again...this gives me an opportunity to explore a different angle to this problem. I will work on this today and see what happens. The latest version of the clipped images is 1 GB...it's a fraction of the original (10 cm resolution), so if I could share that somehow I would. However, I did take a peek at it using the "Zoom to Source Resolution" and it pretty well substantiates my observation on the coarseness disappearing when zoomed in. The clipped image is to the right of the red line: This is a snapshot of what it looks like when I zoom out to 1:30,000 scale: Thanks again.
... View more
03-06-2019
08:49 AM
|
0
|
0
|
2036
|
POST
|
Jay: Thanks a lot for your time on this...this has me double-checking my entire workflow too, which is a good exercise. The cell size in both original and resulting images are identical (x=0.1, y=0.1), which is a good thing to check as that could have this affect if these were different. I checked the general Environment settings too and those turned out to be the same as default settings when I use the tools in ArcGIS Pro. So I'm pretty sure that there was nothing there that could be affecting my output. I also tried my workflow 3 different ways using ArcMap (Raster Clip, Raster Export and Extract by Mask), but all 3 returned the exact same results. In one method I tried using a different compression option, but that too made no difference. Raster Clip using ArcMap in ArcGIS 10.6.1 I had this same issue when I originally created the image from 192 TIFF images, but what ended up resolving that (for some reason) was using JPEG compression (not sure why). That has no effect here though. Interestingly, with exception to the resolution over the water, when I zoom in to a larger scale I cannot see the coarseness anymore...it's only at the smaller scales where this becomes more obvious. This is quite baffling. One would think that one should just be able to clip the image while maintaining the quality of the original image...I wonder what's really going on in the background when I process this image? Original Image I hope this can be resolved...I would hate to quit on this. The source data specs are: The specs on the clipped raster: One question though...could this be a problem because my original raster image was created using JPEG compression? Just a thought. Thanks
... View more
03-05-2019
04:52 PM
|
0
|
3
|
2036
|
POST
|
Jay: Thanks very much for your response...most appreciated. I took a little while to respond because I wanted to try this out a few times to make sure I could replicate your results. I tried processing this clipped imaged 3 different ways using just the default settings, but it sill produced the same grainy coarse results (as per below). This is very frustrating. I tried Clip Raster using my polygon, Copy Raster, and then Clip from Raster Functions using the Export Raster option...all with just the default settings, but nothing seems to change. I'm wondering if there is a default setting somewhere that is overriding my process each time? I say this because no matter what settings I use the results never seem to change regardless of what compression method was selected, which to me seems odd.
... View more
03-05-2019
11:41 AM
|
0
|
5
|
2036
|
POST
|
I have been trying to clip an image using ArcGIS Pro (2.3). I need to send this image to a 3rd party, so it's not going to be used in my system. I am simply trying to convert an ESRI GRID format image into a smaller ESRI GRID format image. I have tried various geoprocessing tools: Extract by Mask Clip (using a polygon) Copy Raster (after using clip in Raster Functions) And have used various compression settings: LZ77 JPEG LZW I also always let the software build pyramids using the -1 option, and have tried setting "no data" to both "0" and "256". I have not changed the projection. None of my methods seem to work and in every case the resulting image appears coarse and no like the original at all. All I want to be able to do is capture a piece of our high-res orthophoto and preserve the original image quality in the resulting image, which sounds fairly straight forward. Because each iteration of my workflow takes about 15 minutes this project is starting to cost me hours...even days. Surely there's a smart way to deal with this, right? Original Image Resulting Image Suggestions? Thank you
... View more
03-05-2019
06:24 AM
|
0
|
10
|
2619
|
POST
|
Fred: That was a great idea...I really thought it would work. I checked the Utility Services in Portal and saw a couple of errors there: 1) the path for the print widget template was outdated, and 2) there was indeed a reference there to the TEST print widget template I want to remove. So I corrected the template path and deleted the entry for the TEST print widget, and then refreshed everything (I even restarted the Portal and GIS Servers), but that one entry in the menu just won't go away, which is intriguing. I'm now thinking what I did when I was building these templates is that at one point I inadvertently saved the TEST PAGX file as another PAGX file, so it is actually referencing a valid print template (i.e. there are now two map templates accessing the same PAGX file). This "might" explain why it won't go away; however, I am at a bit of a loss on how to fix that if everything else has already been deleted. Thanks for your help though...these were all excellent suggestions. I am narrowing this down and I'm sure I will get to the bottom of this. When I do I will certainly update this thread.
... View more
02-19-2019
09:01 AM
|
0
|
0
|
735
|
Title | Kudos | Posted |
---|---|---|
1 | 03-12-2020 12:36 PM | |
1 | 11-12-2019 09:57 AM | |
1 | 02-12-2020 02:57 PM | |
1 | 11-25-2020 11:39 AM | |
1 | 11-18-2020 01:15 PM |
Online Status |
Offline
|
Date Last Visited |
04-30-2023
12:47 PM
|