|
IDEA
|
Hi Peoples, In ArcGIS Pro I can export a Layout to Tiff, but according to the help it is not possible to do this with a world file or as a GeoTiff Export a Map or Layout : For maps, choose whether to generate a World File. The world file is used to contain georeference information so the image export can be used as raster data in ArcGIS Pro or other GIS applications. This option is unavailable for 3D view and layout exports. I note this is the same with ArcMap - unless you purchase the additional Production Mapping extension Export Layout to GeoTiff Esri Production Mapping allows you to export a page layout view to GeoTIFF. GeoTIFFs are TIFF files that contain spatial reference information. It would be good to have this functionality in the standard product. Cheers, Mark
... View more
01-23-2017
08:48 PM
|
0
|
0
|
5144
|
|
POST
|
Hi Peoples, In ArcGIS Pro I can export a Layout to Tiff, but according to the help it is not possible to do this with a world file or as a GeoTiff Export a Map or Layout : For maps, choose whether to generate a World File. The world file is used to contain georeference information so the image export can be used as raster data in ArcGIS Pro or other GIS applications. This option is unavailable for 3D view and layout exports. I note this is the same with ArcMap - unless you purchase the additional Production Mapping extension Export Layout to GeoTiff Esri Production Mapping allows you to export a page layout view to GeoTIFF. GeoTIFFs are TIFF files that contain spatial reference information. It would be good to have this functionality in the standard product. Cheers, Mark
... View more
01-23-2017
07:50 PM
|
0
|
3
|
5306
|
|
POST
|
Hi Peoples, There are a number of methods one can use to publish raster datasets to ArcGIS Server. One method is to simply add the raster datasets to a map document, and publish the map document. The layers in the mxd simply reference raster data sources. This is what we have done with one of our services that contains historic data. When this method is used, I cannot add an individual layer from the server to a web map in AGOL. One can do this when the data source is feature class, but it does not appear to support when the data source is a raster. The dialogue that appears states : Error The layer is not supported and can not be added to the map. Why is this the case? I did note I can add the entire Map Service to the web map (as opposed to individual layers). Cheers, Mark
... View more
01-23-2017
07:13 PM
|
0
|
9
|
5500
|
|
IDEA
|
sdelayer -o describe_long : Gives information on a layer such as the current spatial index, the layerID, system units etc that cannot be found through ArcCatalog. Create a tool that returns all the information about a layer, so you don't have to go looking in the SDE user system tables. ArcSDE 10.2 Layer Administration Utility ----------------------------------------------------- Layer Description ....: <None> Table Owner ..........: CUSTODIANS_AGENCY Table Name ...........: OVG_VISTAS_REVAL Spatial Column .......: SHAPE Layer Id .............: 2237 SRID .................: 2 Auth SRID.............: 3857 Minimum Shape Id .....: 1 Offset ...............: falsex: -20037700.000000 falsey: -30241100.000000 System Units .........: 10000.000000 Z Offset..............: 0.000000 Z Units ..............: 1.000000 Measure Offset .......: <None> Measure Units ........: <None> XY Cluster Tolerance .: 0.001 Spatial Index ........: parameter: SPIDX_GRID,GRID0=4000,FULL exist: Yes array form: 4000,0,0 Layer Envelope .......: minx: 16011558.40080, miny: -5349578.14150 maxx: 16528928.07960, maxy: -4751324.92700 Entities .............: nac+ Layer Type ...........: Extended SQL Type/ST_GEOMETRY Creation Date ........: 08/11/16 10:45:08 I/O Mode .............: NORMAL Autolocking ..........: Enabled Precision.............: High User Privileges ......: SELECT, UPDATE, INSERT, DELETE Coordinate System ....: PROJCS["WGS_1984_Web_Mercator_Auxil 174532925199433]],PROJECTION["Mercator_Auxiliary_Sphere"],P R["Auxiliary_Sphere_Type",0.0],UNIT["Meter",1.0]] Layer Configuration ..: DEFAULTS
... View more
12-14-2016
07:16 PM
|
0
|
1
|
862
|
|
IDEA
|
sdetable -o si_stats is a useful command line tool. Build a Geoprocessing tool to report the same things. ArcSDE 10.2 Layer Administration Utility ----------------------------------------------------- Layer 2237 Spatial Index Statistics: Level 1, Grid Size 4000 |-------------------------------------------------------------------| | Grid Records: 105565 | | Feature Records: 92519 | | Grids/Feature Ratio: 1.14 | | Avg. Features per Grid: 42.88 | | Max. Features per Grid: 8022 | | % of Features Wholly Inside 1 Grid: 91.82 | |-------------------------------------------------------------------| | Spatial Index Record Count By Group | | Grids: <=4 >4 >10 >25 >50 >100 >250 >500 | |---------- ------ ------ ------ ------ ------ ------ ------ ------ | | Features: 92225 294 98 20 8 2 0 0 | | % Total: 100% 0% 0% 0% 0% 0% 0% 0%| |-------------------------------------------------------------------|
... View more
12-14-2016
07:05 PM
|
1
|
0
|
704
|
|
IDEA
|
sdetable -o si_stats is a useful command line tool. Build a Geoprocessing tool to report the same things. ArcSDE 10.2 Layer Administration Utility ----------------------------------------------------- Layer 2237 Spatial Index Statistics: Level 1, Grid Size 4000 |-------------------------------------------------------------------| | Grid Records: 105565 | | Feature Records: 92519 | | Grids/Feature Ratio: 1.14 | | Avg. Features per Grid: 42.88 | | Max. Features per Grid: 8022 | | % of Features Wholly Inside 1 Grid: 91.82 | |-------------------------------------------------------------------| | Spatial Index Record Count By Group | | Grids: <=4 >4 >10 >25 >50 >100 >250 >500 | |---------- ------ ------ ------ ------ ------ ------ ------ ------ | | Features: 92225 294 98 20 8 2 0 0 | | % Total: 100% 0% 0% 0% 0% 0% 0% 0%| |-------------------------------------------------------------------|
... View more
12-14-2016
07:05 PM
|
1
|
0
|
457
|
|
POST
|
Hi Peoples, Summary: If you are unfortunate enough to create a feature class where the aliases for two fields are the same, or there is an alias that is the same as another field name [thus the table appears to have two fields of the same name] the service will publish to ArcGIS Server – unless you have WFS capability enabled – in which case it will fail with no real error message. Description: First off: It is not possible to have two fields the same name – the database will not allow it, and you cannot do this in ArcCatalog In ArcCatalog, it is possible to have two fields with the same alias name – (yeh I know - you should not do it, but mistakes happen) In ArcCatalog, it is possible to have a field alias equal to another field name (thus the table appears to have two fields of the same name) – this should not be allowed If there is a field alias equal to another field, when the layer is added to a document and is published to ArcGIS Server it will publish – but if the WFS capability is added, the publishing will fail [ without any decent error messages – very difficult to track down]. There have been a number of enhancements logged to improve the error messages, and not allow this sort of thing to occur.
... View more
12-04-2016
08:01 PM
|
0
|
0
|
1355
|
|
POST
|
One option is to use sdetable -o delete to delete the tables, then use ArcCatalog to create a table of the same name, then use ArcCatalog to delete it.
... View more
12-04-2016
07:53 PM
|
0
|
1
|
3803
|
|
IDEA
|
When the Enterprise Geodatabase used to be three tier, with the ArcSDE running, you had the option of shutting it down and restarting. This had the added bonus of stuff used to get cleaned up in the restart. For example, Log File tables that may have been created under a session, but not dropped when a connection terminated abnormally. The same goes for when KEYSET tables are created, or when stay connections may have been around. With the two tier connect - the database is not restarted, and thus these items have a habit of accumulating, and needing to be cleaned up manually. It would be good to have some sort of Restart or Clean up script, that did the same thing the old restart used to do. In a similar fashion, if you have been using and Enterprise Geodatabase (say Oracle) for a number of years, there can be a problem where feature classes may have been created in third party apps, or created in say Oracle Spatial and registered with the Geodatabase, but subsequently removed, but leaves entries in the Geodatabase tables. It would be good to have a Clean geoprocessing tool that reports on the integrity of Geodatabase entries and can clean this up (sort of like a Windows Registry clean).
... View more
11-28-2016
03:35 PM
|
2
|
1
|
802
|
|
IDEA
|
When the Enterprise Geodatabase used to be three tier, with the ArcSDE running, you had the option of shutting it down and restarting. This had the added bonus of stuff used to get cleaned up in the restart. For example, Log File tables that may have been created under a session, but not dropped when a connection terminated abnormally. The same goes for when KEYSET tables are created, or when stay connections may have been around. With the two tier connect - the database is not restarted, and thus these items have a habit of accumulating, and needing to be cleaned up manually. It would be good to have some sort of Restart or Clean up script, that did the same thing the old restart used to do. In a similar fashion, if you have been using and Enterprise Geodatabase (say Oracle) for a number of years, there can be a problem where feature classes may have been created in third party apps, or created in say Oracle Spatial and registered with the Geodatabase, but subsequently removed, but leaves entries in the Geodatabase tables. It would be good to have a Clean geoprocessing tool that reports on the integrity of Geodatabase entries and can clean this up (sort of like a Windows Registry clean).
... View more
11-28-2016
03:35 PM
|
3
|
1
|
1344
|
|
POST
|
... As it turns out - it has not changed. The REST user is the one that gets written to the editor tracking fields.
... View more
11-15-2016
07:46 PM
|
0
|
0
|
2493
|
|
POST
|
Hi Russ, Has this changed recently? We have secured services from ArcGIS Server that require a username and password to connect to the REST endpoint to obtain a token. As you indicated - the token user was the name that was written to the editor tracking layer with Collector - not the AGOL user. Testing today would indicate the AGOL user name is now written into editor tracking field. Cheers, Mark
... View more
11-15-2016
04:20 PM
|
0
|
2
|
2493
|
|
POST
|
Hi Vince, We haven't chatted for a while. I noted you mention: I strongly discourage creation of user-schema geodatabases because they don't provide the isolation that they purport to. Our Delivery database is 99% simple read only feature classes. There are one or two feature classes that are registered as versioned. We are considering placing the versioned data into a user-schema geodatabase with the thought that it would make compress back to state zero easier, and thus make management of the instance more efficient. Ie we would not have to kick all the users off the database to do a successful compress back to state zero – just the schema user. Thoughts? ... Are we overthinking this? Cheers, Mark
... View more
08-25-2016
05:54 PM
|
1
|
1
|
2467
|
|
POST
|
Hi Alex, All good once I fixed the TNS. I just like to place this sort of information into the forum to help other people out should they come across the issue. Cheers, Mark
... View more
08-24-2016
09:53 PM
|
0
|
0
|
3392
|
|
POST
|
Hi Peoples, When I access a feature class in an Enterprise Geodatabase that is not registered as versioned – will the version tree and state tree effect performance? Our PROD database is 99% simple read only feature classes. There are one or two feature classes that are registered as versioned. We are considering placing the versioned data into a user-schema geodatabase with the thought that it would make compress back to state zero easier, and thus make management of the instance more efficient. Ie we would not have to kick all the users off the database to do a successful compress back to state zero – just the schema user. … or are we overthinking this? Cheers, Mark
... View more
08-24-2016
09:52 PM
|
0
|
2
|
1806
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 05-17-2022 04:39 PM | |
| 1 | 05-09-2023 08:11 PM | |
| 5 | 09-13-2022 03:18 PM | |
| 1 | 09-12-2022 06:55 PM | |
| 1 | 05-31-2022 10:13 PM |
| Online Status |
Offline
|
| Date Last Visited |
2 weeks ago
|