Latest Contributions by KiyoshiYamashita

Hi John, We did a webinar series in 2021 that goes into the process in a little more depth.  I believe it's a bit newer than the video at the YouTube link you shared.  You can find the recordings here: https://www.esri.com/en-us/lg/industry/government/2021-national-aviation-webinar-series. Also, it sounds like you are very much on the right track for getting started.  The next step would be to load data into the AIS, and the Import AIXM 5.1 geoprocessing tool is the main way that we do that.  Unfortunately, the FAA NASR data is not a dataset that we've done much testing with in its AIXM flavor. I did a little bit of experimenting and was able to reproduce the results that you describe (empty output).  Looking a bit closer, I noticed that there may be some things in the AIXM message itself that are contributing to the issue.  But without errors being returned by the tool, it's hard to track down what the specific issue is.  I've passed this on to the product team so that they can look into this further. If it's critical for you to work with this FAA data, please reach out to us through tech support so we can start to look a bit deeper sooner.  But if you're just trying to familiarize yourself with the product for now, you may have better luck with AIXM data from a different organization.  Here are a few agencies that publish AIXM data that I've had success with in the past: Brazil - https://aisweb.decea.mil.br/?i=publicacoes&p=aixm Spain - https://aip.enaire.es/AIP/DatosDigitales-en.html Germany - https://aip.dfs.de/datasets/   ... View more

In addition to the resources that Bob shared, you might try looking at some data that the FAA shares via their Open Data site: https://adds-faa.opendata.arcgis.com/.  They include both airports and air traffic routes in the US, though you'll still have to construct the network from the data yourself. ... View more

