topic Re: Domain values on fields not coming through to Open Data in ArcGIS Hub Questions

Domain values on fields not coming through to Open Data

MalcolmJ — Mon, 22 Dec 2014 23:44:13 GMT

I have noticed that fields with a domain are not bringing the domain description fields through to the open data site.

So I have a layer with a few domain fields. One field has a text coded values domain. E.g. the code is "Prohibited" and the Description is "Dogs NOT Allowed". In webmaps etc the field will display as Dogs Not Allowed as I would expect. In Open Data it displays Prohibited.

Same on another field which is using short integer coded values. Field values come through open data as 1, 2, etc instead of 'One way',

'Two way' etc.

Is this a issue with open data or is there something I need to change somewhere in order to bring through the domain values?

I am accessing the data through the Open Data site using a feature service in ArcGIS Server 10.2.2. Underlying data is stored in SDE in SQL server.

Thanks

Re: Domain values on fields not coming through to Open Data

MalcolmJ — Sun, 11 Jan 2015 22:26:06 GMT

Anyone else had the same issue? Or is it just me?

If its the same for everyone, I would like to know whether its something that I can change on my end (to see the domain descriptions in open data instead of the field code values) or if its something that has to change in the open data configuration/code?

Thanks

Re: Domain values on fields not coming through to Open Data

ChristopherBoland — Mon, 12 Jan 2015 13:51:08 GMT

I'm currently not publishing out data with domains. I'll give it a try and see what happens.

In any case, I'm interested in the outcome of this issue.Andrew Stauffer‌

Re: Domain values on fields not coming through to Open Data

City_of_MorgantonNC — Tue, 03 Feb 2015 14:23:51 GMT

I use domains heavily in my data, so this is a big issue for me. I was looking into setting up an open data site today, but the lack of domain support stopped me in my tracks.

Re: Domain values on fields not coming through to Open Data

TimMinter — Wed, 04 Feb 2015 19:14:36 GMT

yes, same here. no domains.

Re: Domain values on fields not coming through to Open Data

MalcolmJ — Tue, 17 Feb 2015 19:28:39 GMT

If anyone from the Open Data team is reading this, are domains likely to be supported in Open Data anytime soon?

Re: Domain values on fields not coming through to Open Data

AndrewTurner — Wed, 18 Feb 2015 13:52:49 GMT

Hi Malcolm (and everyone). Can a few of your share the services you are using which have good domain examples? It helps to test with your specific data to ensure we're building it correctly.

Thanks!

Andrew

Re: Domain values on fields not coming through to Open Data

C_EHoward — Wed, 18 Feb 2015 15:42:41 GMT

RTDC/Traffic_Counts (MapServer) is one example I have that uses several domains

Re: Domain values on fields not coming through to Open Data

MalcolmJ — Wed, 18 Feb 2015 19:08:35 GMT

This layer has domains on several fields

Layer: Walking and Cycling Tracks (ID: 49)

Re: Domain values on fields not coming through to Open Data

MalcolmJ — Tue, 24 Feb 2015 22:39:46 GMT

Any update on this? We are looking to release our Open Data site to the public soon and not having domain values coming through is going to limit the amount of datasets we make available.

Re: Domain values on fields not coming through to Open Data

DanielFenton1 — Thu, 26 Feb 2015 19:32:55 GMT

Hi Malcolm this is in our backlog and we will get to it but I cannot give a timeline yet. Sorry I can't give more information right now.

Re: Domain values on fields not coming through to Open Data

C_EHoward — Thu, 26 Feb 2015 19:36:01 GMT

Are there any recommendations on how to manage until this important functionality is added?

Re: Domain values on fields not coming through to Open Data

DanielFenton1 — Thu, 26 Feb 2015 19:45:16 GMT

Hi C E, you could use a string field instead of a coded field. Instead of those codes just put the actual values in their place.

Re: Domain values on fields not coming through to Open Data

C_EHoward — Thu, 26 Feb 2015 19:47:15 GMT

thanks, yes I know. I was hoping to not have to create dozens more fields just to have values that are already coded and described. an alternative, yes, but not a very realistic one for many

Re: Domain values on fields not coming through to Open Data

DanielFenton1 — Thu, 26 Feb 2015 19:49:23 GMT

Just curious, can you explain why you created these as coded fields instead of strings in the fist place? Was this about maintaining data consistency?

Re: Domain values on fields not coming through to Open Data

C_EHoward — Thu, 26 Feb 2015 19:55:14 GMT

I did not for the most part, I inherited data from several sources/entities that use codes. There are a lot of reasons that they may use codes but I cannot really speculate. I think I remember way back in GDB design 101 that domains and subtypes are even encouraged to be used to manage data/consistency. Of course there was no way knowing which way things would go with data sharing, etc. But my bottom line and expectation is that we should not lose functionality in the name of sharing and using web GIS. Domains and-- even more important to me-- related records-- should not be sacrificed or thought of as 'enhancements'

I appreciate the strides being made by AGO and OpenData. But you (meaning Esri) cannot expect us to all think this is the answer when there are usually more workarounds to get things going. I do not want to have to rely on 3rd party apps/widgets for basic functions.

Re: Domain values on fields not coming through to Open Data

MalcolmJ — Thu, 26 Feb 2015 20:10:38 GMT

That's why we use them, for data consistency.

I did consider creating string fields with the descriptions instead of the codes but dismissed this idea due to the amount of fields and layers we have using domains.

Re: Domain values on fields not coming through to Open Data

MalcolmJ — Fri, 27 Feb 2015 01:03:14 GMT

As a similar item to look at, I've just noticed that if a field name has an Alias, when you download the data it will revert back to the original field name in the downloaded data.

e.g. Layer: Drains (ID: 19)

The field "SecondTier" has an alias name of "Type". It displays as Type when using the Open Data website, but when downloaded displays SecondTier.

Ideally, this should download using the alias field name.

Re: Domain values on fields not coming through to Open Data

AndrewTurner — Fri, 27 Feb 2015 01:48:15 GMT