nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Full support of OGC layers in rich APIs

NicolasPy

The rich APIs (either for flex, silverlight or javascript) should be able to consume, at least, non transactional OGC layers without development... I mean WFS, WMS, tiled WMS

Trouver plus de publications taguées avec

Status: Ouvrir

Réponses

AitorCalero_García

I totally agree! Native support should be included in every rich API.

BernieConnors

Support for OGC WMS, WFS, and WMTS should be standard across all ESRI products and not an after-thought.

GreggHadish

Please add OGC WMS support to ArcGIS Online, and ArcGIS Explorer Online. This would make these tools very useful for organizations that do not have ArcGIS Server.

Yann-EricBoyeau

Because missing the support of WFS, we can not effectively promote the use of ESRI APIs to build webapps for organizations asking for Mashups with OGC compliant mapservices.

This point is very important for users in Europe where Inspire directive defines OGC as the standards for web mapping.

CedricMoullet

WMTS Restful is a must

Joachim_EckboJuell

Should also include support for WCS.

OlavKavli

Should be standard for all ArcGIS platform

DavidBrick

Should also provide simple support for PostGIS spatial as well -- that is WKT, WKB, EWKT, EWKB.

SomeGISGuy

Regarding PostGIS support, non of the browser API's would be able to connect to a PostGIS database (security limitation). In many cases, due to cross domain policies, this wouldn't be possible without a proxy anyway. I believe that you can publish an ArcGIS Server service that pulls directly from the WMS/WMTS/WFS/WCS/etc, so the API's can talk to them via ArcGIS Server. The server would then simply be a 'proxy' for these services.

Btw. WMS and WMTS is natively supported by the client API's at this point.

DominiqueESNAULT

All OGC (WMS/WMTS/WFS/WCS/etc) should be able to consume

LorenzMeyer

If we can deploy a WFS on the server side, it should be also possible to consume it on client side. So I would appreciat to have access to WFS in the Javascript API

JimSomerville

Agree, support for WFS, WMS, tiled WMS should be fully supported in the APIs and desktop.

Better would be for ESRI to standardize ArcGIS Server on OGC endpoints, rather than a custom implementation.

Duarte_Carreira

support for wfs in javascript api is a basic requiremente today.

Agree with MAGISNC:
"Because missing the support of WFS, we can not effectively promote the use of ESRI APIs to build webapps for organizations asking for Mashups with OGC compliant mapservices.

This point is very important for users in Europe where Inspire directive defines OGC as the standards for web mapping."

GaneshSolai_Sambandam

I agree and support this feature to be enabled with ARGIS Javascript api.

DHEERABHATLEELAWUTTICHOKE

All of OGC services should be able to consume in ArcGIS API.

BrunoAvard

This is still a must have!!!!! Nothing has been done since this post was first put up 5 years ago.

Rejoindre la conversation

Connectez-vous pour publier, suivre du contenu, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.