We Are Here To Help

Follow

Open Data Release Notes for 8/8/2016 - New Catalog Connector for ArcGIS Server, Instant Dataset column metadata edits, DataSync 1.7.2

CATALOG CONNECTOR FOR ArcGIS SERVER

As part of our commitment to continually updating and improving the Socrata platform, today we released a new feature to help customers share their geospatial data more easily through their Open Data Portal.

A significant portion of data released to the public comes in the form of geospatial data. Many customers use ArcGIS as their primary tool to author and manage their geospatial assets. As a result, many Socrata customers have expressed a desire to make their geospatial data easier for citizens to find alongside their other open data resources.

With the release of Socrata’s new Catalog Connector for ArcGIS Server, administrators and publishers now have the ability to connect a public ArcGIS server to their Socrata catalog and selectively federate the layers to include in their Socrata catalog as external datasets. These federated layers will then become searchable and discoverable within the Open Data Portal catalog.


The Catalog Connector for ArcGIS Server is available on all Open Data sites.  

Read this Knowledge Base article for more details on how the Catalog Connector for ArcGIS Server works.

 

INSTANT DATASET COLUMN METADATA EDITS

Publishers can now update column metadata information of a Dataset without creating working copies. This allows publishers to easily change column Names, Descriptions and Formatting settings so they can keep it up-to-date.  

Changing the data type or updating data still needs a working copy. Read this Knowledge Base article for more details on how to update column metadata.

DATASYNC 1.7.2 RELEASED

DataSync 1.7.2 is now available on https://socrata.github.io/datasync/. This minor release fixes the following issues:

  • A previous issue with the 'Trim Whitespace' checkbox under Map Fields was fixed such that users can now specify whether incoming data uploaded via DataSync needs to be trimmed of whitespace. Comparisons between incoming data and server-side data will always be whitespace sensitive.
  • Setting a custom separator now re-evaluates the fields to be mapped.
  • Empty fields in CSVs get converted to null instead of empty string ("").


Check out our other Product News, and give us a shout at support@socrata.com with questions or ideas.

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

Powered by Zendesk