Learn about recent changes to the ArcGIS Urban API. The release date is February 22, 2023.
What's new
This section provides a summary of the most important changes in this release.
- The GraphQL Playground has been replaced with GraphiQL.
- An
Opt
directive which enables the use of experimental features has been added.In - Various descriptions have been improved.
Schema changes
This section describes new features, improvements, and changes made to the Urban API schema.
The Develop
field on Parcel
was renamed to Demolish
:
- Input field
Demolish
was added to input object typeCreate
Parcel Attributes Input - Input field
Demolish
was added to input object typeUpdate
Parcel Attributes Input - Field
Demolish
was added to object typeParcel
Attributes - Field
Parcel
is deprecated (Removal date: 2024-02-28). Use theAttributes. Develop Demolish
field instead.
Other additions were introduced:
- Directive
requires
was addedOpt In
Bug fixes
- Fixed a bug where Urban model creation would fail for trial organizations.
Deprecations
The Locked
field on Branch
, Indicator
, Plan
and Project
has been deprecated:
- Field
Branch
is deprecated (Removal date: 2024-02-28). No longer supported.Attributes. Locked - Field
Indicator
is deprecated (Removal date: 2024-02-28). No longer supported.Attributes. Locked - Field
Plan
is deprecated (Removal date: 2024-02-28). No longer supported.Attributes. Locked - Field
Project
is deprecated (Removal date: 2024-02-28). No longer supported.Attributes. Locked
The Develop
and Show
fields on Parcel
have been deprecated:
- Field
Parcel
is deprecated (Removal date: 2024-02-28). Use theAttributes. Develop Demolish
field instead. - Field
Parcel
is deprecated (Removal date: 2024-02-22). This field is no longer used. After improving the zoning workflow in the Urban web app, manually turning envelopes on and off for individual parcels will no longer be available.Attributes. Show Zoning Envelopes
Upcoming breaking changes
Changes scheduled for 2023-10-25
The default value for the async
argument on create
and create
will be changed from false
to true
.
This is a potential breaking change for clients that do not explicitly specify the async
argument. Specify the async
argument explicitly to prevent your application from breaking. It is strongly recommended to set async
to true
, as the async
option will not be supported in the long-term future.
Use the following operations to create a new urban model or urban design database using the async
parameter.
- Create a new urban model using the
create
mutation and specifyUrban Model async
:: true
mutation {
createUrbanModel(
title: "URBAN_MODEL_NAME",
folderId: "FOLDER_ID"
async: true
)
}
The response should look something like this:
{
"data": {
"createUrbanModel": "96de6000c21c48bf87707154b711e7e5"
}
}
- Periodically check the status of the urban model, for example each 10 seconds:
query {
urbanModel(urbanModelId: "96de6000c21c48bf87707154b711e7e5") {
upgradeInfo {
upgradeStatus
}
}
}
The response tells you if the urban model is ready or not:
{
"data": {
"urbanModel": {
"upgradeInfo": {
"upgradeStatus": "InProgress"
}
}
}
}
Wait for the upgrade
to become Ready
. Now your urban model is ready to be used.