/
GeoCortex: Map Services and Responsibilities

GeoCortex: Map Services and Responsibilities

Owned by Joel Clark (Unlicensed)
Last updated: Jun 10, 2020

Landing Page

 

BACKGROUND

Back 2 Top

GeoCortex is the map tool that is integrated into the AMANDA software and is central to the City's Integrated Permitting System overhaul. PBCE-IT manages the GeoCortex backend configuration, called GeoCortex Essentials, but the Public Works enterprise GIS team is responsible for the map services it consumes. To better manage GeoCortex, we are going to publish map service changes in 6 month cycles. Remember to publish the change to both the "_Internal" and "_Public" version. The MXDs can be found in PLN on PW-GISAPP1/GEO-APPDEV.

Only list here NEW layers or significant schema or display modifications, do not list small display changes. GIS data updates will routinely update the service when the replica publishes each week.

MAP SERVICES

Back 2 Top

Note the multiple map services that support GeoCortex.


Internal (Server Identity Store Password Protected) Services. All layers should be identical across these:

https://geo.sanjoseca.gov/server/rest/services/PLN/PLN_Geocortex_Internal_PRD/MapServer  A-7 Production GeoCortex Viewer, Internal (City Staff) Only. Has sensitive layers. Password protected. MXD is in PLN folder on PW-GISAPP1.

https://geo.sanjoseca.gov/server/rest/services/PLN/PLN_Geocortex_Internal_TST/MapServer  A-7 Test GeoCortex Viewer, Internal (City Staff) Only. Has sensitive layers. Password protected. MXD is in PLN folder on PW-GISAPP1.

https://geo.sanjoseca.gov/serverdev/rest/services/PLN/PLN_Geocortex_Internal_DEV/MapServer  A-7 Development GeoCortex Viewer, Internal (City Staff) Only. Has sensitive layers. Password protected. MXD is in PLN folder on GEO-APPDEV.

https://geo.sanjoseca.gov/server/rest/services/PLN/PLN_Geocortex_Published/MapServer  A-6 Production GeoCortex Viewer, Internal (City Staff) Only. Has sensitive layers. Password protected. MXD is in PLN folder on PW-GISAPP1. (To be retired)


External (No Password) Services. All layers should be identical across these:

https://geo.sanjoseca.gov/server/rest/services/PLN/PLN_Geocortex_Public_PRD/MapServer  A-7 Production GeoCortex Lite Viewer, A-7 Embedded Maps, Public GIS Viewer Not Yet. External Facing. No Password. MXD is in PLN folder on PW-GISAPP1.

https://geo.sanjoseca.gov/server/rest/services/PLN/PLN_Geocortex_Public_TST/MapServer  A-7 Test  GeoCortex Lite Viewer, A-7 Embedded Maps. External Facing. No Password. MXD is in PLN folder on PW-GISAPP1.

https://geo.sanjoseca.gov/serverdev/rest/services/PLN/PLN_Geocortex_Public_DEV/MapServer  A-7 Development GeoCortex Lite Viewer, A-7 Embedded Maps. External Facing. No Password. MXD is in PLN folder on MXD is in PLN folder on GEO-APPDEV.

https://geo.sanjoseca.gov/server/rest/services/PLN/PLN_Geocortex_Public/MapServer  AGOL Version 1 Public GIS Viewer Only. External Facing. No Password. MXD is in PLN folder on PW-GISAPP1. (To be retired)


WHO MAKES CHANGES?

Back 2 Top

GeoCortex is a one-size fits all solution for many departments. As such, the department, and division within, that owns the GeoCortex layer is the only authority on layer's existence, data content, and how it should be displayed. The owning department can be found by looking at the name of the enterprise geodatabase can in which the layer in question resides. Please use the following boilerplate message to staff who inquire about GeoCortex layer changes. Technical inquiries regarding the interface or the application itself please forward to PBCE-IT.

“Thank you for your request, however, any request to remove or change a layer from the Public GIS viewer / GeoCortex should be discussed with the appropriate Department or Division that the layer represents.  The layers were reviewed and approved for publication by each respective Division or Department at the time of implementation.  The Public GIS viewer / GeoCortex is meant to be a one stop location that residents, developers or engineers can do research on properties. Please make a help desk ticket to GIS Services who will determine the owner of the data layer you wish to change, and will forward the ticket appropriately. Thanks”


BROKEN LAYERS

Back 2 Top

It should go without saying that any changes made to the schema of enterprise data layers will break the downstream map services. Avoid making schema changes (feature dataset, feature class name, field name) to the layers listed below. If schema changes are made, please go through each service MXD, reattach the source data, and republish the services.


CHANGESET v1.1

- To Be Deployed Aug 4th 2020, nine months after the A-7 Go live.

Back 2 Top

  • The GP2040RoadwayTypologies layer in the enterprise should be added under the Geocortex published layers as “General Plan 2040 Designated Streets” and should be located under the General Plan “bucket” (see image). The streets should be characterized similar to the way the they are shown (i.e. color) on the “Transportation Network Diagram” that is part of the General Plan (see PDF). Once published to the GeoCortex layers it should be incorporated into GeoCortex.Add the cone zone to the GeoCortex service SEE TICKET 97844.
  • Add the new vertical asset types = radar signs, flashing beacons, cameras.

  • Every time we run a report on the parcels, it always gives a 17,000 square foot lot size. Most of these lots are clearly smaller than 17,000 square feet. Can this be fixed? (Justin Daniels)

  • Can Urban Village Designations and their subsequent growth areas be added to the parcels? (Justin Daniels)

  • When a project is in a Planned Development Zoning, Geocortex shows just the Planned Development Permit Number that was approved for the lot, but it doesn't show the Planned Development Zoning number, for example PDC19-002. Can this be added to the applicable lots? (Justin Daniels)

  • Add Parks and Trails, requested by Nolan 4-24-19

  • Add near parks/trails 500ft buffer, requested by Nolan 4-24-19

  • Add Easements for electrical, storm, sanitary (Requested 4/8/19 by Building staff)

  • Analyze and update the FEMA layer, possibly need to publish as a new layer (Requested 3/22/19 by Joe D)

  • Add Soft Story (After RFP Delivers) (Requested by Building)

ORIGINAL v1.0

- Deployed 3/25/2019

Back 2 Top




Back 2 Top

Related content