ArcGIS Aviation includes tools that can help you create these surfaces.  By default, the surfaces use parameters (i.e. slopes, etc.) that conform to various US and international standards.  But there is also a utility that lets you customize many of these parameters.  For example, you could change the default 50:1 slope to a 37:1 slope if desired.  The tool can create both 3D polygon and multipatch output.  Also, as Christine mentioned above, there are tools that can help you perform the required analysis as well.  In particular, the Analyze LAS Runway Obstacles tool (https://pro.arcgis.com/en/pro-app/latest/tool-reference/aviation/analyze-las-runway-obstacles.htm) compares LAS data to the 3D surfaces (multipatch features) you create, to identify areas where the point cloud penetrates the surfaces. Without access to ArcGIS Aviation Airports, the raster approach described above is probably a suitable substitute.  ... View more

Yeah... creating the contours is actually the easy part, once you have noise data in raster format.  The interpolation approach mentioned above is probably the best if you're trying to represent observed noise.  In other words, if you have a collection of noise observations/measurements, you can use interpolation to create a raster that will allow you to build contours.  But often airports are trying to do noise studies based on things like types of aircraft and normal traffic patterns.  Unfortunately, I don't believe we have specific tools for doing this modeling yet... there's some hefty science behind it.  I imagine it would be possible, but would have to learn more about the specific models first.  There are other tools that are commonly used for this though.  FAA's Aviation Environmental Design Tool (https://aedt.faa.gov/) is probably one of the biggest.  I haven't used it myself, but if it can output a raster, you could very easily create the contours from there. ... View more

Good call @DavidWickliffe ! That's a much easier way to find it.  I had to dig around to find the individual services.  The open data site you linked also includes some of the actual data that goes into the maps, which might be useful as well. ... View more

@Will - looks like I was wrong... FAA services are shared publicly now.  There are four services altogether:  Sectionals: https://tiles.arcgis.com/tiles/ssFJjBXIUyZDrSYZ/arcgis/rest/services/VFR_Sectional/MapServer TACs: https://tiles.arcgis.com/tiles/ssFJjBXIUyZDrSYZ/arcgis/rest/services/VFR_Terminal/MapServer Enroute Low: https://tiles.arcgis.com/tiles/ssFJjBXIUyZDrSYZ/arcgis/rest/services/IFR_AreaLow/MapServer Enroute High: https://tiles.arcgis.com/tiles/ssFJjBXIUyZDrSYZ/arcgis/rest/services/IFR_High/MapServer   ... View more

The FAA does have a service like this, but it is still internal only at the moment.  Skyvector (https://skyvector.com/) also hosts all of the FAA enroute and sectional charts, but I've only ever used it through the browser, not sure whether their service can be used outside their site.  Finally, FAA also publishes all of their charts as geoTIFs so downloading and/or creating your own service might be possible as well. Also fwiw - it looks like chartbundle has shut down (they commented on this thread https://www.pilotsofamerica.com/community/threads/sectionals-for-google-earth-anybody-know-what-happened-to-chartbundle.145754/). ... View more

Hi @Don_Snow.  The ArcGIS Aviation Airports extension has some tools that can help with this sort of analysis. There are tools for creating the OLS surfaces, tools for comparing the OLS surfaces to obstacle data (both vector and lidar point cloud), and tools for creating terrain and obstacle profile graphics for obstacle charts.  You can check out the tools we have available here: https://pro.arcgis.com/en/pro-app/latest/tool-reference/aviation/an-overview-of-the-airports-toolset.htm The specific case you described above is a little more challenging though.  If your terrain data is available as a lidar dataset (.las or .lasd), you could use the Analyze LAS Runway Obstacles tool to find the places where the terrain penetrates the OLS.  But your output would be either a *.las point cloud or a collection of point features.  Another approach might be to convert your OLS features to raster and do some raster math with the terrain.  I think a difference function (Minus: https://pro.arcgis.com/en/pro-app/latest/tool-reference/3d-analyst/minus.htm) should yield a raster where negative values indicate penetrations.  Then you could do some classification and convert the output to polygons. Hope this is helpful.  If you have any questions about the ArcGIS Aviation products, come find us in the ArcGIS Aviation community here: https://community.esri.com/t5/arcgis-aviation/ct-p/arcgis-aviation.    ... View more

Yes, the extension includes tools for creating surfaces based on the Unified Facilities Criteria (UFC) 3-260-01 that is prescribed by MIL-STD 3007.  You can find more information about those tools here: https://pro.arcgis.com/en/pro-app/latest/tool-reference/aviation/ufc.htm ... View more

Hi Roman, Thanks for bringing this additional issue to our attention!  We have looked into this a bit more and, yes, we will be addressing the problem in a future release.  In the meantime, there are a couple ways that you can address this: One approach is to directly modify the AIXM message after export to correct the formatting issue.  This is probably the simplest approach, but may not be ideal for long term use with repeated exports over time.  To do this, you'll need to modify the date string in the XML file for each <aixm:certificationDate> entity (or any other date-only entities.  date-time entities like those in the TimeSlice should be ok).  You'll need to either remove the "T00:00:00" portion all together, or change it to a "+00:00" format to represent the time zone as a GMT offset. Another approach would be to extend the AIS model with a new attribute to store the date as text in the proper AIXM-friendly format.  For example, you could add CertificationDate_Txt with a Text data type to the feature class to store the date in the "YYY-MM-DD" format that AIXM allows.  Then, you would need to modify some of the installed configuration files to ensure that the exporter uses this new field instead of the original one.  This would a more permanent workaround, but is a bit more complicated to implement. If you would like assistance with either of these, you can contact us at aero@esri.com or submit a request through technical support. ... View more

Hi Roman, This is a known issue that will be addressed in a future release.  Essentially, the exporter is currently including the ADHPSurfaceArea::Designator_Txt attribute for apron features, but this is not supported in AIXM.  Thus, the validation is reporting the unsupported value that it's finding. Until the fix is available, I've found that removing the Designator_Txt values for apron features (for example, the "APN_EAST" value you show in your attachment) before exporting to AIXM will avoid the validation errors as well. ... View more

Hi @whiss33!  We see a lot of applications for GIS in the aviation industry.  Some agencies use it for data management and chart production and cartography.  We're also seeing a lot of applications for data visualization and analysis, drone imagery capture, AI/ML, and airfield operations. Check out our industry page for more examples: https://www.esri.com/en-us/industries/aviation/overview (3d point cloud captured by drone using Site Scan) ... View more

Are you getting any error messages from Analyze Runway Obstacles?  On the surface, it seems like there shouldn't be an issue with the process you describe.  However, if you're trying to append the Description value to the feature class name as-is, you may be running into an issue of invalid feature class names.  The Description includes special characters (spaces, parens, slashes, etc.) that will not be allowed when naming a feature class. Side note: the output of Analyze Runway Obstacles will include the Description on each feature in a field called DESCRIP.  So another approach might be to run Analyze Runway Obstacles once and then use your model to split the output into separate feature classes afterwards. ... View more

@DanN If you've created an AIS geodatabase and created one or more AOI features in the AIS_AOI feature class (note: prior to the 2.9 release the AOI feature class was named "AOI"), you should see your AOIs listed in the "AOIs Available" section of the Map Properties dialog as shown in your screenshot.  Now, you'll need to make sure that you've populated the attributes of your AOI features as well, specifically the MapID, ReferenceScale, Rotation, UseGeographicExtent, SpatialReference, and Tags attributes. As you noted, the MapId string is parsed to generate the tree structure used in the dialog, so make sure your MapId values use the proper format: each name in the MapId is separated by two colons ("::").  And each name represents a level in your product catalog hierarchy. One other note, sometimes I've found that you need to restart ArcGIS Pro after creating your AOI features because Pro has a tendency to cache information for efficiency.   ... View more