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; } } }

accented letters not recognized by GeocodeService

mihkelhaav

I'm trying to create an address locator to use in an ArcGIS viewer for Flex application. I end up with a locator that does not support accented letters like ö, ä, ü, õ. Doesn't matter wheter I use the service via the Flex application or just query via browser - the locator is unable to process these accents.

I have tried with the feature class in a gdb and shapefile, locator in a gdb and in a folder, setting the gdb-s and locators configuration keywords to DEFAULTS (which is UTF-8), installed ArcGIS 10 SP2 (Desktop, Server) Fullwidth Unicode Characters and Conversion Patch both for my PC and Server. Both are running v10 SP2. Still no luck... 😞

Has anybody a clue what might be the problem?

Thanks in advance,

Mihkel

Find more posts tagged with

Accepted answers

All comments

BradNiemand

Does the locator work in ArcMap?

Brad

mihkelhaav

Does the locator work in ArcMap?

Brad

Yes, works just fine in ArcMap.
It turns out that the problem not only occurs with locators but with other REST services as well: the query URL-s are encoded nicely to UTF-8 but the servers response is what gives errors - all special characters are handled as "?" within GET queries. POST queries containing special characters are handled nicely, but as far as I know the locator services only support the GET method?
Any ideas?

Mihkel

RaviNarayanan

Mihkel,

is this 10.0 or a 10.1 beta server?

mihkelhaav

Mihkel,

is this 10.0 or a 10.1 beta server?

Server version 10.0 SP2.
Does the GET method through a REST service support accented characters in queries at all?

Mihkel

RaviNarayanan

Both GET/POST are supported and we want to understand why this may not be working for your case. Is this a .NET or a Java Server. If this is a Java, can you provide information about the applications server that is used?

mihkelhaav

Both GET/POST are supported and we want to understand why this may not be working for your case. Is this a .NET or a Java Server. If this is a Java, can you provide information about the applications server that is used?

It is an ArcGIS Server 10.0 for the Java Platform SP2 and Tomcat 6.0.32 as the application server. I have to mention that I am not very familiar with configuring Tomcat. So any ideas or tips are more than welcome.

Mihkel

RaviNarayanan

Mihkel,

if the URIEncoding property is set for tomcat HTTP Connector, can you try without this setting?

http://tomcat.apache.org/tomcat-5.5-doc/config/http.html

For example if this is tomcat that is installed with the server check for the URIEncoding property defined for a <Connector> in \ArcGIS\Server10.0\java\manager\service\managerappserver\conf\server.xml

mihkelhaav

Mihkel,

if the URIEncoding property is set for tomcat HTTP Connector, can you try without this setting?

http://tomcat.apache.org/tomcat-5.5-doc/config/http.html

For example if this is tomcat that is installed with the server check for the URIEncoding property defined for a <Connector> in \ArcGIS\Server10.0\java\manager\service\managerappserver\conf\server.xml

The URLEncoding property is set only for the <connector> port 8080 in \Tomcat6.0\conf\server.xml and this has to be UTF-8.
Will setting the URIEncoding for \managerappserver\conf\server.xml <connector> port 8399 or for \managerserver\conf\server.xml <connector> port 8099 affect the processing of GET queries?

Mihkel

mihkelhaav

I managed to get the GET queries to handle accents, but only with secured (https) services. Regular http services still won't handle the accents. Have tried out different configurations for the http port both on Tomcat's and ArcGIS Server Java side, doesn't matter whether the URLEncoding property is set to UTF-8 or not. So, if there are any Tomcat specialists, I'm still interested in getting the damn thing working with regular http.

Mihkel

RaviNarayanan

The URLEncoding property is set only for the <connector> port 8080 in \Tomcat6.0\conf\server.xml and this has to be UTF-8.

Mihkel, Did you try without the URIEncoding property set for the tomcat on port 8080? My previous post assumed the service was accessed via port 8399.

mihkelhaav

Mihkel, Did you try without the URIEncoding property set for the tomcat on port 8080? My previous post assumed the service was accessed via port 8399.

Ravi, in our case the URLEncoding property for the <connector> port 8080 has to be UTF-8 because we have other REST services on the same webserver separate from ArcGIS services that require UTF-8.

RaviNarayanan

Mihkel,

Most likely the setting of URIEncoding to UTF-8 is causing this behavior. if you can isolate the one of the REST services to use to use a different instance of tomcat, you might be able to identify if it works as expected.

Ravi

EzequiasRodrigues_da_Rocha

Mihkel,

Most likely the setting of URIEncoding to UTF-8 is causing this behavior. if you can isolate the one of the REST services to use to use a different instance of tomcat, you might be able to identify if it works as expected.

Ravi

Strange, becouse i have experienced the same problem but locally (in some machines but not in other) using DataExtractorWidget (for Flex 3.6).

Does anyone knows why this happens?

Regards
Ezequias Rocha

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.