Dashing Through The Snow, With URL And Georeference Data (19 December 2018)

Support for URL Data Type in the New Import & Edit Experience

On tabular datasets, you can select the "data type" used for each field, such as Text, Number, or URL. The URL data type allows you to provide either a URL that is hyperlinked within your dataset, such as https://www.tylertech.com/, or to provide both a URL and a label, so that you could have something like Tyler Technologies

Starting today, the URL data type is now an available data type to select for fields in your tabular dataset using the new import and edit experience. You can provide URLs or URLs with labels, using the formats specified in this knowledge base article.

Additionally, with the support for the URL data type, any dataset that contains that URL type can now be edited through the new import and edit experience, and you can change fields to the URL data type at any time.

Read this Knowledge Base article for more details on how data types work. 

 

Adding and Editing Georeference Fields

Georeference fields (formerly known as location fields) are a great way to help you visualize your tabular dataset with addresses on a map. The georeference field can be set up using either a single column, for example if latitude and longitude are listed together, or as separate fields for address, city, state, and zip.

Previously there was one tab on the left side of the data preview page for "Add Georeference" which was where you both added a new georeference field and edited the existing georeference field. However, this experience wasn't as easy to use in the cases where you might have more than one georeference field. As of today, you can continue to create a new georeference field through the "Add georeference" tab, but you will now edit any georeference field through the column menu icon for that column.

This change should make it easier to manage your georeference field(s) no matter how many you have or what stage of editing you are in.

In addition to this change, we've also removed the default option for hiding the source columns. Before, any column that was used to create the combined georeference field was set to be removed from the dataset as an individual column going forward. However, since many users prefered to maintain the source columns as individual columns in addition to being used in the georeference field, we've now changed the default behavior and all columns will be retained in the dataset. You can still hide or remove any column through the column menu.

Read this Knowledge Base article for more details on how the georeference field works. 

 

Filter Visualizations by Distance from an Address

Georeferenced (location) columns can now be added as filters on visualizations. Once you've added the filter, enter an address in the search field and select the distance from that address you would like to filter by. Now, your chart or map as well as the data table are filtered down to show only rows within the specified radius. This feature is enabled for any kind of visualization, as long as you have a georeferenced column in your dataset. 


Read this Knowledge Base article for more details on how visualizations work. 

 

Small Updates & Bug Fixes 

  • Data imports and edits
    • The flyout that appears on the blue "Publish" button when you are publishing a draft of a new dataset has updated text that better indicates that the dataset will remain private unless you chose to change the visibility, and that you will have a chance to review the changes before it's published.
    • If you are publishing an update to a dataset through the classic working copy edit experience, you will no longer be prompted to re-select the public/private visibility. The visibility will remain the same, and you can continue to make updates to that through the action bar on the dataset.
    • An issue where the classic /edit_metadata page was not retaining dataset descriptions is now fixed.
    • Due to security concerns, we are no longer supporting attachments or non-parseable data files with the .html or .htm extension. If you have a file of that type already uploaded to Socrata, you will need to remove or replace the file before it can be downloaded by other users.
  • ESRI Connector
    • Administrators can now add a "Display Name" to your ESRI Connector that will be displayed only in the Connectors administration page. For example, if you are setting up an ESRI Connector for the Department of Parks & Recreation, you could name it "City of Evergreen Department of Parks & Rec".
    • Additional performance and reliability improvements were made to the connector, so your data stays up to date without errors.
  • Datasets that contain more than one georeference/location column no longer have an export option for shapefile, geojson, kml, or kmz. These datasets can still be exported as tabular data such as CSV or CSV for Excel.
  • When adding collaborators or updating the permissions on a Perspectives page, the scrollbar for the Menu Panel will no longer render in front of the modal.
  • In Open Performance, goal pages no longer overlap with the branded header. Likewise, while editing a goal, the goal editor header no longer overlaps with the goal content.

 


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

0 comments

Article is closed for comments.