Latest Contributions by Gert-JanVan_der_Weijden

‎04-14-2010

I posted the second part of this request as parr of my ArcGIS 10 betatesting: ESRI respons: That will be a nice feature to have, but currently it's not planned for ArcGIS 10. Without client side SLD support in ArcMap the use of WFS will be minimal: to slooooow! I can't imagine why it would be hard to implement in ArcMap.

‎04-14-2010

I posted the second part of this request as parr of my ArcGIS 10 betatesting: ESRI respons: That will be a nice feature to have, but currently it's not planned for ArcGIS 10. Without client side SLD support in ArcMap the use of WFS will be minimal: to slooooow! I can't imagine why it would be hard to implement in ArcMap.

‎03-09-2010

Last minute request (when is RC1 due?) for extra functionality: It would be usefull to include the mxd properties in the PDF metadata (XMP) when exporting to PDF. technically simple, as the arcpy module already makes this possible: import arcpy pdfDoc = arcpy.mapping.PDFDocumentOpen(r"C:\Temp\ParcelAtlasOverview.pdf") pdfDoc.updateDocProperties(pdf_title="Atlas Overview", pdf_author="ESRI", pdf_subject="Map Book", pdf_keywords="Atlas; Map Books", pdfDoc.saveAndClose() del pdfDoc For my not so python/arcpy-minded users it would be nice to include this in the standard user interface To be extended with: - lastsavedate, - lastsavedby, - arcgis version/build, - mxd name + path and even: - data sources of used layers and finally (perhaps already ArcGIS 13 by then): - metadata of datasources used That would make a perfect archiving system, not depending on ArcGIS versions, not depending on the availability of datasources!

‎02-08-2010

I would like to see support for client side SLDs (with WMS-services) in ArcMap. until now (including beta2) only server side SLDs are supported (in layer properties for an WMS (sub-)layer, at the tab "styles". An option "custom" that would change the URL textbox in this dialog to a read/write state could possible do the trick. For ArcGIS Server 9.3 some fine samples of the use of a external SLD are shown at: http://webhelp.esri.com/arcgisserver/9.3/java/index.htm#wms_sld_samples.htm#polygon_overlaps For on of the samples I made a version with a client side SLD The original is at: http://sampleserver1.arcgisonline.com/ArcGIS/services/Specialty/ESRI_StatesCitiesRivers_USA/MapServer/WMSServer?VERSION=1.3.0&REQUEST=GetMap&CRS=CRS:84&BBOX=-178.217598,18.924782,-66.969271,71.406235&WIDTH=765&HEIGHT=360&LAYERS=0,0&STYLES=,overlaps&EXCEPTIONS=application/vnd.ogc.se_xml&FORMAT=image/png&BGCOLOR=0xFFFFFF&TRANSPARENT=TRUE&SLD=http://sampleserver1.arcgisonline.com/arcgis/wms/slds/polygon_overlaps.xml My adjusted version (with a SLD at my own site is at: http://sampleserver1.arcgisonline.com/ArcGIS/services/Specialty/ESRI_StatesCitiesRivers_USA/MapServer/WMSServer?VERSION=1.3.0&REQUEST=GetMap&CRS=CRS:84&BBOX=-178.217598,18.924782,-66.969271,71.406235&WIDTH=765&HEIGHT=360&LAYERS=0,0&STYLES=,overlaps&EXCEPTIONS=application/vnd.ogc.se_xml&FORMAT=image/png&BGCOLOR=0xFFFFFF&TRANSPARENT=TRUE&SLD=http://geo.sohosted.com/sld/polygon_overlaps.xml

‎02-03-2010

A known bug since 9.3 SP1 (NIM045522): Data Interoperability will index all features before displaying the geometry of a WFS. This takes a long time when the WFS references a large dataset. This behaviour is still present in 10. Or often even worse: The indexing simply finishes with an error "Error indexing <wfs name>.fdl" The latter for instance with the "Nieuwe kaart van Nederland (New map of the Netherlands): http://webservice.nieuwekaart.nl/cgi-bin/nkn?request=GetCapabilities&service=WFS&version=1.0.0 Gert-Jan

‎02-03-2010

To be honest, I didn't. I'm so much used to DS Mapbook where all the Mapbook/DDP functionality is within the Mapbook dialogs, that I forgot to check others dialogs for DDP related functionality. Thumbs up! Both the dynamic queries and the clipping functionality fullfill my needs. Especially the "exclude layers" option in the latter is very nice. One suggestion: for easy reference it would be usefull to see the Definition Query and the Page Definition Query in one dialog (instead of a subdialog for the Page Definition). Will install beta2 ASAP and continue testing DDP Well, some beta2 experiences: Page Definition Queries The "Page definition query" dialog is unfortunately still a subdialog of the "Page Def" dialog. It also would be usefull to be able to see (read-only!) in the Page Def dialog what the actual field name is that has been chosen as "data driven page" field (and perhaps even some sample values). Clipping the data frame (to be found at data frame properties) As an addition to the "exclude layers" and the "border symbology" options I would like to suggest to more options: 1. An option to mask the part of the data frame outside the clip area with a semi-transparent fill (with an option to adjust the % transparancy); 2. An option to buffer the outside of the clip area on-the-fly: this shows the excluded layers for instance for a just the first 2 miles distance outside the clip area; You might foresee my next wish: a combination of 1 and 2 with the option to let the transparancy range from 100% at the clip border to 0% (opaque) at the "2 mile border" Gert-Jan

‎02-01-2010

Gert, Have you looked into using Page Definition Queries or data frame clipping? Using Page Definition Queries Clipping the Data Frame Tom To be honest, I didn't. I'm so much used to DS Mapbook where all the Mapbook/DDP functionality is within the Mapbook dialogs, that I forgot to check others dialogs for DDP related functionality. Thumbs up! Both the dynamic queries and the clipping functionality fullfill my needs. Especially the "exclude layers" option in the latter is very nice. One suggestion: for easy reference it would be usefull to see the Definition Query and the Page Definition Query in one dialog (instead of a subdialog for the Page Definition). Will install beta2 ASAP and continue testing DDP

‎01-08-2010

Two suggestions for a better way to deal with environment settings (hoped 9.4 would already have it...): 1. In order to distinguish between general settings, model settings and command settings a visual distiction would be nice, e.g general settings in bold, model settings in italic, command settings in a normal font. (a difference in colro: black/red/grey) could also do but is hard to distinguish for the colorblind users); 2. In the environment settings window for a singe tool only the relevant settings have to be shown: e.g. in the feature to raster tool only some 13 settings are relevant. So why show all the other 100+ ones?

‎12-18-2009

mgrossman;2770 wrote: Andrew, Thanks for the extensive feedback and good analysis. Here are my comments and recommended solutions: [INDENT] There's a really simple arcpy.mapping python script that does exactly this. Copy it from the help, paste into notepad, save as a ".py" and run it from the Python Window. Incidentally, this is also a really great intro to the world of arcpy.mapping scripts, which can be used to create complete map books exported to any format you want. [/INDENT] No doubt about the simplicity of this pythonscript, but I have quite a number of colleagues who don't want to know about the existance of Python at all (and to admit: I don't want them to know about Python as well. Data Driven Pages are valuable to "out-of-the-box" ArcGIS Desktop users

‎12-06-2009

The data driven pages as implemented in 9.4 are too basic to meet my 21st century requirements. The identifier frame as available in DS Mapbook is a minimal requirement. Dynamic queries as implemented in MPS Atlas and in NW Mapbook are highly wanted as well. These type of queries are required to prevent overlapping pages from showing information from adjacent pages. I realize that this discussion is also about what functionality to include in core arcgis and what to include in an extension (MPS Atlas). Gert-Jan http://www.gisnederland.nl

‎12-06-2009

Although I can imagine some technical reasons it is very non-intuitive to add WFS server in a very different way (by adding an Interop connection) than a WMS or WCS server ("add GIS server"). Knowing that in ArcToolBox contains a "WFS to feature class"-tool already exists it can't be that hard to implement an "add WFS connection" directly in ArcCatalog. (preferably with some modifications to the interface of this tool: why do I have to type the "service=WFS", "request=getcapabilites"and version="1.x.x" myself?) Because of this difference the way of configuring a proxy server is different for WFS servers, although the manual says: "When configuring a proxy server, all Internet connections to GIS servers (both ArcGIS and ArcIMS servers) will utilize this proxy server". That's ArcGIS and ArcIMS indeed, but what about OGC? Gert-Jan www.gisnederland.nl

Online Status	Offline
Date Last Visited	‎11-11-2020 02:23 AM

My Ideas

Latest Contributions by Gert-JanVan_der_Weijden

Re: SLD Support-.MXD/AGServer

Re: SLD Support-.MXD/AGServer

feature request: export to pdf with metadata

client-side SLD support in ArcMap

Error indexing WFS Service.fdl

Data driven pages: identifier frame and dynamic queries

Data driven pages: identifier frame and dynamic queries

Environment Settings: more specific

Data Driven Pages - Still have a way to go

Data driven pages: identifier frame and dynamic queries

"Add WFS" in "GIS servers" instead by Interop